LKML Archive on
help / color / mirror / Atom feed
From: "Metzger, Markus T" <>
To: "stephane eranian" <>
Cc: "Roland McGrath" <>,
	"Ingo Molnar" <>, <>,
Subject: RE: ptrace API extensions for BTS
Date: Wed, 30 Jan 2008 12:52:40 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>From: stephane eranian [] 
>Sent: Mittwoch, 30. Januar 2008 12:01

>You can get information about the perfmon2 project at: 

I downloaded your patch for 2.6.23 and cloned your git repository.

>From a first glance, it looks like there is indeed a lot of overlap.

>I would like to take a look at your patches. Where can I get them?

You can find the changes in the mm branch of the x86 git. Do they keep
the patches there, somewhere, as well?

You should get the best overview if you look at arch/x86/kernel/ds.c,
include/asm-x86/ds.h, include/asm-x86/ptrace-abi.h, and
arch/x86/kernel/ptrace.c or simply grep for BTS.

I have all the patches that I submitted but they rather protocol
development than describe the final thing.

>My understanding at this point is that we would need to coordinate
>access to the
>DS_AREA. It would likely have to be mutually exclusive access. 

>From a brief look at your patch, I would say that we should rather
combine the configuration and collection part. They are very similar.

We might still want to provide different interfaces on top of it.
In particular, I think the ptrace interface is most appropriate for

>I am planning on
>adding support for LBRs in the next few months. But BTS the way it is
>currently defined
>is useless for performance monitoring. I think this a great debug
>feature, though.

Debugging was my target;-)

>Now, there is some preliminary perf. MSR allocator in the kernel.
>However, it does not know
>of all available MSRs out there. It focuses on the counters mostly.
>Perfmon, oprofile and
>the NMI watchdog use it. I think it could be generalized to other MSR
>I would be happy to work with you in refining this MSR allocator.

Are you planning to get the perfmon patch into the kernel? Or do you
want it to remain a separate patch?

In the first case, we should try to merge the features. In the second
case, refining the MSR allocator would probably be best.

thanks and regards,
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.

  reply	other threads:[~2008-01-30 12:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-07  9:11 Metzger, Markus T
2007-12-07 11:18 ` Andi Kleen
2007-12-07 12:01   ` Metzger, Markus T
2007-12-07 13:04     ` Andi Kleen
2007-12-07 13:36       ` Metzger, Markus T
2008-01-30  7:25 ` Roland McGrath
2008-01-30 10:32   ` Metzger, Markus T
2008-01-30 11:01     ` stephane eranian
2008-01-30 12:52       ` Metzger, Markus T [this message]
2008-01-30 13:39         ` stephane eranian
2008-01-31 11:15         ` stephane eranian
2008-01-31 17:45           ` Metzger, Markus T

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='RE: ptrace API extensions for BTS' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).