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


[Xen-devel] [RFC] [PATCH] xen, vtd: Check ownership of a domain context

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] [PATCH] xen, vtd: Check ownership of a domain context using internal structures
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Wed, 27 Jul 2011 11:36:05 +0100
Cc: Jiang Yunhong <yunhong.jiang@xxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Wed, 27 Jul 2011 03:37:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type; bh=Nc/VWIF1UjZVMEBZx+7HWc8Q5BTnffrAhEc19Nv2j2A=; b=KTfjW6C4AkWPaNJNsO3uI/D4fBiUp5sIgwwIf2QLB+/xTiVYd0/ee0j3wiObz0waut xYyI7vJfWuNbvTTY5pscrNItPMhNTQ5OtQgfP0lITYfJnYkoQ6Nv7mDymPXJSVMRHaSU J4a4VG2O9buKGhR1Vl90hAw1rjPerUcO7ySTc=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Keir, Jan, et al:

Can you take a look at this patch to see if you think this is the
right way to solve this problem?

This particular patch is still being tested by the partner who saw the
problem; but a less safe change -- just returning "OK" if the pci
device didn't exist -- did solve the problem.  It seemed like this
check was probably there for a reason, so I wanted to keep it in
place.  (Although the c/s in which this check was introduced,
18906:2941b1a9, only mentioned locking changes, not introduction of
new checks.)


Attachment: vtd-get-context-owner-from-context.diff
Description: application/download

Xen-devel mailing list