From: Xiao Yang <yangx.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] Question about Cpus_allowed_list
Date: Tue, 17 Jul 2018 17:41:21 +0800 [thread overview]
Message-ID: <5B4DB9C1.1040209@cn.fujitsu.com> (raw)
Hi,
With Intel(R) Core(TM)2 Duo CPU E7500, running cpuset_hotplug_test.sh
always got the following error:
-------------------------------------------------------------------------------------
cpuset_hotplug 1 TFAIL: task's allowed list isn't expected.(Result: 0-3,
Expect: 0-1)
-------------------------------------------------------------------------------------
No matter what is the number of cpu processors from /proc/cpuinfo
(specify 2 or 1 by offlining cpu),
the Cpus_allowed_list from /proc/<pid>/status is always 0-3.
Simple steps to reproduce this issue:
# /bin/cat /dev/zero > /dev/null 2>&1 &
[1] 15079
# nproc (or cat /proc/cpuinfo | grep processor | wc -l)
2
# cat /proc/15079/status | grep Cpus_allowed_list
Cpus_allowed_list: 0-3
We also tested cpuset_hotplug_test.sh with Core(TM) i3 CPU and Core(TM)
i5 CPU, it showed the
same Cpus_allowed_list as the number of cpu processors as expected.
Is this a known issue on Core(TM)2 Duo CPU, should we use taskset
command to change Cpus_allowed_list?
Thanks,
Xiao Yang
reply other threads:[~2018-07-17 9:41 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=5B4DB9C1.1040209@cn.fujitsu.com \
--to=yangx.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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.