From: Ingo Molnar <mingo@elte.hu>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Andi Kleen <ak@suse.de>,
tglx@linutronix.de, Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, hpa@zytor.com, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>,
Michael Kerrisk <mtk-manpages@gmx.net>,
markus.t.metzger@gmail.com, Roland McGrath <roland@redhat.com>
Subject: Re: [patch 0/2] x86, ptrace: support for branch trace store(BTS)
Date: Sat, 1 Dec 2007 08:40:46 +0100 [thread overview]
Message-ID: <20071201074044.GA13974@elte.hu> (raw)
In-Reply-To: <20071130170655.GA10868@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> > Our debugger team has a prototype implementation for their debugger.
> > But that will not be available for some time.
> >
> > I hope that we get gdb support, soon, but that would take a while if
> > I had to do it.
>
> i'm wondering what the main use-case would be then, and what the gdb
> folks think about the current API. (Roland?)
here's a forwarded mail from Roland about the patch and APIs. (and i
hope that now i can stop playing the middleman, with everyone Cc:-ed :)
------------>
From: Roland McGrath <roland@redhat.com>
Subject: Re: [patch][v2] x86, ptrace: support for branch trace store(BTS)]
Cool. It's been on my list to look into exposing those features
somehow. I hadn't planned on doing it until after the utrace stuff
settles and there is a more coherent interface context in which to do
it.
If they are tackling the MSR hacking and context switch and so forth,
I'd like to see them start out by just adding block-step
(debugctlmsr.btf) with the PTRACE_SINGLEBLOCK interface as ia64 has.
That should lay some of the same groundwork needed here, but is much
simpler.
I am not really in favor of this new ptrace interface. I think they
should look around across arch's and think about sane general-purpose
interfaces for features of this kind that might be built with some
commonality across machines. Also do it in a layered way from
low-level, with something usable for kernel-mode too. The discussion
Alan Stern and I had on LKML that started as kwatch and became
hw_breakpoint is an example of how I would go at this set of features
too.
next prev parent reply other threads:[~2007-12-01 7:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 8:14 [patch 0/2] x86, ptrace: support for branch trace store(BTS) Metzger, Markus T
2007-11-29 23:59 ` Andrew Morton
2007-11-30 9:57 ` Metzger, Markus T
2007-11-30 10:34 ` Andi Kleen
2007-11-30 15:45 ` Metzger, Markus T
2007-11-30 17:06 ` Ingo Molnar
2007-12-01 7:40 ` Ingo Molnar [this message]
2007-12-03 13:53 ` Markus Metzger
2007-12-03 15:17 ` Metzger, Markus T
2007-12-03 16:21 ` Andi Kleen
2007-12-03 16:45 ` Ingo Molnar
2007-12-03 17:11 ` Andi Kleen
2007-12-03 17:22 ` Thomas Gleixner
2007-12-03 21:55 ` Ingo Molnar
2007-12-03 22:02 ` Andi Kleen
2007-12-04 8:52 ` Metzger, Markus T
2007-11-30 10:54 ` Ingo Molnar
2007-11-30 15:48 ` Metzger, Markus T
2007-11-30 16:04 ` Michael Kerrisk
2007-11-30 16:08 ` Michael Kerrisk
2007-11-30 15:56 Markus Metzger
2007-12-04 18:03 Markus Metzger
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=20071201074044.GA13974@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mtk-manpages@gmx.net \
--cc=roland@redhat.com \
--cc=suresh.b.siddha@intel.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;
as well as URLs for NNTP newsgroup(s).