From: Prarit Bhargava <prarit@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: nhorman@redhat.com, Len Brown <len.brown@intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 0/7] turbostat, Fix AMD output by making turbostat aware of nodes
Date: Wed, 19 Jul 2017 08:36:43 -0400 [thread overview]
Message-ID: <bea2fe5c-1aba-1ccb-a103-223d38ca9d7e@redhat.com> (raw)
In-Reply-To: <1500238203-14507-1-git-send-email-prarit@redhat.com>
Forgot to cc Len at his kernel.org address ...
P.
On 07/16/2017 04:49 PM, Prarit Bhargava wrote:
> AMD family processors do not show all cores in the output of turbostat. This
> occurs because AMD has multiple nodes per socket and enumerates cores
> within each node from 0. For example, socket 0 may have two nodes (0 and 1)
> and those nodes both have cores enumerated from 0 through 7. turbostat cannot
> handle this configuration, and as a result only shows 1/2 the cores in its
> output.
>
> This patchset makes turbostate aware of nodes. It has been tested on
> various AMD and Intel systems and no issues have been found.
>
> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
> Cc: Len Brown <len.brown@intel.com>
>
> Prarit Bhargava (7):
> turbostat: set max_num_cpus equal to the cpumask length
> turbostat: Fix node and siblings lookup data
> turbostat: Calculate additional node information for a
> turbostat: track thread ID in cpu_topology
> turbostat: rename num_cores_per_pkg to num_cores_per_node
> turbostat: remove num_ from cpu_topology struct
> turbostat: add node information into turbostat calculations
>
> tools/power/x86/turbostat/turbostat.c | 419 +++++++++++++++++++++-------------
> 1 file changed, 259 insertions(+), 160 deletions(-)
>
prev parent reply other threads:[~2017-07-19 12:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 20:49 Prarit Bhargava
2017-07-16 20:49 ` [PATCH 1/7] turbostat: set max_num_cpus equal to the cpumask length Prarit Bhargava
2017-07-16 20:49 ` [PATCH 2/7] turbostat: Fix node and siblings lookup data Prarit Bhargava
2017-07-16 20:49 ` [PATCH 3/7] turbostat: Calculate additional node information for a package Prarit Bhargava
2017-07-16 20:50 ` [PATCH 4/7] turbostat: track thread ID in cpu_topology Prarit Bhargava
2017-07-16 20:50 ` [PATCH 5/7] turbostat: rename num_cores_per_pkg to num_cores_per_node Prarit Bhargava
2017-07-16 20:50 ` [PATCH 6/7] turbostat: remove num_ from cpu_topology struct Prarit Bhargava
2017-07-16 20:50 ` [PATCH 7/7] turbostat: add node information into turbostat calculations Prarit Bhargava
2017-07-19 12:36 ` Prarit Bhargava [this message]
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=bea2fe5c-1aba-1ccb-a103-223d38ca9d7e@redhat.com \
--to=prarit@redhat.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®