public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Markus Metzger <markus.t.metzger@intel.com>,
	ak@suse.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, markus.t.metzger@gmail.com,
	suresh.b.siddha@intel.com, akpm@linux-foundation.org,
	mtk.manpages@gmail.com, eranian@googlemail.com
Subject: Re: [patch 1/2] x86, ptrace: support pebs in ds.c
Date: Tue, 26 Feb 2008 09:51:54 +0100	[thread overview]
Message-ID: <20080226085154.GD9857@elte.hu> (raw)
In-Reply-To: <20080221210026.7B1C62701D5@magilla.localdomain>


* Roland McGrath <roland@redhat.com> wrote:

> Sorry I haven't replied in this thread sooner.
> 
> I would like to see all the BTS and DS work wait until after 2.6.25. 
> We have a lot of x86 churn in 2.6.25 already, and I think we'd do 
> better without adding this wrinkle at the same time.
> 
> The low-level implementation pieces should gel a bit more in -mm or 
> whereever.  They should both get more testing and also get more 
> concrete use from the perfmon2 integration effort to iron out their 
> internal interface kinks.
> 
> For the user-level interface, we should not be hasty with cooking up 
> hairy ptrace extensions.  Personally, I'd prefer that we never add a 
> ptrace-based interface for this (ptrace must die).  I think it will 
> fit much better either merged into the interfaces that come from 
> perfmon2 integration, or into what replaces ptrace when that comes. 
> There is not yet any different userland interface framework in the 
> tree to base it on, so ptrace extensions may be better than nothing if 
> they are well-gelled in 2.6.26 and nothing else is close to ready. But 
> I also don't know of anyone desperate and about to burst from lack of 
> BTS functionality.

i'd you'd like to have something like the patch below to happen?

what API should BTS/DS functionality use towards user-space if not 
ptrace? Should it be utrace?

	Ingo

--------------------->
Subject: x86: disable BTS ptrace extensions for now
From: Ingo Molnar <mingo@elte.hu>
Date: Tue Feb 26 09:40:27 CET 2008

based on general objections from Roland McGrath:

    http://lkml.org/lkml/2008/2/21/323

we'll let the BTS functionality cook some more and enable
it in v2.6.26.

(X86_BTS is not defined at the moment)

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/kernel/ptrace.c |    5 +++++
 1 file changed, 5 insertions(+)

Index: linux-x86.q/arch/x86/kernel/ptrace.c
===================================================================
--- linux-x86.q.orig/arch/x86/kernel/ptrace.c
+++ linux-x86.q/arch/x86/kernel/ptrace.c
@@ -961,6 +961,10 @@ long arch_ptrace(struct task_struct *chi
 		break;
 #endif
 
+	/*
+	 * These bits need more cooking - not enabled yet:
+	 */
+#ifdef X86_BTS
 	case PTRACE_BTS_CONFIG:
 		ret = ptrace_bts_config
 			(child, data, (struct ptrace_bts_config __user *)addr);
@@ -988,6 +992,7 @@ long arch_ptrace(struct task_struct *chi
 		ret = ptrace_bts_drain
 			(child, data, (struct bts_struct __user *) addr);
 		break;
+#endif
 
 	default:
 		ret = ptrace_request(child, request, addr, data);

  parent reply	other threads:[~2008-02-26  8:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 10:23 [patch 1/2] x86, ptrace: support pebs in ds.c Markus Metzger
2008-02-21 21:00 ` Roland McGrath
2008-02-21 22:36   ` stephane eranian
2008-02-22  8:49   ` Metzger, Markus T
2008-02-22  9:53     ` Ingo Molnar
2008-02-22 10:12       ` Metzger, Markus T
2008-02-26  8:51   ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-18  8:41 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=20080226085154.GD9857@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=eranian@googlemail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus.t.metzger@gmail.com \
    --cc=markus.t.metzger@intel.com \
    --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