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

[Xen-devel] How does domain (smp) scheduling work?

  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
  • Date: Sat, 1 Oct 2005 19:16:06 +0000
  • Delivery-date: Sat, 01 Oct 2005 19:13:41 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EmDwYMy9n6bvCsSFcAA24LtxiTAA8cxnih/Fb4Z2RGGKjlVGmr1bTh+LyZrCLZuX0Ny/60+gT49ZRZ6EEMp4xIKPGX+vsUqmFO0Y31S6SIQ/Iz68Eg97tChqoNHArj11P2egRreAlm5mkwgeqJ/kbFhbV3HNB9k7kkiXY6h5LKs=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


I'm curious about how the SMP support in Xen works. Is it possible to
have a SMP aware 2 vcpu domain running on both physical processors at
the same time? Can Xen schedule two domains at the same time, one
running on each processor? How about on a hyperthreaded kernel?

If one domain has a run away process (eg. fork loop) or bad device
driver, will it affect the running of other domains? I suspect it
does, as there are no resource guarantees. If I have a SMP or
hyperthreaded machine with uniprocessor domains, will other domains be
scheduled on the 2nd cpu if the first is being hogged by a runaway

Sorry if this has come up before, I've checked google and couldn't
find any answers.


Xen-devel mailing list



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