mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "stephane eranian" <eranian@googlemail.com>
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,
	mingo@elte.hu, tglx@linutronix.de, markus.t.metzger@gmail.com,
	suresh.b.siddha@intel.com, akpm@linux-foundation.org,
	mtk.manpages@gmail.com
Subject: Re: [patch 1/2] x86, ptrace: support pebs in ds.c
Date: Thu, 21 Feb 2008 23:36:01 +0100	[thread overview]
Message-ID: <7c86c4470802211436p22155681n9a38095c0ff305ab@mail.gmail.com> (raw)
In-Reply-To: <20080221210026.7B1C62701D5@magilla.localdomain>

Roland,

I think you bring up some very good points and I agree with you.
Hopefully, I should be able to modify perfmon to use this new
internal interface in the coming weeks. That should be a good test.


On Thu, Feb 21, 2008 at 10:00 PM, 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.
>
>
>  Thanks,
>  Roland
>

  reply	other threads:[~2008-02-21 22:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 10:23 Markus Metzger
2008-02-21 21:00 ` Roland McGrath
2008-02-21 22:36   ` stephane eranian [this message]
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
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=7c86c4470802211436p22155681n9a38095c0ff305ab@mail.gmail.com \
    --to=eranian@googlemail.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.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

all inboxes | Powered by JetHome®