From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 2/3 v2] perf_counter: allow arch to supply event misc flags and instruction pointer
Date: Fri, 15 May 2009 16:39:12 +0200 [thread overview]
Message-ID: <20090515143912.GA5478@elte.hu> (raw)
In-Reply-To: <18956.1272.818511.561835@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> At present the values we put in overflow events for the misc flags
> indicating processor mode and the instruction pointer are obtained
> using the standard user_mode() and instruction_pointer()
> functions. Those functions tell you where the performance monitor
> interrupt was taken, which might not be exactly where the counter
> overflow occurred, for example because interrupts were disabled at
> the point where the overflow occurred, or because the processor
> had many instructions in flight and chose to complete some more
> instructions beyond the one that caused the counter overflow.
>
> Some architectures (e.g. powerpc) can supply more precise
> information about where the counter overflow occurred and the
> processor mode at that point. This introduces new functions,
> perf_misc_flags() and perf_instruction_pointer(), which arch code
> can override to provide more precise information if available.
> They have default implementations which are identical to the
> existing code.
>
> This also adds a new misc flag value, PERF_EVENT_MISC_HYPERVISOR, for
> the case where a counter overflow occurred in the hypervisor. We
> encode the processor mode in the 2 bits previously used to indicate
> user or kernel mode; the values for user and kernel mode are unchanged
> and hypervisor mode is indicated by both bits being set.
>
> Signed-off-by: Paul Mackerras <paulus@samba.org>
> ---
> Patches 1/3 and 3/3 of this series are unchanged. Ingo, do you need
> me to repost them?
no need, picked them all up, thanks Paul!
Ingo
next prev parent reply other threads:[~2009-05-15 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 11:48 [PATCH 2/3 v2] perf_counter: allow arch to supply event misc flags and instruction pointer Paul Mackerras
2009-05-15 14:39 ` Ingo Molnar [this message]
2009-05-15 14:44 ` [tip:perfcounters/core] " tip-bot for Paul Mackerras
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=20090515143912.GA5478@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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