>>> On 03.03.17 at 10:41, wrote:
> Long term we want to be able to disentangle PV and HVM code. Move the
> PVH domain builder to a dedicated file. It will later depends on
> CONFIG_HVM or CONFIG_PVH.
>
> This in turn requires exposing a few functions and variables via
>
On Fri, Mar 03, 2017 at 01:39:24PM +, Wei Liu wrote:
> On Fri, Mar 03, 2017 at 11:16:39AM +, Roger Pau Monné wrote:
> > On Fri, Mar 03, 2017 at 09:41:10AM +, Wei Liu wrote:
> > > +++ b/xen/arch/x86/domain_build_pvh.c
> > > @@ -0,0 +1,1097 @@
> > >
On Fri, Mar 03, 2017 at 11:16:39AM +, Roger Pau Monné wrote:
> On Fri, Mar 03, 2017 at 09:41:10AM +, Wei Liu wrote:
> > Long term we want to be able to disentangle PV and HVM code. Move the
> > PVH domain builder to a dedicated file. It will later depends on
> > CONFIG_HVM or CONFIG_PVH.
>
On Fri, Mar 03, 2017 at 09:41:10AM +, Wei Liu wrote:
> Long term we want to be able to disentangle PV and HVM code. Move the
> PVH domain builder to a dedicated file. It will later depends on
> CONFIG_HVM or CONFIG_PVH.
>
> This in turn requires exposing a few functions and variables via
>
Long term we want to be able to disentangle PV and HVM code. Move the
PVH domain builder to a dedicated file. It will later depends on
CONFIG_HVM or CONFIG_PVH.
This in turn requires exposing a few functions and variables via
domain_build.h.
Signed-off-by: Wei Liu
---