From: Peter Zijlstra <peterz@infradead.org>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"oleg@redhat.com" <oleg@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@elte.hu" <mingo@elte.hu>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: RE: [tip:tracing/core] Revert "x86, bts: reenable ptrace branch trace support"
Date: Thu, 11 Jun 2009 08:36:23 +0200 [thread overview]
Message-ID: <1244702183.6691.8.camel@laptop> (raw)
In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77EBBC6544B@irsmsx504.ger.corp.intel.com>
On Thu, 2009-06-11 at 07:30 +0100, Metzger, Markus T wrote:
> >-----Original Message-----
> >From: tip-bot for Ingo Molnar [mailto:mingo@elte.hu]
> >Sent: Thursday, June 11, 2009 1:37 AM
> >To: linux-tip-commits@vger.kernel.org
> >Cc: hpa@zytor.com; mingo@redhat.com; peterz@infradead.org; Metzger, Markus T; oleg@redhat.com;
> >tglx@linutronix.de; mingo@elte.hu
> >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@elte.hu>
> >AuthorDate: Thu, 11 Jun 2009 00:32:00 +0200
> >Committer: Ingo Molnar <mingo@elte.hu>
> >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.
next prev parent reply other threads:[~2009-06-11 6:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-511b01bdf64ad8a38414096eab283c7784aebfc4@git.kernel.org>
2009-06-11 6:30 ` [tip:tracing/core] Revert "x86, bts: reenable ptrace branch trace support" Metzger, Markus T
2009-06-11 6:36 ` Peter Zijlstra [this message]
2009-06-11 7:17 ` Metzger, Markus T
2009-06-11 8:08 ` Peter Zijlstra
2009-06-11 8:30 ` Metzger, Markus T
2009-06-11 10:21 ` Ingo Molnar
2009-06-11 10:39 ` Metzger, Markus T
2009-06-11 21:41 ` Ingo Molnar
2009-06-12 11:04 ` Metzger, Markus T
2009-06-18 10:23 ` Metzger, Markus T
2009-06-24 13:10 ` Metzger, Markus T
[not found] ` <20090624133645.GE6224@elte.hu>
[not found] ` <928CFBE8E7CB0040959E56B4EA41A77EBE2DB9B9@irsmsx504.ger.corp.intel.com>
[not found] ` <20090624153229.GA24346@elte.hu>
[not found] ` <928CFBE8E7CB0040959E56B4EA41A77EBE2DC3D9@irsmsx504.ger.corp.intel.com>
[not found] ` <20090626122948.GC10850@elte.hu>
[not found] ` <928CFBE8E7CB0040959E56B4EA41A77EBE519869@irsmsx504.ger.corp.intel.com>
[not found] ` <20090629202002.GF31577@elte.hu>
2009-06-30 7:32 ` bts & perf_counters Metzger, Markus T
2009-06-30 19:32 ` Ingo Molnar
2009-07-06 15:34 ` Peter Zijlstra
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=1244702183.6691.8.camel@laptop \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=oleg@redhat.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.