From: Andi Kleen <andi@firstfloor.org>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, Robert Richter <robert.richter@amd.com>,
gregkh@suse.de, linux-kernel@vger.kernel.org,
William Cohen <wcohen@redhat.com>
Subject: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
Date: Wed, 14 Nov 2007 03:07:02 +0100 [thread overview]
Message-ID: <20071114020702.GB20365@one.firstfloor.org> (raw)
In-Reply-To: <20071113225848.GK5747@frankl.hpl.hp.com>
[dropped all these bouncing email lists. Adding closed lists to public
cc lists is just a bad idea]
> int
> main(int argc, char **argv)
> {
> int ctx_fd;
> pfarg_pmd_t pd[1];
> pfarg_pmc_t pc[1];
> pfarg_ctx_t ctx;
> pfarg_load_t load_args;
>
> memset(&ctx, 0, sizeof(ctx));
> memset(pc, 0, sizeof(pc));
> memset(pd, 0, sizeof(pd));
>
> /* create session (context) and get file descriptor back (identifier) */
> ctx_fd = pfm_create_context(&ctx, NULL, NULL, 0);
There's nothing in your example that makes the file descriptor needed.
>
> /* setup one config register (PMC0) */
> pc[0].reg_num = 0
> pc[0].reg_value = 0x1234;
That would be nicer if it was just two arguments.
>
> /* setup one data register (PMD0) */
> pd[0].reg_num = 0;
> pd[0].reg_value = 0;
Why do you need to set the data register? Wouldn't it make
more sense to let the kernel handle that and just return one.
>
> /* program the registers */
> pfm_write_pmcs(ctx_fd, pc, 1);
> pfm_write_pmds(ctx_fd, pd, 1);
>
> /* attach the context to self */
> load_args.load_pid = getpid();
> pfm_load_context(ctx_fd, &load_args);
My replacement would be to just add a flags argument to write_pmcs
with one flag bit meaning "GLOBAL CONTEXT" versus "MY CONTEXT"
>
> /* activate monitoring */
> pfm_start(ctx_fd, NULL);
Why can't that be done by the call setting up the register?
Or if someone needs to do it for a specific region they can read
the register before and then afterwards.
>
> /*
> * run code to measure
> */
>
> /* stop monitoring */
> pfm_stop(ctx_fd);
>
> /* read data register */
> pfm_read_pmds(ctx_fd, pd, 1);
On x86 i think it would be much simpler to just let the set/alloc
register call return a number and then use RDPMC directly. That would
be actually faster and be much simpler too.
I suppose most architectures have similar facilities, if not a call could be
added for them but it's not really essential. The call might be also needed
for event multiplexing, but frankly I would just leave that out for now.
e.g. here is one use case I would personally see as useful. We need
a replacement for simple cycle counting since RDTSC doesn't do that anymore
on modern x86 CPUs. It could be something like:
/* 0 is the initial value */
/* could be either library or syscall */
event = get_event(COUNTER_CYCLES);
if (event < 0)
/* CPU has no cycle counter */
reg = setup_perfctr(event, 0 /* value */, LOCAL_EVENT); /* syscall */
rdpmc(reg, start);
.... some code to run ...
rdpmc(reg, end);
free_perfctr(reg); /* syscall */
On other architectures rdpmc would be different of course, but
the rest could be probably similar.
-Andi
next prev parent reply other threads:[~2007-11-14 2:11 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 0:34 [PATCH] fix up perfmon to build on -mm Greg KH
2007-11-07 10:34 ` Stephane Eranian
2007-11-07 17:07 ` Greg KH
2007-11-07 13:42 ` Stephane Eranian
2007-11-07 17:08 ` Greg KH
2007-11-07 17:33 ` Andrew Morton
2007-11-07 17:41 ` Greg KH
2007-11-07 17:50 ` Stephane Eranian
2007-11-07 17:47 ` Greg KH
2007-11-07 17:57 ` Stephane Eranian
2007-11-07 19:53 ` Greg KH
2007-11-07 20:39 ` Stephane Eranian
2007-11-08 15:27 ` Stephane Eranian
2007-11-09 20:06 ` Andrew Morton
2007-11-09 21:38 ` Greg KH
2007-11-10 20:32 ` Andi Kleen
2007-11-13 15:17 ` perfmon2 merge news Robert Richter
2007-11-13 15:35 ` [perfmon2] " William Cohen
2007-11-13 17:55 ` Stephane Eranian
2007-11-13 18:33 ` [perfmon] " William Cohen
2007-11-13 21:13 ` Stephane Eranian
2007-11-13 21:29 ` Andi Kleen
2007-11-13 21:46 ` Stephane Eranian
2007-11-13 21:50 ` Andi Kleen
2007-11-13 22:22 ` Stephane Eranian
2007-11-13 22:25 ` Andi Kleen
2007-11-13 22:58 ` Stephane Eranian
2007-11-14 2:07 ` Andi Kleen [this message]
2007-11-14 13:09 ` Stephane Eranian
2007-11-14 14:24 ` Andi Kleen
2007-11-14 15:44 ` William Cohen
2007-11-14 16:13 ` Stephane Eranian
2007-11-14 18:53 ` Philippe Elie
2007-11-14 19:15 ` Andi Kleen
2007-11-15 0:07 ` Stephane Eranian
2007-11-13 18:47 ` Philip Mucci
2007-11-13 18:59 ` Greg KH
2007-11-13 20:07 ` Andrew Morton
2007-11-13 20:14 ` Greg KH
2007-11-13 20:36 ` Andi Kleen
2007-11-14 0:28 ` Philip Mucci
2007-11-14 1:52 ` Andi Kleen
2007-11-16 9:18 ` Philip Mucci
2007-11-16 15:15 ` Andi Kleen
2007-11-16 16:00 ` Stephane Eranian
2007-11-16 16:28 ` Andi Kleen
2007-11-16 17:13 ` William Cohen
2007-11-16 21:56 ` Stephane Eranian
2007-11-16 17:36 ` Stephane Eranian
2007-11-16 17:51 ` dean gaudet
2007-11-17 0:29 ` David Miller
2007-11-17 1:07 ` Greg KH
2007-11-16 20:16 ` Philip Mucci
2007-11-17 0:15 ` David Miller
[not found] ` <1d7226b10711161713j675341b7wdb4f050c59a8be0a@mail.gmail.com>
2007-11-17 1:25 ` Greg KH
[not found] ` <1d7226b10711161748n39b7f195q796d85282ef66134@mail.gmail.com>
2007-11-17 2:13 ` Greg KH
2007-11-14 7:24 ` [perfmon] Re: [perfmon2] " Paul Mackerras
2007-11-14 7:40 ` Andrew Morton
2007-11-14 10:38 ` Christoph Hellwig
2007-11-14 10:43 ` Paul Mackerras
2007-11-14 11:00 ` Christoph Hellwig
2007-11-14 11:12 ` David Miller
2007-11-14 11:14 ` David Miller
2007-11-14 11:44 ` Paul Mackerras
2007-11-13 23:49 ` Nick Piggin
2007-11-14 11:58 ` David Miller
2007-11-14 0:25 ` Nick Piggin
2007-11-14 21:30 ` Paul Mackerras
2007-11-14 10:17 ` Nick Piggin
2007-11-14 22:56 ` Chuck Ebbert
2007-11-14 11:03 ` Nick Piggin
2007-11-14 11:52 ` David Miller
2007-11-14 12:03 ` Paul Mackerras
2007-11-14 12:07 ` David Miller
2007-11-14 0:28 ` Nick Piggin
2007-11-14 21:50 ` Paul Mackerras
2007-11-14 23:03 ` David Miller
2007-11-14 23:12 ` Paul Mackerras
2007-11-14 23:21 ` David Miller
2007-11-15 1:11 ` Paul Mackerras
2007-11-15 1:27 ` David Miller
2007-11-15 2:34 ` Paul Mackerras
2007-11-15 7:48 ` Herbert Xu
2007-11-15 8:19 ` Andi Kleen
2007-11-19 13:08 ` David Miller
2007-11-19 20:53 ` Stephane Eranian
2007-11-20 0:55 ` David Miller
2007-11-19 21:43 ` Paul Mackerras
2007-11-19 22:48 ` Stephane Eranian
2007-11-20 0:53 ` David Miller
2007-12-13 16:00 ` Stephane Eranian
2007-12-14 19:12 ` Frank Ch. Eigler
2007-12-14 21:07 ` Stephane Eranian
2007-12-15 15:54 ` Frank Ch. Eigler
2007-11-15 8:29 ` [perfmon] " Stephane Eranian
2007-11-14 13:51 ` Stephane Eranian
2007-11-14 11:39 ` Paul Mackerras
2007-11-14 11:52 ` David Miller
2007-11-14 13:47 ` Stephane Eranian
2007-11-14 12:38 ` Andi Kleen
2007-11-14 14:13 ` Stephane Eranian
2007-11-14 14:26 ` Andi Kleen
2007-11-15 0:23 ` Paul Mackerras
2007-11-14 19:48 ` David Miller
2007-11-15 4:20 ` dean gaudet
2007-11-15 4:47 ` Paul Mackerras
2007-11-15 5:14 ` dean gaudet
2007-11-15 8:53 ` Stephane Eranian
2007-11-15 17:01 ` [perfmon2] [perfmon] " Dan Terpstra
2007-11-13 21:33 ` [perfmon] Re: [perfmon2] " Stephane Eranian
2007-11-13 21:45 ` Greg KH
2007-11-13 22:27 ` Christoph Hellwig
2007-11-13 20:42 ` Andi Kleen
2007-11-13 18:32 ` Stephane Eranian
2007-11-13 22:29 ` Christoph Hellwig
2007-11-16 18:25 ` PMC core internal API design Mathieu Desnoyers
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=20071114020702.GB20365@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=akpm@osdl.org \
--cc=eranian@hpl.hp.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.richter@amd.com \
--cc=wcohen@redhat.com \
/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
Powered by JetHome