From: Andi Kleen <ak@suse.de>
To: "Markus Metzger" <markus.t.metzger@googlemail.com>
Cc: "Roland McGrath" <roland@redhat.com>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
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, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [patch 0/2] x86, ptrace: support for branch trace store(BTS)
Date: Mon, 3 Dec 2007 17:21:38 +0100 [thread overview]
Message-ID: <200712031721.39013.ak@suse.de> (raw)
In-Reply-To: <a430082a0712030553v22e9b46bnb9da975a23b1c0db@mail.gmail.com>
On Monday 03 December 2007 14:53:27 Markus Metzger wrote:
> > 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.
>
> I'm looking very much forward to utrace. From what I read so far, this is
> a much nicer interface.
Just don't wait for that. utrace doesn't seem to have any concrete
plans to merge any time soon AFAIK[1] and it would be a shame to delay an useful
feature forever.
[1] At least the patches have not reached any mailing lists
> What did you have in mind when you asked for kernel-mode support?
I asked about that earlier too and I would like to see per CPU traces
for ring 0 with some way to dump that on crashes or on user trigger.
-Andi
next prev parent reply other threads:[~2007-12-03 16:21 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
2007-12-03 13:53 ` Markus Metzger
2007-12-03 15:17 ` Metzger, Markus T
2007-12-03 16:21 ` Andi Kleen [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=200712031721.39013.ak@suse.de \
--to=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@googlemail.com \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.