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 0/7] PCI multi-segment support

To: "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx>, "Keir Fraser" <keir@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH, RFC 0/7] PCI multi-segment support
From: "Jan Beulich" <JBeulich@xxxxxxxx>
Date: Mon, 05 Sep 2011 14:18:30 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 05 Sep 2011 06:19:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E567E3E0200007800053454@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: <4E567E3E0200007800053454@xxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 25.08.11 at 16:54, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
> In order for Xen to be able to boot on systems with multiple PCI segments
> (also called domains), a number of changes are necessary to the
> hypervisor, the hypercall interface, the tools, and the Dom0 kernel, as
> in most code paths and definitions there were not even provisions for
> passing a segment number.
> 
> The hypercall interface changes may need some discussion before
> applying the patches, in particular
> 
> - whether the way PHYSDEVOP_map_pirq gets re-used is acceptable,
>   or whether alternatively we should define a replacement one sub-
>   hypercall
> - whether PHYSDEVOP_manage_pci_* should be deprecated
> - whether the bit assignments for the four uses of machine_bdf in
>   the domctl interface can be re-defined

No comment from either of you on the proposed changes?

Jan

> Additionally, in the AMD IOMMU code there are two places where I
> was unable to identify how the segment value ought to be retrieved.
> Since I'm unaware of multi-segment AMD-based systems, imo this
> should not be a reason to not commit the changes proposed.
> 
> 1: introduce notion of PCI segments
> 2: add new physdevop-s
> 3: adjust domctl interface
> 4: VT-d specific adjustments
> 5: AMD-IOMMU specific adjustments
> 6: Pass-through adjustments
> 7: config space accessor adjustments
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>


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