On Fri, May 08, 2015 at 01:05:47PM +0200, Andi Kleen wrote:
> > The first issue is that the 'status' field of the PEBS record is a copy
> > of the GLOBAL_STATUS MSR at PEBS assist time. To see why this is a
>
> I wanted to mention that Skylake has this issue fixed. The status
> field in PEBS is no
> The first issue is that the 'status' field of the PEBS record is a copy
> of the GLOBAL_STATUS MSR at PEBS assist time. To see why this is a
I wanted to mention that Skylake has this issue fixed. The status
field in PEBS is now only the counter that triggered the PEBS record.
> The second issue
From: Yan, Zheng
When the PEBS interrupt threshold is larger than one record and the
machine supports multiple PEBS events, the records of these events are
mixed up and we need to demultiplex them.
Demuxing the records is hard because the hardware is deficient. The
hardware has two issues that,
3 matches
Mail list logo