From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Other PCI devices to mark mark as read-only for dom0 Date: Fri, 22 Jun 2012 11:11:53 +0100 Message-ID: <4FE444E9.8080809@citrix.com> References: <4FE43518.9070106@citrix.com> <1783278186.20120622112436@eikelenboom.it> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1783278186.20120622112436@eikelenboom.it> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sander Eikelenboom Cc: Andre Przywara , Christoph Egger , "Keir (Xen.org)" , Eddie Dong , "xen-devel@lists.xen.org" , Wei Wang , Jan Beulich , "xiantao.zhang@intel.com" List-Id: xen-devel@lists.xenproject.org On 22/06/12 10:24, Sander Eikelenboom wrote: > >> Are there any others I have overlooked, or reasons that dom0 should be >> able to write to these areas? > Make devices specified for pci passthrough be really hidden and "owned" by the hyperviso ? > - which can in turn delegate ownership to a domain (including dom0) > - If a domain is destroyed, the hypervisor resets the device and becomes the owner again instead of dom0 ? Why? Currently this is covered by unbinding the dom0 driver and binding pciback to the device. Well behaved device drivers will not cause problems. This way, the toolstack has control of which domains own what. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900, http://www.citrix.com