From mboxrd@z Thu Jan  1 00:00:00 1970
From: Weidong Han <weidong.han@intel.com>
Subject: Re: Re: follow up to a pciback "pv pci-passthrough
	co-assigned problem"
Date: Tue, 26 Jan 2010 09:42:00 +0800
Message-ID: <4B5E4868.60505@intel.com>
References: <c67eed301001221732s4b6a9a10p4be4182ecf831b6a@mail.gmail.com>	
	<20100123164850.GT2861@reaktio.net>	
	<c67eed301001230936o37dc63c2le944386cbaa02ff3@mail.gmail.com>	
	<20100123174333.GW2861@reaktio.net>	
	<c67eed301001230945i45b8bb22q8cc3ded555cd7959@mail.gmail.com>	
	<c67eed301001230954i6e9098fdwde189d429b8591fa@mail.gmail.com>	
	<20100123175705.GY2861@reaktio.net>	
	<c67eed301001230958x2b22a5cs45df42cb956f75ed@mail.gmail.com>	
	<c67eed301001231015v2c572d2fxb4a221157f3f1bfd@mail.gmail.com>	
	<4B5CF79A.6020002@intel.com>
	<c67eed301001250817o66c39940o2d234bcb040fd593@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <c67eed301001250817o66c39940o2d234bcb040fd593@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: 0bo0 <0.bugs.only.0@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

0bo0 wrote:
> hi,
>
> On Sun, Jan 24, 2010 at 5:44 PM, Weidong Han <weidong.han@intel.com> 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
>   
The option was introduced by changeset 20179. It's small. It can be back 
ported to Xen 3.x if need.

Regards,
Weidong