All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: fix dummy apic read/write warning
Date: Mon, 8 Jun 2009 01:03:37 +0400	[thread overview]
Message-ID: <20090607210337.GG4547@lenovo> (raw)
In-Reply-To: <86802c440906071228x489c3f79q2e1a49dc997e874@mail.gmail.com>

[Yinghai Lu - Sun, Jun 07, 2009 at 12:28:07PM -0700]
| On Sun, Jun 7, 2009 at 12:01 AM, Cyrill Gorcunov<gorcunov@gmail.com> wrote:
| > [Yinghai Lu - Sat, Jun 06, 2009 at 03:16:38PM -0700]
| > | ingo got
| > | [    0.000000] Using APIC driver default
| > | [    0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs
| > | [    0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
| > | [    0.000000] APIC: disable apic facility
| > | [    0.000000] ------------[ cut here ]------------
| > | [    0.000000] WARNING: at arch/x86/kernel/apic/apic.c:254 native_apic_read_dummy+0x2d/0x3b()
| > | [    0.000000] Hardware name: HP OmniBook PC
| > |
| > | we have wrong check in dummy read and write.
| > | [we only test on system that have APIC with "disableapic"...]
| > |
| > | Signed-off-by: yinghai Lu <yinghai@kernel.org>
| > |
| > | ---
| > |  arch/x86/kernel/apic/apic.c |    4 ++--
| > |  1 file changed, 2 insertions(+), 2 deletions(-)
| > |
| > | Index: linux-2.6/arch/x86/kernel/apic/apic.c
| > | ===================================================================
| > | --- linux-2.6.orig/arch/x86/kernel/apic/apic.c
| > | +++ linux-2.6/arch/x86/kernel/apic/apic.c
| > | @@ -246,12 +246,12 @@ static int modern_apic(void)
| > |   */
| > |  static void native_apic_write_dummy(u32 reg, u32 v)
| > |  {
| > | -     WARN_ON_ONCE((cpu_has_apic || !disable_apic));
| > | +     WARN_ON_ONCE((cpu_has_apic && !disable_apic));
| > |  }
| > |
| > |  static u32 native_apic_read_dummy(u32 reg)
| > |  {
| > | -     WARN_ON_ONCE((cpu_has_apic || !disable_apic));
| > | +     WARN_ON_ONCE((cpu_has_apic && !disable_apic));
| > |       return 0;
| > |  }
| > |
| > |
| >
| > No Yinghai, this is wrong. native_apic_write_dummy is not
| > admissible to be called after apic->write has been NOP'ified.
| >
| > If a site calls for apic->write after apic_disable() it's
| > a plain *bug* in caller. So we should continute warning if
| > cpu_has_apic _or_ !disable_apic.
| 
| ok, just change it to
| 
|      WARN_ON_ONCE(1);
| 
| there.

There was some scenario where we had legitime apic->write
on SMP kernel when cpu goes to halt. Will recheck tomorrow.
That is why we added conditional WARN to eliminate uglifying
by additional checks (ie we know that apic->write happens
but it's nothing serious). Thanks Yinghai!

| 
| >
| > Though since for SMP compiled kernel we still rely on
| > apic->read the snippet is to be changed to (cpu_has_apic && !disable_apic)
| > indeed.
| 
| YH
| 
	-- Cyrill

      reply	other threads:[~2009-06-07 21:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090606073737.GA3163@elte.hu>
2009-06-06 22:16 ` [PATCH] x86: fix dummy apic read/write warning Yinghai Lu
2009-06-07  7:01   ` Cyrill Gorcunov
2009-06-07 19:28     ` Yinghai Lu
2009-06-07 21:03       ` 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=20090607210337.GG4547@lenovo \
    --to=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.