linux-kernel - Re: [PATCH v2] perf tools: make -C consistent across commands (for cpu list arg)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111118004139.GA2315@ghostprotocols.net>
Date:	Thu, 17 Nov 2011 22:41:39 -0200
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	David Ahern <dsahern@...il.com>
Cc:	mingo@...e.hu, linux-kernel@...r.kernel.org, peterz@...radead.org,
	fweisbec@...il.com
Subject: Re: [PATCH v2] perf tools: make -C consistent across commands (for
 cpu list arg)

Em Thu, Nov 17, 2011 at 04:10:24PM -0700, David Ahern escreveu:
> On 11/13/2011 11:30 AM, David Ahern wrote:
> > Currently the meaning of -C varies by perf command: for perf-top,
> > perf-stat, perf-record it means cpu list. For perf-report it
> > means comm list. Then perf-annotate, perf-report and perf-script
> > use -c for cpu list.
> > 
> > Fix annotate, report and script to use -C for cpu list to be
> > consistent with top, stat and record. This means report needs
> > to use -c for comm list which does introduce a backward
> > compatibility change.
> 
> Any objections to making this argument consistent? I am waiting to send
> a follow-on patch that adds comm filtering to perf-script.

Its OK for perf/core, I'll apply and try to publish what I have
tomorrow.
 
- Arnaldo
--
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/