From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: george.dunlap@eu.citrix.com, xen-devel@lists.xensource.com
Subject: xc_tbuf_set_cpu_mask & xentrace & cpu_mask
Date: Tue, 11 Mar 2014 10:10:53 -0400 [thread overview]
Message-ID: <20140311141053.GA13345@phenom.dumpdata.com> (raw)
Hey George,
I recently got my hands on a machine with 240CPUS (ugh!) and wanted to play
a bit on figuring out what is happening with certain guests if I partition
it the box in nice per-socket pools.
While I was setting this up I started looking at xentrace and figuring out
what to set the cpu_mask and then I realized it is limited to 64 cpus. Or
at least that is my understanding (with not enough sleep - maybe I am
missing something?).
I see this xc_tbuf_set_cpu_mask which accepts a 32-bit mask and in the
code I see:
sysctl.u.tbuf_op.cpu_mask.nr_bits = sizeof(bytemap) * 8;
where bytemap is a uint8. That all reads to me as a 64-bit mask (thought
we only pass in a 32-bit mask?). Seems like two bugs there.
The hypervisor part is OK - it does the right thing.
Am I reading the code right? And if so, do you have some patches in
your backlog that had addressed this by any chance?
Thanks.
reply other threads:[~2014-03-11 14:10 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=20140311141053.GA13345@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=george.dunlap@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.