From: Glauber Costa <gcosta@redhat.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
kiran@scalemp.com, mingo@elte.hu, tglx@linutronix.de
Subject: Re: + x86-vsmp-build-fixes.patch added to -mm tree
Date: Tue, 18 Mar 2008 06:40:35 -0300 [thread overview]
Message-ID: <47DF8E13.6040408@redhat.com> (raw)
In-Reply-To: <86802c440803172226yb867326rb595b36b03e6c4b9@mail.gmail.com>
Yinghai Lu wrote:
> On Mon, Mar 17, 2008 at 10:14 PM, <akpm@linux-foundation.org> wrote:
>> The patch titled
>> x86: vsmp build fixes
>> has been added to the -mm tree. Its filename is
>> x86-vsmp-build-fixes.patch
>>
>> Before you just go and hit "reply", please:
>> a) Consider who else should be cc'ed
>> b) Prefer to cc a suitable mailing list as well
>> c) Ideally: find the original patch on the mailing list and do a
>> reply-to-all to that, adding suitable additional cc's
>>
>> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>>
>> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
>> out what to do about this
>>
>> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>>
>> ------------------------------------------------------
>> Subject: x86: vsmp build fixes
>> From: Glauber Costa <gcosta@redhat.com>
>>
>> VSMP depends on PCI, but the file is now compiled conditionally on PARAVIRT,
>> no VSMP, so enclose everything in an ifdef CONFIG_PCI.
>>
>> We have to be careful enough to let is_vsmp_box and vsmp_init defined, since
>> they are used outside this file
>>
>> Signed-off-by: Glauber Costa <gcosta@redhat.com>
>> Cc: Ravikiran Thirumalai <kiran@scalemp.com>
>> Cc: Ingo Molnar <mingo@elte.hu>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>> ---
>>
>> arch/x86/kernel/vsmp_64.c | 10 +++++++++-
>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>
>> diff -puN arch/x86/kernel/vsmp_64.c~x86-vsmp-build-fixes arch/x86/kernel/vsmp_64.c
>> --- a/arch/x86/kernel/vsmp_64.c~x86-vsmp-build-fixes
>> +++ a/arch/x86/kernel/vsmp_64.c
>> @@ -19,6 +19,7 @@
>> #include <asm/io.h>
>> #include <asm/paravirt.h>
>>
>> +#ifdef CONFIG_PCI
>> /*
>> * Interrupt control on vSMPowered systems:
>> * ~AC is a shadow of IF. If IF is 'on' AC should be 'off'
>> @@ -87,12 +88,18 @@ int is_vsmp_box(void)
>> if (read_pci_config(0, 0x1f, 0, PCI_VENDOR_ID) ==
>> (PCI_VENDOR_ID_SCALEMP || (PCI_DEVICE_ID_SCALEMP_VSMP_CTL << 16)))
>> vsmp = 1;
>> -
>> return vsmp;
>> }
>> +#else
>> +int is_vsmp_box(void)
>> +{
>> + return 0;
>> +}
>> +#endif
>>
>> void __init vsmp_init(void)
>> {
>> +#ifdef CONFIG_PCI
>> void *address;
>> unsigned int cap, ctl, cfg;
>>
>> @@ -125,5 +132,6 @@ void __init vsmp_init(void)
>> }
>>
>> early_iounmap(address, 8);
>> +#endif
>> return;
>> }
>> _
>
> in arch/x86/Kconfig
>
> config PCI
> bool "PCI support" if !X86_VISWS && !X86_VSMP
> depends on !X86_VOYAGER
> default y
> select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
> help
> Find out whether you have a PCI motherboard. PCI is the name of a
> bus system, i.e. the way the CPU talks to the other stuff inside
> your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
> VESA. If you have PCI, say Y, otherwise N.
>
> will make sure if X86_VSMP, the PCI=y
Unfortunately, as said in the changelog, this file is compiled in
conditionaly with PARAVIRT, not VSMP.
That's precisely the reason for the discovery code. Finding out wheter
or not we're running under vsmp.
prev parent reply other threads:[~2008-03-18 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803180514.m2I5ElVJ015693@imap1.linux-foundation.org>
2008-03-18 5:26 ` + x86-vsmp-build-fixes.patch added to -mm tree Yinghai Lu
2008-03-18 7:28 ` Ravikiran Thirumalai
2008-03-18 7:56 ` Yinghai Lu
2008-03-18 8:25 ` Yinghai Lu
2008-03-18 8:37 ` Fwd: " Yinghai Lu
2008-03-18 9:40 ` Glauber Costa [this message]
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=47DF8E13.6040408@redhat.com \
--to=gcosta@redhat.com \
--cc=kiran@scalemp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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