From: Andi Kleen <andi@firstfloor.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
andi-suse@firstfloor.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de,
markus.t.metzger@gmail.com, "Siddha,
Suresh B" <suresh.b.siddha@intel.com>,
roland@redhat.com, akpm@linux-foundation.org,
mtk.manpages@gmail.com, eranian@googlemail.com, "Villacis,
Juan" <juan.villacis@intel.com>
Subject: Re: [patch] x86, ptrace: in-kernel BTS interface
Date: Wed, 30 Apr 2008 18:06:11 +0200 [thread overview]
Message-ID: <20080430160611.GD20451@one.firstfloor.org> (raw)
In-Reply-To: <029E5BE7F699594398CA44E3DDF5544401CE236A@swsmsx413.ger.corp.intel.com>
>
> >I'm not quite sure on the kernel interface. How would a in kernel
> >subsystem use it for tracing itself for example?
>
> The task parameter would be current.
>
> Apart from that, you would use it the same way it is used in
> arch/x86/kernel/ptrace.c.
Hmm, sounds a little too complicated. Surely that could be easier?
>
> You would want to bts_configure() it to disable tracing before you start
> reading your own BTS buffer.
I would suggest to write a simple example and put it with some overview
into Documentation
-Andi
next prev parent reply other threads:[~2008-04-30 16:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 11:54 [patch] x86, ptrace: in-kernel BTS interface Markus Metzger
2008-04-30 12:26 ` Andrew Morton
2008-04-30 12:43 ` Metzger, Markus T
2008-04-30 12:55 ` Andrew Morton
2008-04-30 13:03 ` Andi Kleen
2008-04-30 15:30 ` Metzger, Markus T
2008-04-30 16:06 ` Andi Kleen [this message]
2008-05-05 6:25 ` Metzger, Markus T
2008-05-03 1:43 ` Roland McGrath
2008-05-03 8:45 ` Andi Kleen
2008-05-05 9:09 ` Metzger, Markus T
2008-05-05 23:03 ` Roland McGrath
2008-05-06 6:39 ` stephane eranian
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=20080430160611.GD20451@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@linux-foundation.org \
--cc=andi-suse@firstfloor.org \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=mtk.manpages@gmail.com \
--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