All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
	peterz@infradead.org, mingo@elte.hu, dsahern@gmail.com,
	robert.richter@amd.com, ak@linux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)
Date: Fri, 23 Sep 2011 12:17:20 +0300	[thread overview]
Message-ID: <CAOJsxLE_kF2O6FrG7bLHtQKFV_D=PB77jP+aWBp1UERKzO4qng@mail.gmail.com> (raw)
In-Reply-To: <CABPqkBSpqNWJVhRh4bKRK5PGcCdZhzsJzyeQ53Mh4_7fVUm+wg@mail.gmail.com>

On Fri, Sep 23, 2011 at 10:03 AM, Pekka Enberg <penberg@cs.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@google.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

  reply	other threads:[~2011-09-23  9:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 12:31 [PATCH] perf: make perf.data more self-descriptive (v5) Stephane Eranian
2011-09-22 15:35 ` David Ahern
2011-09-22 15:40   ` Stephane Eranian
2011-09-22 15:48     ` David Ahern
2011-09-22 21:20 ` Andi Kleen
2011-09-22 21:25   ` Stephane Eranian
2011-09-23  3:26     ` Andi Kleen
2011-09-23  6:28       ` Stephane Eranian
2011-09-23  6:40 ` Pekka Enberg
2011-09-23  7:31   ` Stephane Eranian
2011-09-23  8:03     ` Pekka Enberg
2011-09-23  9:04       ` Stephane Eranian
2011-09-23  9:17         ` Pekka Enberg [this message]
2011-09-23 13:36         ` David Ahern
     [not found]           ` <CABPqkBTuc_jowJx0PqPPhcCuj6B5dqRaQNiZWiyhhHMN+NkLYg@mail.gmail.com>
2011-09-23 14:09             ` David Ahern
2011-09-23 14:22               ` Stephane Eranian
2011-09-23 22:13       ` Valdis.Kletnieks
2011-09-23 10:13 ` Robert Richter

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='CAOJsxLE_kF2O6FrG7bLHtQKFV_D=PB77jP+aWBp1UERKzO4qng@mail.gmail.com' \
    --to=penberg@cs.helsinki.fi \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.