public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>,
	mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, mingo@elte.hu,
	linux-tip-commits@vger.kernel.org
Subject: Re: [tip:irq/numa] x86, apic: Fix dummy apic read operation together with broken MP handling
Date: Mon, 8 Jun 2009 21:47:34 +0400	[thread overview]
Message-ID: <20090608174734.GF5015@lenovo> (raw)
In-Reply-To: <20090608151646.GB5015@lenovo>

[Cyrill Gorcunov - Mon, Jun 08, 2009 at 07:16:46PM +0400]
...
| | should be other case:
| | when MADT is right, but disablelapic is used.
| | will get cpu_has_apic == 0, and we are not using dummy apic read/write.
| | 
| | so don't need to check
| |         /*
| |          * If we couldn't find a local APIC, then get out of here now!
| |          */
| |         if (APIC_INTEGRATED(apic_version[boot_cpu_physical_apicid]) &&
| |             !cpu_has_apic) {
| |                 if (!disable_apic) {
| |                         pr_err("BIOS bug, local APIC #%d not detected!...\n",
| |                                 boot_cpu_physical_apicid);
| |                         pr_err("... forcing use of dummy APIC emulation."
| |                                 "(tell your hw vendor)\n");
| |                 }
| |                 smpboot_clear_io_apic();
| |                 arch_disable_smp_support();
| |                 return -1;
| |         }
|
...

I've just emulated the situation where this if() triggered via
disable_apic boot option and without if (!disable_apic) we
have just a wrong message about BIOS bug (which is not since
we've disabled apic by hands). So no need to remove this
"if (!disable_apic)" snippet. In most cases it will be
always-true condition but for rare cases it'll be usefull
as well.

Now I'm trying to fake apic integrated case so we could
need additional check here...
 
	-- Cyrill

      reply	other threads:[~2009-06-08 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-07 12:48 [PATCH -tip] x86: apic - fix dummy apic read operation together with broken MP handling Cyrill Gorcunov
2009-06-07 14:24 ` [tip:irq/numa] x86, apic: Fix " tip-bot for Cyrill Gorcunov
2009-06-07 14:33   ` Cyrill Gorcunov
2009-06-07 19:23   ` Yinghai Lu
2009-06-07 20:39     ` Cyrill Gorcunov
2009-06-07 22:59       ` Yinghai Lu
2009-06-08 15:16         ` Cyrill Gorcunov
2009-06-08 17:47           ` Cyrill Gorcunov [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=20090608174734.GF5015@lenovo \
    --to=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --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