From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: HVMlite ABI specification DRAFT A Date: Mon, 8 Feb 2016 13:21:22 +0000 Message-ID: <56B89652.5080805@citrix.com> References: <56B38EDE.5090700@citrix.com> <20160205160101.GE94831@deinos.phlegethon.org> <56B4D888.3020107@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aSlku-0008Hm-KV for xen-devel@lists.xenproject.org; Mon, 08 Feb 2016 13:21:28 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini , Andrew Cooper Cc: Wei Liu , Tim Deegan , Paul Durrant , David Vrabel , Jan Beulich , xen-devel , samuel.thibault@ens-lyon.org, Boris Ostrovsky , =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= List-Id: xen-devel@lists.xenproject.org On 08/02/16 12:10, Stefano Stabellini wrote: > On Fri, 5 Feb 2016, Andrew Cooper wrote: >> The current pci-front/back and Qemu-based methods have substantial >> architectural deficiencies, and are incredibly fragile to change. When >> was the last XSA to PCI Passthrough which didn't end up requiring >> further bugfixes to undo the collateral damage? > > What's the problem with the pcifront/pciback model exactly (aside from > being tied to pirqs, but we already had a plan to fix that so that we > could use them on ARM, where we always have a GIC interrupt controller)? The most obvious is that it doesn't work for dom0. David