From: Gabriel C <nix.or.die@googlemail.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Ingo Molnar <mingo@elte.hu>, Priit Laes <plaes@plaes.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jack Steiner <steiner@sgi.com>
Subject: Re: [REGRESSION] x86: support for new UV apic
Date: Fri, 25 Apr 2008 13:41:06 +0200 [thread overview]
Message-ID: <4811C352.5080802@googlemail.com> (raw)
In-Reply-To: <4811BEA1.502@googlemail.com>
Gabriel C wrote:
> Andi Kleen wrote:
>> Ingo Molnar <mingo@elte.hu> writes:
>>
>>> * Priit Laes <plaes@plaes.org> wrote:
>>>
>>>> Hey,
>>>>
>>>> I am getting two following warnings (probable one per each CPU core)
>>>> using the latest Linus's git:
>>>>
>>>> WARNING: at arch/x86/kernel/genapic_64.c:86 read_apic_id+0x30/0x62()
>>>> Modules linked in:
>>>> Pid: 1, comm: swapper Not tainted 2.6.25-03563-gf7288b1 #20
>>> thanks - could you check the patch below, does it fix the warnings?
>> I think it would have been better to change the WARN_ON to
>>
>> WARN_ON(preemptible() && num_online_cpus() > 1)
>
> Hmm , I think you are right , Ingo's patch fixes the warning on boot but now I get one when I reboot the box.
>
>> Preemption is actually ok here because this runs before the other
>> CPUs are started
>>
>> Alternative patch appended.
>
> I will test your patch in some minutes.
Your patch works better , at least for my box , 4 reboots with your patch and boot/reboot warnings are all gone.
>>
>> Don't warn in read_apic_id() when preemptible but only one CPU online.
>>
>> Signed-off-by: Andi Kleen <andi@firstfloor.org>
>>
>> Index: linux/arch/x86/kernel/genapic_64.c
>> ===================================================================
>> --- linux.orig/arch/x86/kernel/genapic_64.c
>> +++ linux/arch/x86/kernel/genapic_64.c
>> @@ -83,7 +83,7 @@ unsigned int read_apic_id(void)
>> {
>> unsigned int id;
>>
>> - WARN_ON(preemptible());
>> + WARN_ON(preemptible() && num_online_cpus() > 1);
>> id = apic_read(APIC_ID);
>> if (uv_system_type >= UV_X2APIC)
>> id |= __get_cpu_var(x2apic_extra_bits);
>
>
next prev parent reply other threads:[~2008-04-25 11:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 4:43 [REGRESSION] x86: support for new UV apic Priit Laes
2008-04-25 6:44 ` Ingo Molnar
2008-04-25 9:11 ` Gabriel C
2008-04-25 9:19 ` Priit Laes
2008-04-25 9:45 ` Andi Kleen
2008-04-25 11:21 ` Gabriel C
2008-04-25 11:41 ` Gabriel C [this message]
2008-04-25 15:53 ` Priit Laes
2008-04-28 17:41 ` 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=4811C352.5080802@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=plaes@plaes.org \
--cc=steiner@sgi.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