lscpu command produces incorrect output with the options -b and -c

All of lore.kernel.org
 help / color / mirror / Atom feed

From: faizan husain <faizanh@linux.vnet.ibm.com>
To: util-linux@vger.kernel.org
Subject: lscpu command produces incorrect output with the options -b and -c
Date: Sun, 05 Aug 2012 16:01:28 +0530	[thread overview]
Message-ID: <501E4B80.1010003@linux.vnet.ibm.com> (raw)

Options for lscpu command are giving incorrect output. As per the man page or help,
'-b' option should limit the output to online CPUs  and
'-c' option should limit the output to offline CPUs.
But we could see the output is same for '-a','-b' and '-c' options.

---Steps to Reproduce---
  [root@mx3650m2 ~]# lscpu -a
...
...
CPU(s):                16
On-line CPU(s) list:   0-5,7-13,15
Off-line CPU(s) list:  6,14
...
...

[root@mx3650m2 ~]# lscpu -b
Architecture:          x86_64
...
...
CPU(s):                16
On-line CPU(s) list:   0-5,7-13,15
Off-line CPU(s) list:  6,14
...
...

[root@mx3650m2 ~]# lscpu -c
...
...
CPU(s):                16
On-line CPU(s) list:   0-5,7-13,15
Off-line CPU(s) list:  6,14
...
...

patch in the next mail fixes this issue.

Thanks
Faizan

                 reply	other threads:[~2012-08-05 10:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=501E4B80.1010003@linux.vnet.ibm.com \
    --to=faizanh@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 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.