Searched refs:psb_period (Results 1 – 3 of 3) sorted by relevance
141 size_t psb_period; in intel_pt_psb_period() local152 psb_period = 256; in intel_pt_psb_period()160 psb_period = 1 << (val + 11); in intel_pt_psb_period()163 return psb_period; in intel_pt_psb_period()222 ",psb_period=%d", psb_period); in intel_pt_default_config()710 if (psb_period && in intel_pt_recording_options()739 if (psb_period && in intel_pt_recording_options()742 min_sz, psb_period); in intel_pt_recording_options()983 size_t buf_size = 0, psb_period; in intel_pt_snapshot_ref_buf_size() local989 if (psb_period) in intel_pt_snapshot_ref_buf_size()[all …]
255 /sys/bus/event_source/devices/intel_pt/format/psb_period:config:24-27352 *psb_period*::358 Support for psb_period is indicated by:372 The psb_period value is converted to the approximate number of382 $ perf record -e intel_pt/psb_period=15/u uname383 Invalid psb_period for intel_pt. Valid values are: 0-5386 of 3 (i.e. psb_period=3) or the nearest lower value that is619 The calculation used for that is: if sample_size <= psb_period + 256 display the620 warning. When sampling is used, psb_period defaults to 0 (2KiB).1189 PSBEND). Note PSB packets occur regularly in the trace based on the psb_period
120 PMU_FORMAT_ATTR(psb_period, "config:24-27" );