WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: follow up to a pciback "pv pci-passthrough co-assig

To: Weidong Han <weidong.han@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: follow up to a pciback "pv pci-passthrough co-assigned problem"
From: 0bo0 <0.bugs.only.0@xxxxxxxxx>
Date: Mon, 25 Jan 2010 08:17:35 -0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 25 Jan 2010 08:17:53 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=YW1IqWp7mbYrlnlFFdzgTziMkQsGlSr+y6tGPXt5wvM=; b=RY9PVGf7c2i9Qi55BteaPBt7KCx1ov+0ljX4ojHaOpQSzCKnRPfiohV31tS/iyj3QL z7oxP7xRKOUEHIlUOKwCIj8yt1N1CfBDyNrPeYNU8ubYsG6T5OwKqKe/mKoEvRCLn3u3 DUsVWwVQ8ufRkOuUIesVaQqhwv76CiEuV/vxk=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=AR43O3Pop1HwG0lg0RCWyy/+LcORGLE3DgKIcr/yvrb/jLGBTQZr7/oUHQXj19ItGO h0samwxnnIMd1bWgvryFunNoH9h8IYino5QFBqItQR5P/8yiKCwAmskZFlxbmLtxdQWx NeUjmV7VRbHuSCmJudTzsy34v9JveBk1+g95U=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B5CF79A.6020002@xxxxxxxxx>
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: <c67eed301001221732s4b6a9a10p4be4182ecf831b6a@xxxxxxxxxxxxxx> <20100123164850.GT2861@xxxxxxxxxxx> <c67eed301001230936o37dc63c2le944386cbaa02ff3@xxxxxxxxxxxxxx> <20100123174333.GW2861@xxxxxxxxxxx> <c67eed301001230945i45b8bb22q8cc3ded555cd7959@xxxxxxxxxxxxxx> <c67eed301001230954i6e9098fdwde189d429b8591fa@xxxxxxxxxxxxxx> <20100123175705.GY2861@xxxxxxxxxxx> <c67eed301001230958x2b22a5cs45df42cb956f75ed@xxxxxxxxxxxxxx> <c67eed301001231015v2c572d2fxb4a221157f3f1bfd@xxxxxxxxxxxxxx> <4B5CF79A.6020002@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
hi,

On Sun, Jan 24, 2010 at 5:44 PM, Weidong Han <weidong.han@xxxxxxxxx> wrote:
> I think this is not a bug. pls note ...

(snip)

Ack'd, even if the limitations are not fully understood:-/

> or you
> can set "pci-passthrough-strict-check no" in /etc/xen/xend-config.sxp and
> restart xend to loose the check in xend, but in this way you should be aware
> of potential issues (e.g. assigned device doesn't work).

sure.  would it not be reasonable to have a similar config-file option
in xen 3.x -- with similar warnings etc -- as is done in 4.x? if all
that's required for a workaround is a patch similar to that above ...

thanks

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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