[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] VCPU hotplug problem

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Gabriel Southern" <gsouther@xxxxxxx>
  • Date: Mon, 11 Feb 2008 22:26:21 -0500
  • Delivery-date: Mon, 11 Feb 2008 19:26:42 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=IIvlPHT8EC2GhTYewof7LTJc0LkPj18QT7pfpT4Il0DgEdOUuEY+IS8+rxlMe0P6ztvTCNifCLaScm4M7w5+frnY+2NLlpA19KIeRbgvlLwKTNXZKq5XLbzt7lNSWYwl/I66jvXgkVBaN8QUIIOZ/T1eVNOp1EFvfVEfjHSOafw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


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

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.



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.