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][2/4] PCI Driver Domains: PCI Backend/Frontend

On Tue, 2006-02-07 at 23:17 +0000, Keir Fraser wrote:
> On 7 Feb 2006, at 19:58, Ryan wrote:
> 
> > One issue with this patch (at least the frontend part of it) is that it
> > will probably only work correctly with x86 (I don't have access to 
> > other
> > architectures to test on) and the kconfig menu entries will appear
> > regardless of the architecture (they don't list x86 as a dependency).
> > Should they list x86 as a dependency? Right now, they're under the 
> > "Xen"
> > menu with the other backends and frontends. Should I move the PCI
> > frontend configuration option into the "Bus options/PCI Access" menu
> > next to the mmconfig, direct, and bios options? I think it would be
> > better placed under the "Bus options/PCI Access" menu but I wasn't sure
> > if all the backends and frontends needed to be listed together.
> 
> By x86 you mean i386 and x86_64? I guess it makes sense to list X86 as 
> a dependency for now. And yes, I think 'Bus Options/PCI Access' is the 
> correct place to place the pci frontend option. Maybe call the option 
> 'Xen PCI channel' or something like that?

I can only say i386 because that's all I've tested, but I would think it
should work for x86_64 unmodified (although I haven't placed the PCI
frontend options in the x86_64 kconfig file since I can't test it).

Here's the updated patch with the PCI frontend configuration option in
its new place.

Signed-off-by: Ryan Wilson <hap9@xxxxxxxxxxxxxx>

Attachment: pci-ddi.patch
Description: Text Data

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