Sam Ravnborg wrote:
So use arch/*/virt/kvm/ if kvm really requires
a subdirectory of it own. Preferably not.
A handful of files named kvm* does not warrant their own
subdirectory IMO.
We'll have 5-6 x86 specific files.
Where do you suggest we place them?
/arch/x86/virt/
But, I want to place the arch independent files in virt/kvm/, so as to
leave room for virt/lguest/.
Seems logical and fit the way we handle mm/ versus arch/*/mm,
kernel/ arch/*/kernel etc.
Exactly, so virt/kvm/ -> arch/x86/virt/kvm/.
Are there any dependencies between the arch and non-arch files
such as they are combined in a single module?
Yes, they are combined into a single module.
In the case of x86, some of arch/x86/... will be combined with virt/kvm/
to form kvm.ko, while others will generate kvm-intel.ko and kvm-amd.ko.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
