From: Borislav Petkov <bp@alien8.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Don Zickus <dzickus@redhat.com>,
Huang Ying <ying.huang@intel.com>, Len Brown <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <andi@firstfloor.org>,
"Luck, Tony" <tony.luck@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [RFC] ACPI, APEI, Generic Hardware Error Source (GHES) injecting support
Date: Tue, 17 May 2011 21:57:57 +0200 [thread overview]
Message-ID: <20110517195757.GA31067@liondog.tnic> (raw)
In-Reply-To: <20110517191803.GC29574@elte.hu>
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.
next prev parent reply other threads:[~2011-05-17 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 3:08 Huang Ying
2011-05-16 19:33 ` Don Zickus
2011-05-17 6:41 ` Huang Ying
2011-05-17 13:50 ` Don Zickus
2011-05-17 19:18 ` Ingo Molnar
2011-05-17 19:57 ` Borislav Petkov [this message]
2011-05-20 11:53 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110517195757.GA31067@liondog.tnic \
--to=bp@alien8.de \
--cc=andi@firstfloor.org \
--cc=dzickus@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tony.luck@intel.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®