RE: [tip:tracing/core] Revert "x86, bts: reenable ptrace branchtrace support"
From: Metzger, Markus T
Date: Thu Jun 11 2009 - 06:39:55 EST
>From: Ingo Molnar [mailto:mingo@xxxxxxx]
>Sent: Thursday, June 11, 2009 12:22 PM
>To: Peter Zijlstra
>Cc: Metzger, Markus T; linux-kernel@xxxxxxxxxxxxxxx; mingo@xxxxxxxxxx; hpa@xxxxxxxxx; oleg@xxxxxxxxxx;
>Subject: Re: [tip:tracing/core] Revert "x86, bts: reenable ptrace branch trace support"
>* Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
>> On Thu, 2009-06-11 at 07:30 +0100, Metzger, Markus T wrote:
>> > >-----Original Message-----
>> > >From: tip-bot for Ingo Molnar [mailto:mingo@xxxxxxx]
>> > >Sent: Thursday, June 11, 2009 1:37 AM
>> > >To: linux-tip-commits@xxxxxxxxxxxxxxx
>> > >Cc: hpa@xxxxxxxxx; mingo@xxxxxxxxxx; peterz@xxxxxxxxxxxxx; Metzger, Markus T; oleg@xxxxxxxxxx;
>> > >tglx@xxxxxxxxxxxxx; mingo@xxxxxxx
>> > >Subject: [tip:tracing/core] Revert "x86, bts: reenable ptrace branch trace support"
>> > >
>> > >Commit-ID: 511b01bdf64ad8a38414096eab283c7784aebfc4
>> > >Gitweb: http://git.kernel.org/tip/511b01bdf64ad8a38414096eab283c7784aebfc4
>> > >Author: Ingo Molnar <mingo@xxxxxxx>
>> > >AuthorDate: Thu, 11 Jun 2009 00:32:00 +0200
>> > >Committer: Ingo Molnar <mingo@xxxxxxx>
>> > >CommitDate: Thu, 11 Jun 2009 00:32:00 +0200
>> > >
>> > >Revert "x86, bts: reenable ptrace branch trace support"
>> > >
>> > >This reverts commit 7e0bfad24d85de7cf2202a7b0ce51de11a077b21.
>> > >
>> > >A late objection to the ABI has arrived:
>> > >
>> > > http://lkml.org/lkml/2009/6/10/253
>> > I thought that this has been resolved. See for example http://lkml.org/lkml/2009/6/10/257.
>> > Peters concerns were that Debug Store details are exposed to user space, which is
>> > not the case. Debug Store itself is fully in-kernel and the expectation of a
>> > user-defined buffer can be implemented on top of the Debug Store changes that
>> > Peter expects are needed to support PEBS.
>> > A user-defined trace buffer size is required to support
>> > different usage models. Some users only need a small amount of
>> > trace, whereas others need a big amount. The interface will have
>> > to reflect that in some way.
>> Right, your last email did explain how we could keep per task
>> in-kernel buffers and fill them from the DS and still have them of
>> user-specified size.
>> That would indeed keep the proposed ABI workable, what I'm still
>> not liking is that this buffer is in-kernel, but I guess that
>> might be something for other people to have an opinion on.
>Hm. Wrt. the ABI, wouldnt it make more sense to expose this PMU
>feature via perfcounters: a sampling hw-branch-executions counter,
>That would give the exact existing semantics, plus a lot lot more.
What more would we get?
I take it that you don't want to implement branch tracing via PEBS,
which would be possible but rather inefficient since the BTS format
is much more compact than the PEBS format.
So we would still implement it via BTS and we would still like to present
a branch trace specific format to the user.
Are you suggesting to use a common ABI for sampling and branch tracing?
The existing ABI is tailored towards the expected users: debuggers.
I do believe that a ptrace based interface makes a lot of sense for
this debugging-related feature, since debuggers already speak ptrace.
Branch tracing and sampling are used by different classes of user-mode
applications. I don't think that a common ABI would benefit user-mode.
Since we do need different implementations in the kernel, I don't see
how a common ABI would help here, either.
I rather see this as two independent, unrelated hardware features that
happen to use the same technique to allow arbitrary-sized buffers and
that therefore share some hardware real-estate.
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/