From: Ryan Harper <ryanh@us.ibm.com>
To: "Carb, Brian A" <Brian.Carb@unisys.com>
Cc: xen-devel@lists.xensource.com, "McAfee,
Tommie M" <Tommie.McAfee@unisys.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: Unable to set dom0 vcpu to 1
Date: Mon, 12 Jun 2006 10:50:02 -0500 [thread overview]
Message-ID: <20060612155002.GC1694@us.ibm.com> (raw)
In-Reply-To: <B05D2E415E8CC94897BB44233D14EE68041AAB74@USTR-EXCH5.na.uis.unisys.com>
* Carb, Brian A <Brian.Carb@unisys.com> [2006-06-12 10:44]:
> Thanks Ryan. We've experienced the wait as well (we contributed the
> timeout loop in changeset 10043 for xm-test
> 01_enforce_dom0_cpus_basic_pos). For some reason, though, vcpu-set is
> not releasing procs above #7, even when we wait a long time.
There was a recent patch dealing with hotplug cpu and rcu sent to the
list by Harry Butterworth. I think it has been committed yet but you
will probably want to try again with that patch.
--
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-06-12 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 15:43 Unable to set dom0 vcpu to 1 Carb, Brian A
2006-06-12 15:50 ` Ryan Harper [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 15:11 Carb, Brian A
2006-06-15 16:16 ` Ryan Harper
2006-06-08 21:20 Apparao, Padmashree K
2006-06-12 19:06 ` Pablo Montesinos
2006-06-08 21:15 Subrahmanian, Raj
2006-06-08 21:03 Apparao, Padmashree K
2006-06-08 20:11 Carb, Brian A
2006-06-12 15:11 ` 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=20060612155002.GC1694@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=Brian.Carb@unisys.com \
--cc=Bruce.Vessey@unisys.com \
--cc=KRYSANS@unisys.com \
--cc=Tommie.McAfee@unisys.com \
--cc=aravindh.puthiyaparambil@unisys.com \
--cc=raj.subrahmanian@unisys.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.