From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [RFC PATCH linux-2.6.18-xen] pciback: clean up (MSI-X vec, entrynr) list when resetting PCI device Date: Wed, 01 Jun 2011 18:27:17 +0200 Message-ID: <4DE66865.4000502@redhat.com> References: <1818654223.418514.1306945550994.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1818654223.418514.1306945550994.JavaMail.root@zmail01.collab.prod.int.phx2.redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andrew Jones Cc: xen-devel@lists.xensource.com, Laszlo Ersek , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 06/01/2011 06:25 PM, Andrew Jones wrote: > > When the guest is dead, the host has to take care. As long as the > > guest is alive, it ought to be responsible (and the host simply must > > not get in the way). > > As Laszlo stated, we can leave the security concerns out since we're > talking about pci passthrough for pv guests. So malicious guests aside, > there's still the scenario where a proprietary, broken (but works on > bare-metal) driver comes along and messes things up. You then try to > either reboot and re-passthrough to that same guest or even to a > different guest that doesn't have a broken driver, but it now fails. Or, > IOW, the host should guarantee that no domu (even ones running > proprietary, broken code) can't ruin the day of another domu (or even > its own day on a subsequent boot). I think you're in violent agreement here.