The way X86_TSC works and the fact that Xen itself won't work on
systems without TSC (really any systems pre-dating i686) makes it
unnecessary for XEN to depend on it.
Similarly, X86_CMPXCHG isn't needed here either as Xen for the above
reason guarantees its availability.
This allows the option to be available when selecting M386, M486, or
M586.
Signed-off-by: Jan Beulich <[email protected]>
Cc: Jeremy Fitzhardinge <[email protected]>
arch/x86/xen/Kconfig | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.24-rc5/arch/x86/xen/Kconfig 2007-12-12 11:28:18.000000000 +0100
+++ 2.6.24-rc5-i386-xen-no-tsc/arch/x86/xen/Kconfig 2007-12-07 14:53:28.000000000 +0100
@@ -5,7 +5,7 @@
config XEN
bool "Xen guest support"
select PARAVIRT
- depends on X86_CMPXCHG && X86_TSC && !NEED_MULTIPLE_NODES && !(X86_VISWS || X86_VOYAGER)
+ depends on !NEED_MULTIPLE_NODES && !(X86_VISWS || X86_VOYAGER)
help
This is the Linux Xen port. Enabling this will allow the
kernel to boot in a paravirtualized environment under the
--
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]
