From: Valdis.Kletnieks@vt.edu
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Stephane Eranian <eranian@google.com>,
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 18:13:05 -0400 [thread overview]
Message-ID: <35021.1316815985@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 23 Sep 2011 11:03:20 +0300." <CAOJsxLE1L1ffZmuF+2+vYZMTXyvq00pOcP1xvGJuW0TqxQskrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Thu, Sep 22, 2011 at 3:31 PM, Stephane Eranian <eranian@google.com> wrote:
> # CPU0 sibling cores : 0-3
> # CPU0 sibling threads: 0
> # CPU1 sibling cores : 0-3
> # CPU1 sibling threads: 1
> # CPU2 sibling cores : 0-3
> # CPU2 sibling threads: 2
On Fri, 23 Sep 2011 11:03:20 +0300, Pekka Enberg said:
> 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.
Too bad there's probably no easy way to provide an iterator/metafunction that
describes the CPUs, so it could output
"for n in 0..4095 cpu[n] looks like this:
CPU_n sibling cores: round(n,4)..round(n,4)+3
CPU_n sibling threads: n...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-09-23 22:15 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
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 [this message]
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=35021.1316815985@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--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=penberg@cs.helsinki.fi \
--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.