From: Chris Lalancette <clalance@redhat.com>
To: Gabriel Southern <gsouther@gmu.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: VCPU hotplug problem
Date: Mon, 11 Feb 2008 22:42:11 -0500 [thread overview]
Message-ID: <47B11593.3010103@redhat.com> (raw)
In-Reply-To: <7a88c6510802111926n346882cn4f6cfbe3afc06e90@mail.gmail.com>
Gabriel Southern wrote:
> Hello,
>
> I am working on a project using the VCPU hotplug feature in Xen, and I
> think that there is a problem with how Linux is processing CPU hotplug
> events. The problem I have seen is that the /proc/stat file does not
> change the number of CPU entries in response to the: xm vcpu-set
> <domain> <num> command. However, the /proc/cpuinfo file is updated
> correctly.
>
> The reason this is important is that some applications use the
> sysconf(_SC_NPROCESSORS_ONLN) to determine how many threads to run.
> In Linux this function parses the /proc/stat file to determine how
> many processors are available. However, the /proc/stat file is not
> being updated correctly in response to the xm vcpu-set command.
>
> It would be a big help for me if anyone else could test to see if they
> experience the same problem. I'm not sure if this would qualify as a
> problem with Linux or with Xen; however, any ideas for fixing it are
> appreciated as well.
Hm, it would be helpful if you told us what version of Xen you are
running and which kernel you are running. For what it is worth, running
a RHEL-5.1 PV guest on a RHEL-5.1 dom0 (both x86_64) seems to do the
right thing for me; xm vcpu-set <dom> 1 updates both /proc/cpuinfo and
/proc/stat, and xm vcpu-set <dom> 2 updates both again.
Chris Lalancette
next prev parent reply other threads:[~2008-02-12 3:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 3:26 VCPU hotplug problem Gabriel Southern
2008-02-12 3:42 ` Chris Lalancette [this message]
2008-02-12 4:13 ` Gabriel Southern
2008-02-12 7:59 ` Keir Fraser
2008-02-13 2:20 ` Gabriel Southern
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=47B11593.3010103@redhat.com \
--to=clalance@redhat.com \
--cc=gsouther@gmu.edu \
--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.