From: "Jan Beulich" <jbeulich@novell.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>
Cc: <linux-kernel@vger.kernel.org>,
"Jeremy Fitzhardinge" <jeremy@xensource.com>
Subject: [PATCH] i386: XEN config option should not depend on X86_TSC/X86_CMPXCHG
Date: Thu, 13 Dec 2007 09:00:49 +0000 [thread overview]
Message-ID: <476102D1.76E4.0078.0@novell.com> (raw)
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 <jbeulich@novell.com>
Cc: Jeremy Fitzhardinge <jeremy@xensource.com>
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
next reply other threads:[~2007-12-13 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 9:00 Jan Beulich [this message]
2007-12-14 7:08 ` [PATCH] i386: XEN config option should not depend on X86_TSC/X86_CMPXCHG Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476102D1.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=hpa@zytor.com \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox