mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, acme@ghostprotocols.net,
	mingo@redhat.com, Paul Mackerras <paulus@samba.org>,
	Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH] perf tools: Add support for pinned modifier
Date: Thu, 25 Jul 2013 22:53:26 +1000	[thread overview]
Message-ID: <1374756806.12885.14.camel@concordia> (raw)
In-Reply-To: <20130725110447.GS27075@twins.programming.kicks-ass.net>

On Thu, 2013-07-25 at 13:04 +0200, Peter Zijlstra wrote:
> On Wed, Jul 24, 2013 at 12:26:42PM +1000, Michael Ellerman wrote:
> > 
> > I would have used "p" obviously, but that's taken. Are folks happy that
> > "P" is sufficiently different from "p"? I couldn't think of anything
> > better.
> 
> I've seen proposals where 'P' is used for the max 'p' level :/

Hmm, OK.

So 'p' is for precise, which maps onto a 2 bit field in
perf_event_attr.precise_ip.

No 'p' modifier means precise_ip = 0, so the max value of 3 would be
'ppp' right?

We don't use 'p' so I have no idea how often it's used and whether
typing 'ppp' is going to be a major pain for people.

> But yes, vexing situation. 

Quite. Nothing jumps out as an obvious alternative, including any of the
symbols.

So how about 'D'.

Because it makes a smiley face:

 $ perf stat -e cycles:D

And having perf smile at you can't be a bad thing.

cheers




      reply	other threads:[~2013-07-25 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  2:26 Michael Ellerman
2013-07-25 11:04 ` Peter Zijlstra
2013-07-25 12:53   ` Michael Ellerman [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=1374756806.12885.14.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=acme@ghostprotocols.net \
    --cc=anton@samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    /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®