From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [RFC PATCH] perfcounters: provide expansion room in the ABI
Date: Wed, 4 Mar 2009 11:49:45 +0100 [thread overview]
Message-ID: <20090304104945.GB4879@elte.hu> (raw)
In-Reply-To: <18862.19599.929591.3109@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> Impact: ABI change
>
> This expands several fields in the perf_counter_hw_event
> struct and adds a "flags" argument to the perf_counter_open
> system call, in order that features can be added in future
> without ABI changes.
>
> In particular the record_type field is expanded to 64 bits,
> and the space for flag bits has been expanded from 32 to 64
> bits.
>
> This also adds some new fields:
>
> * read_format (64 bits) is intended to provide a way to specify what
> userspace wants to get back when it does a read() on a simple
> (non-interrupting) counter;
>
> * exclude_idle (1 bit) provides a way for userspace to ask that events
> that occur when the cpu is idle be excluded;
>
> * extra_config_len will provide a way for userspace to supply an
> arbitrary amount of extra machine-specific PMU configuration data
> immediately following the perf_counter_hw_event struct, to allow
> sophisticated users to program things such as instruction matching
> CAMs and address range registers;
>
> * __reserved_3 and __reserved_4 provide space for future expansion.
>
> Signed-off-by: Paul Mackerras <paulus@samba.org>
> ---
> This should provide plenty of room for future expansion, in fact maybe
> it's a little over the top.
Yeah - but i think it does not hurt to be defensive when it
comes to ABI extensibility.
Your changes look very good to me.
> Ingo, if this looks OK, you can pull it from the rfc branch of my
> perfcounters.git tree at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/perfcounters.git rfc
>
> include/linux/perf_counter.h | 12 +++++++++---
> include/linux/syscalls.h | 2 +-
> kernel/perf_counter.c | 10 +++++++---
> 3 files changed, 17 insertions(+), 7 deletions(-)
Pulled into tip:perfcounters/core, thanks Paul!
Ingo
next prev parent reply other threads:[~2009-03-04 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 9:40 Paul Mackerras
2009-03-04 10:49 ` Ingo Molnar [this message]
2009-03-04 22:46 ` Paul Mackerras
2009-03-05 10:07 ` Ingo Molnar
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=20090304104945.GB4879@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--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®