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

[Xen-devel] Re: [PATCH 2 of 6] amd iommu: Cleanup iommu pci capabilites

To: Jan Beulich <JBeulich@xxxxxxxx>
Subject: [Xen-devel] Re: [PATCH 2 of 6] amd iommu: Cleanup iommu pci capabilites detection
From: Wei Wang2 <wei.wang2@xxxxxxx>
Date: Fri, 11 Nov 2011 11:16:27 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 11 Nov 2011 02:14:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4EBCF9E30200007800060600@xxxxxxxxxxxxxxxxxxxx>
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: <patchbomb.1320853855@xxxxxxxxxxxx> <4b115815bc13e4f2a3a1.1320853857@xxxxxxxxxxxx> <4EBCF9E30200007800060600@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.6 (enterprise 20070904.708012)
On Friday 11 November 2011 10:33:07 Jan Beulich wrote:
> >>> On 09.11.11 at 16:50, Wei Wang <wei.wang2@xxxxxxx> wrote:
> >
> > # HG changeset patch
> > # User Wei Wang <wei.wang2@xxxxxxx>
> > # Date 1320851997 -3600
> > # Node ID 4b115815bc13e4f2a3a178f3de7477ecf46cb44b
> > # Parent  4769713326a876c25bdc0f9d1f90594f90fba9c5
> > amd iommu: Cleanup iommu pci capabilites detection.
> > * Define new structure to represent capability block.
> > * Remove unnecessary read for unused information.
> > * Add sanity check into get_iommu_capabilities.
> > * iommu capability offset is 16 bit not 8 bit, fix that.
>
> Does this imply that the capability can reside in extended config space?
> If so, all code paths using this will need revisiting with regard to
> extended config space possibly being inaccessible until early Dom0
> initialization.

Jan,
This is just an inconsistency issue with iommu specification as in IVHD 
header, it has been defined as 16 bit value. In reality, both current and 
next generation amd iommu will not have this capability in  extended pci 
config space. 

Thanks,
Wei

> Jan
>
> > Signed-off-by: Wei Wang <wei.wang2@xxxxxxx>




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