From: Peter Zijlstra <peterz@infradead.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"oleg@redhat.com" <oleg@redhat.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: RE: [tip:tracing/core] x86, bts: reenable ptrace branch trace support
Date: Wed, 10 Jun 2009 15:29:18 +0200 [thread overview]
Message-ID: <1244640558.13761.11833.camel@twins> (raw)
In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77EBBC651E2@irsmsx504.ger.corp.intel.com>
On Wed, 2009-06-10 at 14:22 +0100, Metzger, Markus T wrote:
>
> The Debug Store interface is completely in-kernel. It does not expose
> anything to the outside world.
>
> What we expose is a ptrace interface for branch tracing.
> That this is built on top of Debug Store is completely hidden.
> The Debug Store interface may be changed without impacting the
> user-visible part at any time.
>
> I do think that a ptrace interface makes sense since debuggers are the
> targeted users for branch tracing.
>
> I don't see why we should not merge the fixes now and then rework the
> in-kernel parts as needed for supporting PEBS.
Ok, so what is all that account_locked_memory() for?
next prev parent reply other threads:[~2009-06-10 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 7:44 [patch] x86, bts: reenable ptrace branch trace support Markus Metzger
2009-05-07 9:25 ` [tip:tracing/core] " tip-bot for Markus Metzger
2009-06-10 12:44 ` Peter Zijlstra
2009-06-10 12:51 ` Ingo Molnar
2009-06-10 13:22 ` Metzger, Markus T
2009-06-10 13:29 ` Peter Zijlstra [this message]
2009-06-10 13:32 ` Metzger, Markus T
2009-06-10 13:43 ` Peter Zijlstra
2009-06-10 14:07 ` Metzger, Markus T
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=1244640558.13761.11833.camel@twins \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--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