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/
Home Products Support Community News


RE: [Xen-devel] Is unmodified_drivers broken?

To: "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx>, "Nowatzki, Thomas L" <Thomas.Nowatzki@xxxxxxxxxx>
Subject: RE: [Xen-devel] Is unmodified_drivers broken?
From: "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Date: Thu, 29 Mar 2007 18:27:45 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 29 Mar 2007 23:29:11 +0100
Envelope-to: Keir.Fraser@xxxxxxxxxxxx
In-reply-to: <1175147205.29659.14.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acdxxam2ZibmE6LcQ36y2CUqoibGAAAicDxg
Thread-topic: [Xen-devel] Is unmodified_drivers broken?
>> All, I tried to compile unmodified drivers on the latest changeset
>> The compile breaks.This is what I did. I booted up a x86_64 hvm
domain that was 
>> running sles 10, I copied the  entire xen-unstable tree into the
>> Then, I went into the unmodified_drivers directory and ran
>> and make -C /usr/src/linux M=$PWD V=1 modules .
>> I have posted the results. 
>> - Have others seen this issue? - Is this because of some kind of mess
up where the 
>> /usr/src/linux/include/xen directory is clashing with the local 
>> include/xen directory? Looking at the overrides.mk file, it does seem
like the local 
>> directory is getting included first.
>That's correct. The include/xen directory in the kernel you 
>are building against is clashing with the one in the 
>unmodified drivers. The workaround is to rename include/xen in 
>the kernel to something else.
>Unfortunately Kbuild doesn't give us an easy way to make sure 
>our headers take precedence over the in kernel ones.

Thank you for your response. 

I discovered that just renaming the include/xen directory does not help.
There's still a clash.

I discovered that the following directories need to be deleted/renamed.


And then, run mkbuildtree and do make as in the README file, and I am
good to go.

So, here's my question : Even though I am on a x86_64 hvm, why does it
include and compile code from asm-i386? Renaming (or not renaming the)
asm-x86_64/mach-xen seems to have absolutely no effect.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>