[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110517195757.GA31067@liondog.tnic>
Date: Tue, 17 May 2011 21:57:57 +0200
From: Borislav Petkov <bp@...en8.de>
To: Ingo Molnar <mingo@...e.hu>
Cc: Don Zickus <dzickus@...hat.com>, Huang Ying <ying.huang@...el.com>,
Len Brown <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andi Kleen <andi@...stfloor.org>,
"Luck, Tony" <tony.luck@...el.com>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [RFC] ACPI, APEI, Generic Hardware Error Source (GHES)
injecting support
On Tue, May 17, 2011 at 09:18:03PM +0200, Ingo Molnar wrote:
> So for example [sufficienty privileged] user-space could inject *any*
> perf event - for example a PERF_COUNT_HW_CACHE_MISSES event (for test
> purposes) and any tooling that runs could not tell apart this injected
> event from a real event.
Yeah about that, I was recently speculating how that would work. So do we do
$ perf record ...
in the one xterm, and, in the other,
$ perf inject
so that while recording, we can inject some events from userspace? Or
do we inject it, it gets buffered somewhere in the meantime and then
the next perf record session sees it along with the remaining injection
events?
The ras inject part would obviously only use the callback and the
injection will happen immediately.
Hmm...
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists