Re: [Xen-devel] [PATCH] x86/hvm: don't create a default ioreq server...

2016-12-12 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 12 December 2016 07:54 > To: Paul Durrant > Cc: Andrew Cooper ; xen- > de...@lists.xenproject.org > Subject: Re: [PATCH] x86/hvm: don't create a default ioreq server... > > >>> On 09.12.16 at 18:55, wrote: > > ..

Re: [Xen-devel] [PATCH] x86/hvm: don't create a default ioreq server...

2016-12-11 Thread Jan Beulich
>>> On 09.12.16 at 18:55, wrote: > ...if the domain is not under construction. I think the title will end up misleading this way. How about "x86/hvm: don't unconditionally create a default ioreq server" with "Avoid doing so if the domain is not under construction" as the 1st sentence? As the pat

Re: [Xen-devel] [PATCH] x86/hvm: don't create a default ioreq server...

2016-12-11 Thread Zhang Chen
On 12/10/2016 02:21 AM, Andrew Cooper wrote: On 09/12/16 17:55, Paul Durrant wrote: ...if the domain is not under construction. If upstream QEMU is in use then it will explicitly create an ioreq server rather than implicitly creating the default ioreq server, which is a side-effect of reading

Re: [Xen-devel] [PATCH] x86/hvm: don't create a default ioreq server...

2016-12-09 Thread Andrew Cooper
On 09/12/16 17:55, Paul Durrant wrote: > ...if the domain is not under construction. > > If upstream QEMU is in use then it will explicitly create an ioreq server > rather than implicitly creating the default ioreq server, which is a > side-effect of reading HVM_PARAM_IOREQ_PFN, HVM_PARAM_BUFIOREQ_