Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2016-07-21 Thread Boris Ostrovsky
On 07/21/2016 10:14 AM, Konrad Rzeszutek Wilk wrote: > On Fri, Jul 10, 2015 at 02:57:51PM -0400, Konrad Rzeszutek Wilk wrote: >> On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote: >>> When Xen migrates an HVM guest, by default its shared_info can >>> only hold up to 32 CPUs. As

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2016-07-21 Thread Konrad Rzeszutek Wilk
On Fri, Jul 10, 2015 at 02:57:51PM -0400, Konrad Rzeszutek Wilk wrote: > On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote: > > When Xen migrates an HVM guest, by default its shared_info can > > only hold up to 32 CPUs. As such the hypercall > > VCPUOP_register_vcpu_info was int

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-12-01 Thread Konrad Rzeszutek Wilk
On Fri, Nov 13, 2015 at 02:49:22PM +, Ian Campbell wrote: > On Fri, 2015-11-13 at 09:42 -0500, Konrad Rzeszutek Wilk wrote: > > On Thu, Nov 12, 2015 at 04:40:06PM +, Ian Campbell wrote: > > > On Fri, 2015-07-10 at 14:57 -0400, Konrad Rzeszutek Wilk wrote: > > > > On Fri, Jul 10, 2015 at 02:

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-11-13 Thread Ian Campbell
On Fri, 2015-11-13 at 09:42 -0500, Konrad Rzeszutek Wilk wrote: > On Thu, Nov 12, 2015 at 04:40:06PM +, Ian Campbell wrote: > > On Fri, 2015-07-10 at 14:57 -0400, Konrad Rzeszutek Wilk wrote: > > > On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk > > > wrote: > > > > When Xen mig

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-11-13 Thread Konrad Rzeszutek Wilk
On Thu, Nov 12, 2015 at 04:40:06PM +, Ian Campbell wrote: > On Fri, 2015-07-10 at 14:57 -0400, Konrad Rzeszutek Wilk wrote: > > On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote: > > > When Xen migrates an HVM guest, by default its shared_info can > > > only hold up to 32 CP

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-11-12 Thread Ian Campbell
On Fri, 2015-07-10 at 14:57 -0400, Konrad Rzeszutek Wilk wrote: > On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote: > > When Xen migrates an HVM guest, by default its shared_info can > > only hold up to 32 CPUs. As such the hypercall > > VCPUOP_register_vcpu_info was introduced

Re: [Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-07-10 Thread Konrad Rzeszutek Wilk
On Fri, Jul 10, 2015 at 02:37:46PM -0400, Konrad Rzeszutek Wilk wrote: > When Xen migrates an HVM guest, by default its shared_info can > only hold up to 32 CPUs. As such the hypercall > VCPUOP_register_vcpu_info was introduced which allowed us to > setup per-page areas for VCPUs. This means we can

[Xen-devel] [PATCH] xen/pvhvm: Support more than 32 VCPUs when migrating (v3).

2015-07-10 Thread Konrad Rzeszutek Wilk
When Xen migrates an HVM guest, by default its shared_info can only hold up to 32 CPUs. As such the hypercall VCPUOP_register_vcpu_info was introduced which allowed us to setup per-page areas for VCPUs. This means we can boot PVHVM guest with more than 32 VCPUs. During migration the per-cpu structu