From: Ryan Harper <ryanh@us.ibm.com>
To: "Carb, Brian A" <Brian.Carb@unisys.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
Xen-devel@lists.xensource.com, "Krysan,
Susan" <KRYSANS@unisys.com>,
"Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@unisys.com>,
"Subrahmanian, Raj" <raj.subrahmanian@unisys.com>,
"Vessey, Bruce A" <Bruce.Vessey@unisys.com>
Subject: Re: Setting dom0-cpus to 0 doesn't use all cpus asdocumented
Date: Tue, 9 May 2006 11:04:14 -0500 [thread overview]
Message-ID: <20060509160414.GH28945@us.ibm.com> (raw)
In-Reply-To: <B05D2E415E8CC94897BB44233D14EE6803EC099E@USTR-EXCH5.na.uis.unisys.com>
* Carb, Brian A <Brian.Carb@unisys.com> [2006-05-09 10:58]:
> We discovered this when running the xm-test suite. One of the tests
> (01_enforce_dom0_cpus) changes the number of cpus by editing the
> xend-config.sxp file and restarting xend. Should this test be updated to
> use the method Ian suggested, to vary the number of cpus, rather than
> restarting xend?
As Ian said, it is for setting the value when xend starts which is what
the test is about. However, the test should bring dom0 vcpus to the
max and then test enforcement down to 1 rather than assuming that dom0's
current value can be reduced. Or, bail on the test if the current value
of dom0's online vcpus isn't > 2.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2006-05-09 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 15:57 Setting dom0-cpus to 0 doesn't use all cpus asdocumented Carb, Brian A
2006-05-09 16:04 ` Ryan Harper [this message]
2006-05-09 19:43 ` [PATCH] xm-test: update enforce_dom0_cpus testcase Ryan Harper
2006-05-11 12:49 ` Ewan Mellor
-- strict thread matches above, loose matches on Subject: below --
2006-05-09 15:52 Setting dom0-cpus to 0 doesn't use all cpus asdocumented Ian Pratt
2006-05-09 16:01 ` Jan Beulich
2006-05-09 15:05 Ian Pratt
2006-05-09 15:44 ` Ryan Harper
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=20060509160414.GH28945@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=Brian.Carb@unisys.com \
--cc=Bruce.Vessey@unisys.com \
--cc=KRYSANS@unisys.com \
--cc=Xen-devel@lists.xensource.com \
--cc=aravindh.puthiyaparambil@unisys.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=raj.subrahmanian@unisys.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.