[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071116.161543.181413865.davem@davemloft.net>
Date: Fri, 16 Nov 2007 16:15:43 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: andi@...stfloor.org
Cc: mucci@...utk.edu, akpm@...ux-foundation.org, gregkh@...e.de,
eranian@....hp.com, wcohen@...hat.com, robert.richter@....com,
linux-kernel@...r.kernel.org, ptools-perfapi@...utk.edu
Subject: Re: perfmon2 merge news
From: Andi Kleen <andi@...stfloor.org>
Date: Fri, 16 Nov 2007 16:15:56 +0100
> Philip Mucci <mucci@...utk.edu> writes:
> > - A feature which was dropped earlier by Stefane (only to satiate
> > LKML), we consider
> > very important. Allowing one tomapping of the kernels view of the
> > PMD's, allowing
> > user-space access to full 64-bit counts, if the architecture
> > supports a user-level read instruction.
>
> You mean returning the register number for RDPMC or equivalent
> and a way to enable it for ring 3 access?
>
> I'm considering that an essential feature too. I wasn't aware
> it was dropped.
>
> > Getting the counts in a
> > couple of dozen cycles
> > is ALWAYS a win for us.
>
> Yes it is for everybody. I've been rather questioning if the slow
> ways (complicated syscalls) to get the counter information are really
> needed.
I would like to add sparc64 support to perfmon2 as well
and therefore I've been considering this angle of the
API issues as well.
The counters on sparc64 can be configured to be readable by userspace,
so for the self-monitoring cases I really would like to make sure the
perfmon2 library interface could use direct reads for sampling instead
of system calls or specialized traps.
If I get some spare time I'll look at the current perfmon2 patches
and see if I can toss together sparc64 support to get a feel for
how things stand currently.
-
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