[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <029E5BE7F699594398CA44E3DDF554440105236A@swsmsx413.ger.corp.intel.com>
Date: Fri, 30 Nov 2007 15:45:31 -0000
From: "Metzger, Markus T" <markus.t.metzger@...el.com>
To: "Andi Kleen" <ak@...e.de>, <tglx@...utronix.de>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>,
<linux-kernel@...r.kernel.org>, <mingo@...e.hu>, <hpa@...or.com>,
"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
"Michael Kerrisk" <mtk-manpages@....net>,
"Metzger, Markus T" <markus.t.metzger@...el.com>,
<markus.t.metzger@...il.com>
Subject: RE: [patch 0/2] x86, ptrace: support for branch trace store(BTS)
>> Not yet. We are talking to internal teams regarding gdb support.
>
>But you already have reasonably realistic test code right?
I wrote a small program to talk to ptrace and look at the trace of small
sample programs to test the patch. I do this on P4 32bit and Core2
64bit.
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.
>e.g. I'm still feeling a bit uneasy about that global sysctl
>embedded in the interface.
I added a ptrace command to query for the maximal buffer size and moved
the macro to ptrace_bts.h.
I am not sure how much flexibility is actually needed, here. I would
expect
the trace to be very useful near its tail, but unmanageable when it gets
too big.
I would rather add flexibility when and where it is needed.
regards,
markus.
---------------------------------------------------------------------
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists