From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH RFC] x86/HVM: assume default ioreq servers follow new bufioreq pointer access model Date: Fri, 28 Aug 2015 17:20:29 +0100 Message-ID: <55E08A4D.8090400@citrix.com> References: <55E0A531020000780009DF38@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZVMOY-0001yD-77 for xen-devel@lists.xenproject.org; Fri, 28 Aug 2015 16:20:50 +0000 In-Reply-To: <55E0A531020000780009DF38@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , xen-devel Cc: Ian Jackson , Keir Fraser , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 28/08/15 17:15, Jan Beulich wrote: > There's no way for Xen to know or for such a qemu to tell us. > > Signed-off-by: Jan Beulich > --- > RFC: This implies only patched qemu-trad or ioreq-server-aware > qemu-upstream get used with xen-unstable. Is this reasonable? Patched qemu-trad, yes, as it comes from the same source. Much less certain about qemu-upstream. There is deliberate support to use a distro provided qemu-upstream as opposed to a xen provided one. ~Andrew