From: Karel Zak <kzak@redhat.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: nacc@linux.vnet.ibm.com, util-linux@vger.kernel.org
Subject: Re: [RFC][PATCH 1/1] lscpu: Print physical cpu information
Date: Wed, 25 Nov 2015 10:17:15 +0100 [thread overview]
Message-ID: <20151125091715.GE4955@ws.net.home> (raw)
In-Reply-To: <1448402285-15621-1-git-send-email-sukadev@linux.vnet.ibm.com>
On Tue, Nov 24, 2015 at 01:58:05PM -0800, Sukadev Bhattiprolu wrote:
> Appreciate comments on the proposal including following:
>
> - Should we instead display the physical information unconditionally?
yes
> Maybe add '--system' or '--no-physical' to suppress the physical
> topology info?
>
> - Should we ignore (as this patch does) or fail if '--physical'
> is specified on yet unsupported architectures?
I have originally thought that --physical will overwrite the current
output (e.g. "Sockets:"). If we add information from librtas as
additional fields (e.g. "Physical sockets:") than maybe we don't need
the option --physical at all, and all we need is to describe all
(difference between system/physical) in docs.
> +static void read_physical_info_powerpc(struct lscpu_desc *desc)
> +{
> + char buf[4096];
buf[BUFSIZ]
...
> static void
> read_basicinfo(struct lscpu_desc *desc, struct lscpu_modifier *mod)
> {
> @@ -506,6 +555,9 @@ read_basicinfo(struct lscpu_desc *desc, struct lscpu_modifier *mod)
> desc->dispatching = path_read_s32(_PATH_SYS_CPU "/dispatching");
> else
> desc->dispatching = -1;
>
you should not read information from rtas when lscpu is running in
shapshot mode ("snapshot" means that we read info from /sys and /proc
dump rather than from a real system; we use it for regression tests).
if (mod->system == SYSTEM_ALIVE)
read_physical_info_powerpc(desc);
and mod->physical will be probably unnecessary if the physical information
will be printed unconditionally ;-)
> + if (mod->physical)
> + read_physical_info_powerpc(desc);
> }
Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-11-25 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 21:58 [RFC][PATCH 1/1] lscpu: Print physical cpu information Sukadev Bhattiprolu
2015-11-25 9:17 ` Karel Zak [this message]
2015-11-25 20:09 ` Sukadev Bhattiprolu
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=20151125091715.GE4955@ws.net.home \
--to=kzak@redhat.com \
--cc=nacc@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=util-linux@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox