From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
virtualization@lists.osdl.org, akpm <akpm@osdl.org>,
chrisw@sous-sol.org, rusty@rustcorp.com.au, zach@vmware.com
Subject: Re: [PATCH] no paravirt for X86_VOYAGER or X86_VISWS
Date: Sat, 09 Dec 2006 02:18:26 -0800 [thread overview]
Message-ID: <457A8D72.4090909@goop.org> (raw)
In-Reply-To: <20061209015131.fc19aeb3.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Since Voyager and Visual WS already define ARCH_SETUP,
> it looks like PARAVIRT shouldn't be offered for them.
>
> In file included from arch/i386/kernel/setup.c:63:
> include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined
> In file included from include/asm/msr.h:5,
> from include/asm/processor.h:17,
> from include/asm/thread_info.h:16,
> from include/linux/thread_info.h:21,
> from include/linux/preempt.h:9,
> from include/linux/spinlock.h:49,
> from include/linux/capability.h:45,
> from include/linux/sched.h:46,
> from arch/i386/kernel/setup.c:26:
> include/asm/paravirt.h:163:1: warning: this is the location of the previous definition
> In file included from arch/i386/kernel/setup.c:63:
> include/asm-i386/mach-visws/setup_arch.h:8:1: warning: "ARCH_SETUP" redefined
> In file included from include/asm/msr.h:5,
> from include/asm/processor.h:17,
> from include/asm/thread_info.h:16,
> from include/linux/thread_info.h:21,
> from include/linux/preempt.h:9,
> from include/linux/spinlock.h:49,
> from include/linux/capability.h:45,
> from include/linux/sched.h:46,
> from arch/i386/kernel/setup.c:26:
> include/asm/paravirt.h:163:1: warning: this is the location of the previous definition
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
> arch/i386/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-2.6.19-git13.orig/arch/i386/Kconfig
> +++ linux-2.6.19-git13/arch/i386/Kconfig
> @@ -190,6 +190,7 @@ endchoice
> config PARAVIRT
> bool "Paravirtualization support (EXPERIMENTAL)"
> depends on EXPERIMENTAL
> + depends on !(X86_VISWS || X86_VOYAGER)
> help
> Paravirtualization is a way of running multiple instances of
> Linux on the same machine, under a hypervisor. This option
>
ACK. At some point paravirt may subsume subarches, but for now it is
only supported on standard PC-style hardware.
J
next prev parent reply other threads:[~2006-12-09 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 9:51 [PATCH] no paravirt for X86_VOYAGER or X86_VISWS Randy Dunlap
2006-12-09 10:18 ` Jeremy Fitzhardinge [this message]
2006-12-09 10:25 ` Zachary Amsden
2006-12-09 21:45 ` Chris Wright
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=457A8D72.4090909@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).