| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] [PATCH] qemu-xen: fix cpu hotplug
|
To: |
"Liu, Jinsong" <jinsong.liu@xxxxxxxxx> |
|
Subject: |
RE: [Xen-devel] [PATCH] qemu-xen: fix cpu hotplug |
|
From: |
Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> |
|
Date: |
Fri, 3 Sep 2010 11:10:13 +0100 |
|
Cc: |
Christoph Egger <Christoph.Egger@xxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, "Li, Xin" <xin.li@xxxxxxxxx> |
|
Delivery-date: |
Fri, 03 Sep 2010 03:11:27 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<BC00F5384FCFC9499AF06F92E8B78A9E1837FFC160@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<alpine.DEB.2.00.1009021416500.2714@kaball-desktop> <19583.57113.276530.834290@xxxxxxxxxxxxxxxxxxxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E1837FFC067@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <201009030934.03106.Christoph.Egger@xxxxxxx> <BC00F5384FCFC9499AF06F92E8B78A9E1837FFC160@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Alpine 2.00 (DEB 1167 2008-08-23) |
On Fri, 3 Sep 2010, Liu, Jinsong wrote:
> Christoph Egger wrote:
> > On Friday 03 September 2010 08:28:53 Liu, Jinsong wrote:
> >> Ian Jackson wrote:
> >>> Stefano Stabellini writes ("[Xen-devel] [PATCH] qemu-xen: fix cpu
> >>>
> >>> hotplug"):
> >>>> qemu-xen: fix cpu hotplug
> >>>>
> >>>> The current xenstore watch path for a vcpu-set event is wrong and
> >>>> is also wrong the code to parse it. This patch fixes both of them:
> >>>
> >>> Thanks. So it seems you're saying it's completely broken in
> >>> xen-unstable.
> >>
> >> Stabellini, I read your attached patch, it's OK.
> >> In fact, we firstly implemented xenstore watch by same scheme of your
> >> patch, watching each cpu node status:
> >> /local/domain/xx/cpu/yy/availability=offline (online)
> >>
> >> However, we finally didn't use this scheme. We watch 'common' node
> >> instead: /local/domain/xx/cpu in this way, only 1 watch point need.
> >> Considering vcpu number may become more and more in the future (say,
> >> more than 128), it's more simple and reasonable. (Watches can be set
> >> at points in the hierarchy and an individual watch will be triggered
> >> when anything at or below that point in the hierachy changes)
> >
> > Does this scheme allow to say how many cores per cpu exist ?
> >
> > When you run a Windows guest with a license for one cpu socket,
> > then you can use 4 cores. But if one cpu is equal to one socket,
> > then you can't use SMP for the Windows guest.
> >
> > Christoph
> >
>
> Seems this is another story?
>
Yes, the scheme we are talking about regards the communication of vcpu
online and offline to qemu and nothing else.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home