This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [RFC PATCH linux-2.6.18-xen] pciback: clean up (MSI-X ve

To: "Laszlo Ersek" <lersek@xxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC PATCH linux-2.6.18-xen] pciback: clean up (MSI-X vec, entrynr) list when resetting PCI device
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 01 Jun 2011 17:07:36 +0100
Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>, Drew Jones <drjones@xxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 01 Jun 2011 09:10:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DE65A53.9020909@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4DE60EF8.5060902@xxxxxxxxxx> <4DE653290200007800044DE4@xxxxxxxxxxxxxxxxxx> <4DE648C3.40602@xxxxxxxxxx> <4DE66FDF0200007800044EC7@xxxxxxxxxxxxxxxxxx> <4DE65A53.9020909@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 01.06.11 at 17:27, Laszlo Ersek <lersek@xxxxxxxxxx> wrote:
> Or, as you say above, the guest's generic MSI-X massaging PCI code could 
> be modified.

The host's.

> We didn't want to leave this to the guest, however. It's not that I 
> intentionally try to postpone the cleanup until after the domain has 
> vanished; it's rather the domU can't be expected / trusted to do the 
> cleanup itself in all cases.

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).


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>