mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Thu, 5 Mar 2009 11:07:48 +0100	[thread overview]
Message-ID: <20090305100748.GB29499@elte.hu> (raw)
In-Reply-To: <18863.1197.527693.75146@drongo.ozlabs.ibm.com>


* Paul Mackerras <paulus@samba.org> wrote:

> Ingo Molnar wrote:
> 
> > > 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!
> 
> Actually, I goofed slightly.  In this bit of the patch:
> 
> @@ -80,10 +81,15 @@ struct perf_counter_hw_event {
>  				exclude_user   :  1, /* don't count user      */
>  				exclude_kernel :  1, /* ditto kernel          */
>  				exclude_hv     :  1, /* ditto hypervisor      */
> +				exclude_idle   :  1, /* don't count when idle */
>  
> -				__reserved_1 : 23;
> +				__reserved_1 : 55;
> +
> 
> the 55 should have been 54 if we want those bitfields to 
> occupy 64 bits.  With 55 there, __reserved_1 will go in the 
> next 64-bit quadword (x86-speak, or doubleword in 
> powerpc-speak).
> 
> Do you think that's worth changing?  If so I'll do a commit 
> changing the 55 to 54.

How about extending it to 118 instead? The creation of a counter 
is a slow path in any case.

	Ingo

      reply	other threads:[~2009-03-05 10:08 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
2009-03-04 22:46   ` Paul Mackerras
2009-03-05 10:07     ` Ingo Molnar [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=20090305100748.GB29499@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®