Re: [PATCH v3 6/9] perf, x86: handle multiple records in PEBS buffer
From: Andi Kleen
Date: Fri Jul 25 2014 - 11:04:54 EST
> You can't.. the events might have different security context.
> Remember, the overflow bit is set from the overflow until the PEBS
> event is generated, this is quite a long time. So if another PEBS event
> gets generated while the other is still pending it will have both bits
> set. Even though the second bit is for another (unrelated) counter.
When an event is not allowed by some policy it should be disabled
in global ctrl right? And disabling makes sure overflow is cleared,
and PEBS will not report it.
When it's not disabled it could happen any time and there
is no isolation.
Or is the concern that the PEBS buffer may not be flushed
on event switch/disable and you see something stale? I believe it is
> I think you can unwind and fully correct this trainwreck. But simply
> delivering an even with multiple bits set to all relevant events is
> wrong and might leak sensitive information.
In theory could double check that the event is enabled,
but I don't think it's really needed.
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/