>> It shouldn't have any confilicts, since they belong to different
>> archs. Currently, you know source code is placed at
>> arch/{$arch}/kvm, and Makefile and Kconfig aslo there.
>> So, it doesn't impact any issues, since ia64 and x86_64 are totally
>> different archs. For example, you can define HAS_IO_PORT macro for
>> ia64 and x86, but they don't invoke any conficlts.:)
>
> What about files that get shared?
I think common files shouldn't use KVM_CONFIG_INTEL.
> The build system should pick up the relevant files
> from /lib/modules/`uname -r`/build/ If it doesn't, it's a bug. (It
> works for me on x86.)
If we built on target machine, you are right. But if the build machine
is not target machine, how to build ?
Xiantao
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
