virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	virtualization@lists.osdl.org, linux-kernel@vger.kernel.org,
	Glauber de Oliveira Costa <glommer@gmail.com>,
	shai@scalex86.org
Subject: Re: 2.6.25-rc5-mm1 (paravirt/vsmp/no PCI)
Date: Tue, 11 Mar 2008 17:10:40 -0700	[thread overview]
Message-ID: <20080312001040.GA6434@localdomain> (raw)
In-Reply-To: <47D6CD04.8060303@goop.org>

On Tue, Mar 11, 2008 at 11:18:44AM -0700, Jeremy Fitzhardinge wrote:
>Randy Dunlap wrote:
>
>Added Cc:
>
>>On Tue, 11 Mar 2008 01:14:34 -0700 Andrew Morton wrote:
>>
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc5/2.6.25-rc5-mm1/
>>>
>>
>>randconfig (x86_64) with
>>PCI=n
>>PARAVIRT=y
>>VSMP=n
>>
>>ends with
>>
>>arch/x86/kernel/built-in.o: In function `is_vsmp_box':
>>(.text+0x1178d): undefined reference to `early_pci_allowed'
>>arch/x86/kernel/built-in.o: In function `is_vsmp_box':
>>(.text+0x117a9): undefined reference to `read_pci_config'
>>arch/x86/kernel/built-in.o: In function `vsmp_init':
>>(.init.text+0x4fcc): undefined reference to `early_pci_allowed'
>>arch/x86/kernel/built-in.o: In function `vsmp_init':
>>(.init.text+0x501a): undefined reference to `read_pci_config'
>>make[1]: *** [.tmp_vmlinux1] Error 1
>>
>>config attached.
>
>   J


Would anyone have objection to have PARAVIRT depend on PCI, since the
vsmp paravirt bits depend on PCI cfg space to determine if the system is
vsmp?   If not, this patch would suffice.

Glauber?

Thanks,
Kiran

---

Make PARAVIRT depend on PCI.

vSMP PARAVIRT ops probe the pci config space to determine if the
system is indeed a ScaleMP vSMP box.  Hence, depend on PCI to enable
PARAVIRT.

Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>

Index: linux-2.6.24/arch/x86/Kconfig
===================================================================
--- linux-2.6.24.orig/arch/x86/Kconfig	2008-03-11 16:38:26.000000000 -0700
+++ linux-2.6.24/arch/x86/Kconfig	2008-03-11 16:50:52.000000000 -0700
@@ -384,7 +384,7 @@ source "arch/x86/lguest/Kconfig"
 
 config PARAVIRT
 	bool "Enable paravirtualization code"
-	depends on !(X86_VISWS || X86_VOYAGER)
+	depends on !(X86_VISWS || X86_VOYAGER) && PCI
 	help
 	  This changes the kernel so it can modify itself when it is run
 	  under a hypervisor, potentially improving performance significantly

  reply	other threads:[~2008-03-12  0:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080311011434.ad8c8d7d.akpm@linux-foundation.org>
2008-03-11 17:09 ` 2.6.25-rc5-mm1 (paravirt/vsmp/no PCI) Randy Dunlap
2008-03-11 18:18   ` Jeremy Fitzhardinge
2008-03-12  0:10     ` Ravikiran G Thirumalai [this message]
2008-03-12  1:42       ` Randy Dunlap
2008-03-12  1:51       ` Jeremy Fitzhardinge
2008-03-12  7:14       ` Ingo Molnar

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=20080312001040.GA6434@localdomain \
    --to=kiran@scalex86.org \
    --cc=akpm@linux-foundation.org \
    --cc=glommer@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=shai@scalex86.org \
    --cc=virtualization@lists.osdl.org \
    /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).