[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-merge] AMD64 dma-mapping


  • To: "Muli Ben-Yehuda" <mulix@xxxxxxxxx>
  • From: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
  • Date: Tue, 24 Jan 2006 14:28:06 -0600
  • Cc: xen-merge@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 24 Jan 2006 20:36:47 +0000
  • List-id: xen-merge <xen-merge.lists.xensource.com>
  • Thread-index: AcYhIfcaTqm5xI2sRZijI6vjamZI1gAAjDSA
  • Thread-topic: [Xen-merge] AMD64 dma-mapping

> > If I turn on CONFIG_GART_IOMMU in the Kconfig,
> > enable it in the .config file, and build the
> > kernel, I get errors because
> > include/asm-i386/mach-xen/asm/dma-mapping.h
> > is included instead of 
> > include/asm-x86_64/mach-xen/asm/dma-mapping.h
> > 
> > I can't figure out how or where the build system
> > decides which dma-mapping file to include.  Help
> > would be appreciated.
> 
> The build always uses include/asm, which should be symlink'd 
> to the right architecture's asm-$(ARCH) directory. Are you 
> sure you're building for x86-64? is gart the only thing 
> that's pulling in the wrong dma-mapping.h?

include/asm is correctly linked to include/asm-x86_64

poking around a bit, I found that asm/dma-mapping is
being included from include/linux/dma-mapping.h
If I force the include there to be asm-x86_64/dma-mapping.h,
the code compiles.  That's not an acceptable long-term
solution, obviously.

There are some files in arch/x86_64/kernel that are 
being compiled from arch/i386/kernel (such as swiotlb.c),
but the mainline tree does that too without this problem.

-Mark Langsdorf
AMD, Inc.


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.