From: "Wei, Jiangang" <weijg.fnst@cn.fujitsu.com>
To: "mingo@kernel.org" <mingo@kernel.org>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@suse.de" <bp@suse.de>
Subject: Re: [PATCH 1/2] x86/smpboot: Check APIC ID before setting up default routing
Date: Thu, 18 Aug 2016 10:15:15 +0000 [thread overview]
Message-ID: <1471515309.7011.12.camel@localhost> (raw)
In-Reply-To: <20160818094730.GA1967@gmail.com>
On Thu, 2016-08-18 at 11:47 +0200, Ingo Molnar wrote:
> * Wei Jiangang <weijg.fnst@cn.fujitsu.com> wrote:
>
> > Check the boot APIC ID firstly,
> > and then setup the default routing of APIC looks better.
> >
> > And move default_setup_apic_routing() close to apic_bsp_setup(),
> > which staying in step with the codes in APIC_init_uniprocessor().
> >
> > Signed-off-by: Wei Jiangang <weijg.fnst@cn.fujitsu.com>
> > ---
> > arch/x86/kernel/smpboot.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
>
> If it's not a bug then please clearly note so in the changelog and
> explain why the change results in better code.
It's not a bug.
The combination of default_setup_apic_routing() and apic_bsp_setup() is
used to enable APIC mode. If the return of read_apic_id() is not equal
to boot_cpu_physical_apicid, it means the APIC ID of current CPU‘s local
APIC is unexpected and enable APIC mode maybe fail. so no need to set
up the apic routing. That's why I want to move
default_setup_apic_routing() behind checking the boot APIC ID.
Sorry for obscure commit message. I will improve it in next version.
>
> If it's fixing a bug/misfeature then please fix the changelog to
> conform to the standard changelog style:
>
> - first describe the symptoms of the bug - how does a user notice?
>
> - then describe how the code behaves today and how that is causing the bug
>
> - and then only describe how it's fixed.
Thanks for your detailed explanation. I'll keep in my mind.
>
> Thanks,
>
> Ingo
>
>
prev parent reply other threads:[~2016-08-18 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 6:42 [PATCH 1/2] x86/smpboot: Check APIC ID before setting up default routing Wei Jiangang
2016-08-17 6:42 ` [PATCH 2/2] x86/apic: Update comment about disabling processor focus Wei Jiangang
2016-08-18 9:47 ` [PATCH 1/2] x86/smpboot: Check APIC ID before setting up default routing Ingo Molnar
2016-08-18 10:15 ` Wei, Jiangang [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=1471515309.7011.12.camel@localhost \
--to=weijg.fnst@cn.fujitsu.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox