Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
>>> On 27.07.12 at 12:21, Ian Campbell wrote: > I was actually think of the issue with 32 bit PV guests accessing MFN > space > 160G, even if they are themselves small, which is a separate > concern. That can be made work if really needed, but not via the mechanism we're talking about here. The

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Ian Campbell
On Fri, 2012-07-27 at 11:17 +0100, Jan Beulich wrote: > >>> On 27.07.12 at 12:00, Ian Campbell wrote: > > On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: > >> >>> On 26.07.12 at 22:47, Konrad Rzeszutek Wilk > >> >>> wrote: > >> > 2). Allocate a new array, copy the existing P2M into it, >

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
>>> On 27.07.12 at 12:00, Ian Campbell wrote: > On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: >> >>> On 26.07.12 at 22:47, Konrad Rzeszutek Wilk >> >>> wrote: >> > 2). Allocate a new array, copy the existing P2M into it, >> > revector the P2M tree to use that, and return the old >>

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Ian Campbell
On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: > >>> On 26.07.12 at 22:47, Konrad Rzeszutek Wilk > >>> wrote: > > 2). Allocate a new array, copy the existing P2M into it, > > revector the P2M tree to use that, and return the old > > P2M to the memory allocate. This has the

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
>>> On 26.07.12 at 22:47, Konrad Rzeszutek Wilk wrote: > 2). Allocate a new array, copy the existing P2M into it, > revector the P2M tree to use that, and return the old > P2M to the memory allocate. This has the advantage that > it sets the stage for using XEN_ELF_NOTE_INIT_P2M >

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
On 26.07.12 at 22:47, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: 2). Allocate a new array, copy the existing P2M into it, revector the P2M tree to use that, and return the old P2M to the memory allocate. This has the advantage that it sets the stage for using

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Ian Campbell
On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: On 26.07.12 at 22:47, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: 2). Allocate a new array, copy the existing P2M into it, revector the P2M tree to use that, and return the old P2M to the memory allocate. This has

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
On 27.07.12 at 12:00, Ian Campbell ian.campb...@citrix.com wrote: On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: On 26.07.12 at 22:47, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: 2). Allocate a new array, copy the existing P2M into it, revector the P2M tree to use

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Ian Campbell
On Fri, 2012-07-27 at 11:17 +0100, Jan Beulich wrote: On 27.07.12 at 12:00, Ian Campbell ian.campb...@citrix.com wrote: On Fri, 2012-07-27 at 08:34 +0100, Jan Beulich wrote: On 26.07.12 at 22:47, Konrad Rzeszutek Wilk konrad.w...@oracle.com wrote: 2). Allocate a new array, copy the

Re: [Xen-devel] [RFC PATCH] Boot PV guests with more than 128GB (v1) for 3.7

2012-07-27 Thread Jan Beulich
On 27.07.12 at 12:21, Ian Campbell ian.campb...@citrix.com wrote: I was actually think of the issue with 32 bit PV guests accessing MFN space 160G, even if they are themselves small, which is a separate concern. That can be made work if really needed, but not via the mechanism we're talking