From: Ingo Molnar <mingo@kernel.org>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] x86/apic: Justification for disabling IO APIC before Local APIC
Date: Thu, 5 Dec 2013 09:54:51 +0100 [thread overview]
Message-ID: <20131205085451.GA13377@gmail.com> (raw)
In-Reply-To: <1386202069-51515-1-git-send-email-fenghua.yu@intel.com>
* Fenghua Yu <fenghua.yu@intel.com> wrote:
> From: Fenghua Yu <fenghua.yu@intel.com>
>
> Since erratum AVR31 in "Intel Atom Processor C2000 Product Family
> Specification Update" is published, I add a justification comment for
> disabling IO APIC before Local APIC (commit 522e6646).
>
> Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
> ---
> arch/x86/kernel/reboot.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
> index da3c599..c752cb4 100644
> --- a/arch/x86/kernel/reboot.c
> +++ b/arch/x86/kernel/reboot.c
> @@ -558,6 +558,17 @@ void native_machine_shutdown(void)
> {
> /* Stop the cpus and apics */
> #ifdef CONFIG_X86_IO_APIC
> + /*
> + * Disabling IO APIC before local APIC is a workaround for
> + * erratum AVR31 in "Intel Atom Processor C2000 Product Family
> + * Specification Update". In this situation, interrupts that target
> + * a Logical Processor whose Local APIC is either in the process of
> + * being hardware disabled or software disabled are neither delivered
> + * nor discarded. When this erratum occurs, the processor may hang.
> + *
> + * Even without the erratum, it still makes sense to quiet IO APIC
> + * before disabling Local APIC.
> + */
> disable_IO_APIC();
> #endif
Looks good to me, except that patch titles should start with verbs,
i.e. something like:
x86/apic/doc: Add justification for disabling IO APIC before Local APIC
Which makes for a much more fluid reading of shortlogs etc.
Unless you sentences without verbs.
^-------------------------------------------like
;-)
Thanks,
Ingo
next prev parent reply other threads:[~2013-12-05 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 0:07 [PATCH] x86/apic: Justification for disabling IO APIC before Local APIC Fenghua Yu
2013-12-05 3:36 ` [tip:x86/urgent] x86/apic, doc: " tip-bot for Fenghua Yu
2013-12-05 8:54 ` Ingo Molnar [this message]
2013-12-05 13:27 ` [PATCH] x86/apic: " Yu, Fenghua
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=20131205085451.GA13377@gmail.com \
--to=mingo@kernel.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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.