public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: hpa@zytor.com, tglx@linutronix.de, xemul@openvz.org,
	yhlu.kernel@gmail.com, linux-kernel@vger.kernel.org,
	macro@linux-mips.org, andi@firstfloor.org
Subject: Re: [rfc 0/4] x86 - apic dummy ops with cleanups
Date: Sun, 12 Apr 2009 20:02:39 +0200	[thread overview]
Message-ID: <20090412180239.GA3489@elte.hu> (raw)
In-Reply-To: <20090412180014.GD6942@lenovo>


* Cyrill Gorcunov <gorcunov@gmail.com> wrote:

> Thanks, Ingo!
> 
> Actually I found one a bit suspicious thing (not sure if it was 
> initially designed to behave like that).
> 
> Suppose we have SMP compiled kernel and even supported on HW level 
> but then we disable apic thru kernel option. And then when system 
> startup it should be working fine since we go to uniprocessor 
> mode. Then the machine going for reboot and we have:
> 
> Starting from arch/x86/kernel/reboot.c
> 
> native_machine_shutdown
> 	smp_send_stop
> 		smp_ops.smp_send_stop
> 			native_smp_send_stop
> 				disable_local_APIC
> 					apic_write(APIC_SPIV, value);
> 
> Since we have reserved APIC memory mapped area (in _anycase_) it 
> doesn't cause any problems but was it initially supposed?

i dont think that was supposed so. If the APIC wasnt even enabled 
then we shouldnt try to disable it. Note that there are a few 
unusual paths to APIC enablement: for example by twiddling the 
nmi_watchdog knob in /proc/sys - or in theory through a CPU hotplug 
event.

	Ingo

  reply	other threads:[~2009-04-12 18:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-12 16:47 [rfc 0/4] x86 - apic dummy ops with cleanups Cyrill Gorcunov
2009-04-12 16:47 ` [rfc 1/4] x86: irq.c - tiny cleanup Cyrill Gorcunov
2009-04-12 17:25   ` Ingo Molnar
2009-04-12 17:53     ` Cyrill Gorcunov
2009-04-12 17:57   ` [tip:x86/apic] " tip-bot for Cyrill Gorcunov
2009-04-12 16:47 ` [rfc 2/4] x86: apic - introduce imcr_ helpers Cyrill Gorcunov
2009-04-12 17:57   ` [tip:x86/apic] " tip-bot for Cyrill Gorcunov
2009-04-12 16:47 ` [rfc 3/4] x86: apic - introduce dummy apic operations Cyrill Gorcunov
2009-04-12 17:57   ` [tip:x86/apic] " tip-bot for Cyrill Gorcunov
2009-04-12 16:47 ` [rfc 4/4] x86: smp.c - align smp_ops assignments Cyrill Gorcunov
2009-04-12 17:58   ` [tip:x86/apic] " tip-bot for Cyrill Gorcunov
2009-04-12 17:24 ` [rfc 0/4] x86 - apic dummy ops with cleanups Ingo Molnar
2009-04-12 18:00   ` Cyrill Gorcunov
2009-04-12 18:02     ` Ingo Molnar [this message]
2009-04-12 18:12       ` Cyrill Gorcunov

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=20090412180239.GA3489@elte.hu \
    --to=mingo@elte.hu \
    --cc=andi@firstfloor.org \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=tglx@linutronix.de \
    --cc=xemul@openvz.org \
    --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