From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-kernel@vger.kernel.org
Cc: Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: [patch][v2] x86, ptrace: support for branch trace store(BTS)
Date: Wed, 21 Nov 2007 03:37:03 -0800 [thread overview]
Message-ID: <20071121113703.GD30184@frankl.hpl.hp.com> (raw)
Hi,
> >and it seems like this patch and perfmon2 are going to have to
> >live with
> >each other... since they both require the use of the DS save area...
>
> Hmmm, this might require some synchronization between those two.
>
> Do you know how (accesses to) MSR's are managed by the kernel?
There is a simple MSR allocator in the nmi watchdog code. It is very
simple though and was only intended for performance counters originally
so you might need to enhance it first for complicated things.
I agree it needs to be extended to manage other not necessarily contiguous
MSR registers.
As for BTS, I am happy to see this resource exposed for debugging purposes.
Note that it could also be used for performance monitoring purposes and it
could be exploited by the perfmon2 subsystem via a new sampling format. This
way one could for instance figure out the path that led to a cache miss. Of
course, this requires that some filtering be applied to BTS which today does
not differentiate loop vs. function branches, AFAIR. The current cost can
be mitigated by using a long sampling period and by monitoring longer.
--
-Stephane
next reply other threads:[~2007-11-21 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 11:37 Stephane Eranian [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-20 8:20 Metzger, Markus T
2007-11-20 12:45 ` Andi Kleen
2007-11-21 11:02 ` Metzger, Markus T
2007-11-21 11:40 ` Andi Kleen
2007-11-22 20:06 ` Metzger, Markus T
2007-11-20 15:26 ` dean gaudet
2007-11-20 15:37 ` dean gaudet
2007-11-20 15:49 ` Metzger, Markus T
2007-11-20 15:57 ` Andi Kleen
2007-11-20 15:39 ` Metzger, Markus T
2007-11-20 15:47 ` Andi Kleen
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=20071121113703.GD30184@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
/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®