From: Paul Mackerras <paulus@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Thomas Gleixner <tglx@linutronix.de>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf_counter: extensible perf_counter_attr
Date: Tue, 9 Jun 2009 19:58:06 +1000 [thread overview]
Message-ID: <18990.12846.941708.201337@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20090609065350.GB16707@elte.hu>
Ingo Molnar writes:
> * Paul Mackerras <paulus@samba.org> wrote:
> > Since this is a user-visible structure, you've just introduced an
> > ABI difference between 32-bit and 64-bit processes, which we've
> > managed to avoid so far. [...]
>
> This is a good point too - handling pointers in ABIs is possible but
> should be avoided as much as possible: it creates the need to
> introduce a compat_sys_perf_counter_open() and doubles the syscall
> table complexity.
>
> Lets do the s/__reserved_1/attr_size ABI i suggested (i outlined
> various properties of it in the previous mail). Agreed?
Yep, sounds good.
We also need a way to allow access to random machine-specific features
that might not be supported in a generic way, such as the instruction
matching CAM on POWER4/PPC970, or (apparently) PEBS. That's what I
had intended exclusive groups + the extra_config_len field to be used
for, but Peter removed extra_config_len...
Paul.
prev parent reply other threads:[~2009-06-09 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 17:25 Peter Zijlstra
2009-06-08 19:02 ` Corey Ashford
2009-06-08 19:51 ` Peter Zijlstra
2009-06-08 21:18 ` Corey Ashford
2009-06-08 21:23 ` Peter Zijlstra
2009-06-08 21:29 ` Corey Ashford
2009-06-08 21:50 ` Ingo Molnar
2009-06-09 0:50 ` Corey Ashford
2009-06-09 6:51 ` Ingo Molnar
2009-06-09 8:13 ` Corey Ashford
2009-06-09 11:53 ` Ingo Molnar
2009-06-09 16:44 ` Corey Ashford
2009-06-09 22:00 ` Ingo Molnar
2009-06-09 23:16 ` Corey Ashford
2009-06-10 0:14 ` Paul Mackerras
2009-06-10 22:06 ` Corey Ashford
2009-06-09 4:17 ` Paul Mackerras
2009-06-09 6:53 ` Ingo Molnar
2009-06-09 9:58 ` Paul Mackerras [this message]
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=18990.12846.941708.201337@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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®