linux-kernel - Re: [PATCH] perf: make perf.data more self-descriptive (v5)

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: <CAOJsxLE_kF2O6FrG7bLHtQKFV_D=PB77jP+aWBp1UERKzO4qng@mail.gmail.com>
Date:	Fri, 23 Sep 2011 12:17:20 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	linux-kernel@...r.kernel.org, acme@...hat.com,
	peterz@...radead.org, mingo@...e.hu, dsahern@...il.com,
	robert.richter@....com, ak@...ux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)

On Fri, Sep 23, 2011 at 10:03 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
>> Well, sure but it blocks rest of the interesting information too. It seems to me
>> that the CPU information could be truncated to some sane limit by default and
>> introduce a command line option for users that really want to see all of it.

On Fri, Sep 23, 2011 at 12:04 PM, Stephane Eranian <eranian@...gle.com> wrote:
> Ok, so here is a proposal:
> - reorder the info so one liners appear first
> - display the "truncated" info by default (no option)
> - truncated: numa topo, cpu topo, stop after 4 cpus/nodes, print msg
> to hint at -I option
> - use -I to print the extended header info report
>
> That way we do no introduce two options just for the header information.
>
> How about that instead?

Yup, makes sense to me. Up to perf maintainers, of course.

                         Pekka
--
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/