Hi all,
There is confusion about the usage of format for me.
E.g. The event config is not continuous for uncore.
cat /sys/devices/uncore_qpi_0/format/event
config:0-7,21
I once thought that the user input should be
uncore_qpi_0/event=0x200038,/
So I submitted this patch and previous patch
Hi all,
There is confusion about the usage of format for me.
E.g. The event config is not continuous for uncore.
cat /sys/devices/uncore_qpi_0/format/event
config:0-7,21
I once thought that the user input should be
uncore_qpi_0/event=0x200038,/
So I submitted this patch and previous patch
> On Mon, Apr 04, 2016 at 06:12:54AM -0700, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > The calculation of format value also rely on the continuity of the
> > format. However, uncore event format is not continuous.
> > E.g. The bit 21 as qpi event is lost.
> >
> >
> On Mon, Apr 04, 2016 at 06:12:54AM -0700, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > The calculation of format value also rely on the continuity of the
> > format. However, uncore event format is not continuous.
> > E.g. The bit 21 as qpi event is lost.
> >
> > perf stat -a -e
On Mon, Apr 04, 2016 at 06:12:54AM -0700, kan.li...@intel.com wrote:
> From: Kan Liang
>
> The calculation of format value also rely on the continuity of the
> format. However, uncore event format is not continuous.
> E.g. The bit 21 as qpi event is lost.
>
> perf stat -a
On Mon, Apr 04, 2016 at 06:12:54AM -0700, kan.li...@intel.com wrote:
> From: Kan Liang
>
> The calculation of format value also rely on the continuity of the
> format. However, uncore event format is not continuous.
> E.g. The bit 21 as qpi event is lost.
>
> perf stat -a -e
6 matches
Mail list logo