From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Dealing with non-existent BDF devices in VT-d and
 in the hardware.
Date: Mon, 17 Mar 2014 16:00:20 -0400
Message-ID: <20140317200020.GD16397@phenom.dumpdata.com>
References: <20140311173039.GB14684@phenom.dumpdata.com>
	<531F49A4.80107@citrix.com>
	<20140311174940.GB15088@phenom.dumpdata.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA15598@SHSMSX104.ccr.corp.intel.com>
	<20140314175115.GL30560@phenom.dumpdata.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0AA1728D@SHSMSX104.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0AA1728D@SHSMSX104.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, "gordan@bobich.net" <gordan@bobich.net>, "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On Mon, Mar 17, 2014 at 01:03:00AM +0000, Zhang, Yang Z wrote:
> Konrad Rzeszutek Wilk wrote on 2014-03-15:
> >> 
> >> What happens if you assign the devices under bus 09 to another guest?
> > 
> > Hadn't tried that. I think it would all blow up as the the
> > non-existent bridge is now assigned to one guest and the phantom DMA
> > requests for the
> > 09 would show up under the 08 device. I think I would corrupt the
> > guest memory with random DMA writes.
> > 
> >> Is it better to add Xen command line to add such devices to a group
> >> and
> > assign the whole group to a guest when trying to assign a device of
> > the group to guest?
> > 
> > Or implement the group assigment in QEMU or libxl so that nobody tries
> > doing it.
> 
> But I think user still need to tell which device is buggy manually and I don't think QEMU or libxl can do it.

I think there are two issues here: 

a) Missing device assigments via groups. That should be done irregardless
   if the device / hardware is buggy.

b) Buggy devices like the IDT bridge that I see. That is a seperate issue - and
   we just discussion if we want to inject that in the VT-d (or AMD-VI) what
   would be the mechanism to do that.

> 
> Best regards,
> Yang
> 
>