[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071116162813.GA29644@one.firstfloor.org>
Date: Fri, 16 Nov 2007 17:28:13 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Stephane Eranian <eranian@....hp.com>
Cc: Andi Kleen <andi@...stfloor.org>, Philip Mucci <mucci@...utk.edu>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <gregkh@...e.de>, William Cohen <wcohen@...hat.com>,
Robert Richter <robert.richter@....com>,
linux-kernel@...r.kernel.org
Subject: Re: perfmon2 merge news
On Fri, Nov 16, 2007 at 08:00:56AM -0800, Stephane Eranian wrote:
> No, he is talking about something similar to what was in perfctr.
> The kernel emulates 64-bit counters in software and that is you
> get back when you read the counters. If you read via RDPMC, you
> get 40 bits. To reconstruct the full 64-bit value from user land
> you need the upper bits. One approach is for the kernel to allow
> you to remap a page that has the 64-bit (software) counters. With
> that and a bit of mask/shifting you can reconstruct the full value.
You mean the page contains the upper [40;63] bits?
Sounds reasonable, although I don't remember seeing that when I looked
at the perfmon code last.
>
> > I'm considering that an essential feature too. I wasn't aware
> > it was dropped.
> >
> What I dropped is the cr4.pce enabled for self-monitoring sessions.
That sounds bad.
> Perfmon2 allows you to have an in-kernel sampling buffer. The idea is
... you also didn't say *why* that is needed.
Can you give a concrete use case for something that cannot be done
without custom buffer formats?
> Using this mechanism, for instance, we were able to connect the
> Oprofile kernel code to perfmon2 on Itanium with a 100 lines of
> code. The exact same approach would also work on X86 Oprofile as well.
The existing oprofile code works already fine on x86, no real
need for another one.
> > e.g. PEBS and so on pretty much fix the in memory sample format in hardware,
> > so they only way to get a custom format would be to use a separate buffer.
> >
>
> This is also how we support PEBS because, as you said, the format of the
> samples is not under your control. if you want zero-copy PEBS support,
> you have to follow the PEBS format.
Exactly that makes the support for random custom buffers questionable.
e.g. as I can see the main advantage of perfmon over existing setups
is that it support PEBS etc., but with your custom buffer formats which
are by definition incompatible with PEBS you would negate that advantage
again.
Ok IBS will probably need some special handling.
> Yes, you could do that without changing the core implementation of
> perfmon2.
Why this insistence against changing anything?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists