Re: [Xen-devel] [PATCH v11 03/12] xen/pvh: Early bootup changes in PV code.

2013-12-18 Thread Stefano Stabellini
On Wed, 18 Dec 2013, Konrad Rzeszutek Wilk wrote: > > If so, does it make sense to check for it at run time too? > > > > I think I might as well rip that out - as that code won't be ever > touched. And perhaps just stash in a BUG with /* PVH: FIXME */? That would be fine. -- To unsubscribe from

Re: [Xen-devel] [PATCH v11 03/12] xen/pvh: Early bootup changes in PV code.

2013-12-18 Thread Konrad Rzeszutek Wilk
On Wed, Dec 18, 2013 at 02:27:08PM +, Stefano Stabellini wrote: > On Tue, 17 Dec 2013, Konrad Rzeszutek Wilk wrote: > > From: Mukesh Rathor > > > > In the bootup code for PVH we can trap cpuid via vmexit, so don't > > need to use emulated prefix call. We also check for vector callback > > ear

Re: [Xen-devel] [PATCH v11 03/12] xen/pvh: Early bootup changes in PV code.

2013-12-18 Thread Stefano Stabellini
On Tue, 17 Dec 2013, Konrad Rzeszutek Wilk wrote: > From: Mukesh Rathor > > In the bootup code for PVH we can trap cpuid via vmexit, so don't > need to use emulated prefix call. We also check for vector callback > early on, as it is a required feature. PVH also runs at default kernel > IOPL. > >

[PATCH v11 03/12] xen/pvh: Early bootup changes in PV code.

2013-12-17 Thread Konrad Rzeszutek Wilk
From: Mukesh Rathor In the bootup code for PVH we can trap cpuid via vmexit, so don't need to use emulated prefix call. We also check for vector callback early on, as it is a required feature. PVH also runs at default kernel IOPL. Finally, pure PV settings are moved to a separate function that a