All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: namhyung@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: perf: header: Regression
Date: Mon, 22 Oct 2012 15:11:42 +0200	[thread overview]
Message-ID: <20121022131141.GA11455@turtle.usersys.redhat.com> (raw)


The patch series that contains 7e94cfcc9d20 regresses the
header output. Below is a diff of info from before and
after the series

58,64c58,59
< # node1 meminfo  : total = 16777216 kB, free = 15712440 kB
< # node1 cpu list : 2,6,10,14,18,22,26,30
< # node2 meminfo  : total = 16777216 kB, free = 16299132 kB
< # node2 cpu list : 1,5,9,13,17,21,25,29
< # node3 meminfo  : total = 16777216 kB, free = 16217192 kB
< # node3 cpu list : 3,7,11,15,19,23,27,31
< # pmu mappings: cpu = 4, software = 1, tracepoint = 2, uncore_bbox_0 =
15, uncore_bbox_1 = 16, uncore_cbox_0 = 7, uncore_cbox_1 = 8,
uncore_cbox_2 = 9, uncore_cbox_3 = 10, uncore_cbox_4 = 11, uncore_cbox_5 =
12, uncore_cbox_6 = 13, uncore_cbox_7 = 14, uncore_mbox_0 = 19,
uncore_mbox_1 = 20, uncore_rbox_0 = 21, uncore_rbox_1 = 22, uncore_sbox_0
= 17, uncore_sbox_1 = 18, breakpoint = 5, uncore_ubox = 6, uncore_wbox =
23
---
> # numa topology : not available
> # pmu mappings: cpu = 4, software = 1, tracepoint = 2, uncore_bbox_0 =
15, uncore_bbox_1 = 16, uncore_cbox_0 = 7, uncore_cbox_1 = 8,
uncore_cbox_2 = 9, uncore_cbox_3 = 10, uncore_cbox_4 = 11, uncore_cbox_5 =
12, uncore_cbox_6 = 13, uncore_cbox_7 = 14, uncore_mbox_0 = 19# pmu
mappings: unable to read

As can be seen in the diff, before the series we had complete
numa info and pmu mappings info. After we get 

"# numa topology : not available" and "# pmu
mappings: unable to read"

Drew

             reply	other threads:[~2012-10-22 13:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 13:11 Andrew Jones [this message]
2012-10-23  2:07 ` perf: header: Regression Namhyung Kim
2012-10-23  7:27   ` Andrew Jones
2012-10-23 13:44     ` [PATCH 1/2] perf header: Fix numa topology printing Namhyung Kim
2012-10-23 13:44       ` [PATCH 2/2] perf tools: Fix strbuf_addf() when the buffer needs to grow Namhyung Kim
2012-10-24  7:49         ` Andrew Jones
2012-11-14  6:28         ` [tip:perf/urgent] " tip-bot for Namhyung Kim
2012-10-23 14:12       ` [PATCH 1/2] perf header: Fix numa topology printing Andrew Jones
2012-10-24  7:00         ` Namhyung Kim
2012-10-24  7:49           ` Andrew Jones
2012-10-29 15:17             ` Namhyung Kim
2012-11-14  6:27       ` [tip:perf/urgent] " tip-bot for Namhyung Kim

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=20121022131141.GA11455@turtle.usersys.redhat.com \
    --to=drjones@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    /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.