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] [PATCH][RFC] Support more Capability Structures andDevic

To: "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx>, "Yuji Shimada" <shimada-yxb@xxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][RFC] Support more Capability Structures andDevice Specific
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Wed, 2 Jul 2008 07:23:56 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Dong, Eddie" <eddie.dong@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 01 Jul 2008 16:25:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <18537.65217.267922.698490@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <20080630131728.F30A.SHIMADA-YXB@xxxxxxxxxxxxxxx><10EA09EFD8728347A513008B6B0DA77A035FC20B@xxxxxxxxxxxxxxxxxxxxxxxxxxxx><20080701163646.C0E3.SHIMADA-YXB@xxxxxxxxxxxxxxx> <18537.65217.267922.698490@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcjbYHFjmjI/FhBjRMGy5KyoLWx9wwAcABdg
Thread-topic: [Xen-devel] [PATCH][RFC] Support more Capability Structures andDevice Specific
> I haven't read many modern PCI card specs but with the
> constant 
> shifting of functionality (even functionality which is
> intended to 
> preserve hardware integrity) to software and firmware, I
> would be wary 
> of assuming that every unknown PCI card has no register
> and 
> configuration settings which can cause hardware damage or
> other kinds 
> of unexpected and undesirable events.

For those vendor specific registers (in PCI cap or not), we always have
dillemma: pass through with functionality or discard with malfunction.
If we pass through them, then the opposite card are in black list that
we can't support, if we discard them, the former class of card becomes
un-assignable.

Per current data, pass through get many known bug fixed as the case
Dexuan mentioned. But we didn't see a HW damaging host. Some know issue
could be a device issuing tons of PCIe traffic, absorbing extra power,
issuing interrupt storm etc, but right now we didn't see issues yet.

> 
> If there is there a requirement written into the general
> PCI 
> specification that this won't happen, then fine - if so
> please quote 
> chapter and verse.
> 
Defintely if PCIe spec can be modified to support this one is best, but
we still have legacy devices.

Thx, eddie


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