From: Jiri Olsa <jolsa@redhat.com>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: acme@kernel.org, jolsa@kernel.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
ak@linux.intel.com
Subject: Re: [PATCH 1/3] perf header: Add die information in CPU topology
Date: Tue, 28 May 2019 21:29:42 +0200 [thread overview]
Message-ID: <20190528192942.GJ10611@krava> (raw)
In-Reply-To: <03a95846-5ccd-bbfa-ec95-b2cb8a83607d@linux.intel.com>
On Tue, May 28, 2019 at 03:06:16PM -0400, Liang, Kan wrote:
>
>
> On 5/28/2019 5:00 AM, Jiri Olsa wrote:
> > On Thu, May 23, 2019 at 01:41:19PM -0700, kan.liang@linux.intel.com wrote:
> >
> > SNIP
> >
> > > diff --git a/tools/perf/util/cputopo.c b/tools/perf/util/cputopo.c
> > > index ece0710..f6e7db7 100644
> > > --- a/tools/perf/util/cputopo.c
> > > +++ b/tools/perf/util/cputopo.c
> > > @@ -1,5 +1,6 @@
> > > // SPDX-License-Identifier: GPL-2.0
> > > #include <sys/param.h>
> > > +#include <sys/utsname.h>
> > > #include <inttypes.h>
> > > #include <api/fs/fs.h>
> > > @@ -8,9 +9,10 @@
> > > #include "util.h"
> > > #include "env.h"
> > > -
> > > #define CORE_SIB_FMT \
> > > "%s/devices/system/cpu/cpu%d/topology/core_siblings_list"
> > > +#define DIE_SIB_FMT \
> > > + "%s/devices/system/cpu/cpu%d/topology/die_cpus_list"
> > > #define THRD_SIB_FMT \
> > > "%s/devices/system/cpu/cpu%d/topology/thread_siblings_list"
> > > #define NODE_ONLINE_FMT \
> > > @@ -20,7 +22,26 @@
> > > #define NODE_CPULIST_FMT \
> > > "%s/devices/system/node/node%d/cpulist"
> > > -static int build_cpu_topology(struct cpu_topology *tp, int cpu)
> > > +bool check_x86_die_exists(void)
> > > +{
> > > + char filename[MAXPATHLEN];
> > > + struct utsname uts;
> > > +
> > > + if (uname(&uts) < 0)
> > > + return false;
> > > +
> > > + if (strncmp(uts.machine, "x86_64", 6))
> > > + return false;
> > > +
> > > + scnprintf(filename, MAXPATHLEN, DIE_SIB_FMT,
> > > + sysfs__mountpoint(), 0);
> > > + if (access(filename, F_OK) == -1)
> > > + return false;
> > > +
> > > + return true;
> > > +}
> >
> > we could rename this to:
> >
> > static bool has_die(void)
> > {
> > static bool has_die;
> >
> > if (initialized)
> > return has_die;
> >
> > has_die = ...
> > initialized = true;
> > }
> >
> > and got rid of all those 'has_die' arguments below
>
> Yes, we can rename the function to has_die(). It looks like all the
> 'has_die' arguments can be replaced either.
>
> But why we want a "initialized" here? to cache the value? It looks like we
> only need to call has_die() once.
right, if it's called from one place then it's ok
thanks,
jirka
next prev parent reply other threads:[~2019-05-28 19:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 20:41 [PATCH 1/3] perf header: Add die information in CPU topology kan.liang
2019-05-23 20:41 ` [PATCH 2/3] perf stat: Support per-die aggregation kan.liang
2019-05-28 9:00 ` Jiri Olsa
2019-05-23 20:41 ` [PATCH 3/3] perf header: Rename "sibling cores" to "sibling sockets" kan.liang
2019-05-28 8:59 ` Jiri Olsa
2019-05-28 19:05 ` Liang, Kan
2019-05-28 8:59 ` [PATCH 1/3] perf header: Add die information in CPU topology Jiri Olsa
2019-05-28 8:59 ` Jiri Olsa
2019-05-28 9:00 ` Jiri Olsa
2019-05-28 19:06 ` Liang, Kan
2019-05-28 19:29 ` Jiri Olsa [this message]
2019-05-28 9:00 ` Jiri Olsa
2019-05-28 9:00 ` Jiri Olsa
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=20190528192942.GJ10611@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox