[Xen-devel] [PATCH for-next v2 06/10] x86/domain: push some code down to hvm_domain_initialise

2017-04-25 Thread Wei Liu
We want to have a single entry point to initialise hvm guest. Now the timing to set hap bit and create per domain mapping is deferred, but that's not a problem. No functional change. Signed-off-by: Wei Liu --- v2: 1. reorder things to avoid rename labels 2. add config to hvm_domain_initialise

Re: [Xen-devel] [PATCH for-next v2 06/10] x86/domain: push some code down to hvm_domain_initialise

2017-04-25 Thread Andrew Cooper
On 25/04/17 14:52, Wei Liu wrote: > We want to have a single entry point to initialise hvm guest. Now the > timing to set hap bit and create per domain mapping is deferred, but > that's not a problem. This wording is a little odd to read. How about "To do this, the setting of hap_enabled and cre

Re: [Xen-devel] [PATCH for-next v2 06/10] x86/domain: push some code down to hvm_domain_initialise

2017-04-25 Thread Wei Liu
On Tue, Apr 25, 2017 at 03:15:03PM +0100, Andrew Cooper wrote: > On 25/04/17 14:52, Wei Liu wrote: > > We want to have a single entry point to initialise hvm guest. Now the > > timing to set hap bit and create per domain mapping is deferred, but > > that's not a problem. > > This wording is a lit