linux-kernel - Re: [PATCH] perf tools: Add support for pinned modifier

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1374756806.12885.14.camel@concordia>
Date:	Thu, 25 Jul 2013 22:53:26 +1000
From:	Michael Ellerman <michael@...erman.id.au>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, acme@...stprotocols.net,
	mingo@...hat.com, Paul Mackerras <paulus@...ba.org>,
	Anton Blanchard <anton@...ba.org>
Subject: Re: [PATCH] perf tools: Add support for pinned modifier

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/