From: Youquan Song <youquan.song@linux.intel.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Youquan Song <youquan.song@intel.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
tglx@linutronix.de, hpa@zytor.com, hpa@linux.intel.com,
suresh.b.siddha@intel.com, yong.y.wang@linux.intel.com,
joe@perches.com, jbaron@redhat.com, trenn@suse.de,
kent.liu@intel.com, chaohong.guo@intel.com,
Youquan Song <youquan.song@linux.intel.com>
Subject: Re: [PATCH v4 1/2] apic: Fix error interrupt report at all APs
Date: Thu, 21 Apr 2011 23:12:50 -0400 [thread overview]
Message-ID: <20110422031250.GA30016@linux-youquan.bj.intel.com> (raw)
In-Reply-To: <20110419170121.GA6640@elte.hu>
> I don't disagree with this change, but unfortunately the changelog is in
> absolutely unreadable English. Please fix it or find someone who can fix it for
> you.
>
> I decoded and fixed the changelog of the 2/2 patch of your series so no need to
> do it for that patch.
Thanks a lot Ingo!
Here is the fixed changelog for 1/2 patch :Fix error interrupt report at all APs
This patch fixes a bug reported from customer, who found many unreasonable error
interrupts reported on all APs during the system boot stage.
According to Chapter 10 of Intel Software Developer Manual Volume 3A, Local APIC
may signal an illegal vector error when an LVT entry is set as an illegal
vector value (0~15) under FIXED delivery mode (bits 8-11 is 0), regardless of
whether the mask bit is set or an interrupt actually happen. These errors are
seen as error interrupts.
The initial value of thermal LVT entries on all APs always reads 0x10000 because
APs are woken up by BSP issuing INIT-SIPI-SIPI sequence to them and LVT
registers are reset to 0s except for the mask bits which are set to 1s when APs
receive INIT IPI. When BIOS take over the thermal throttling interrupt, LVT
thermal deliver mode should be SMI and it is required to restore AP's LVT
thermal monitor register.
This issue happens when BIOS do not take over thermal throttling interrupt,
AP's LVT thermal monitor register will be restored to 0x10000 which means vector
0 and fixed deliver mode, so all APs will signal illegal vector error
interrupt. This patch check if interrupt delivery mode is not fixed mode before
restore AP's LVT thermal monitor register.
-Youquan
next prev parent reply other threads:[~2011-04-21 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 6:36 Youquan Song
2011-04-14 6:36 ` [PATCH v4 2/2] apic: Add print error interrupt reason Youquan Song
2011-04-14 7:54 ` Cyrill Gorcunov
2011-04-14 7:57 ` Cyrill Gorcunov
2011-04-19 17:48 ` [tip:x86/apic] x86, apic: Print verbose error interrupt reason on apic=debug tip-bot for Youquan Song
2011-04-19 17:01 ` [PATCH v4 1/2] apic: Fix error interrupt report at all APs Ingo Molnar
2011-04-22 3:12 ` Youquan Song [this message]
2011-04-21 15:27 ` Ingo Molnar
2011-04-22 4:34 ` Youquan Song
-- strict thread matches above, loose matches on Subject: below --
2011-04-21 16:22 Youquan Song
2011-05-12 2:19 ` Youquan Song
2011-04-06 12:20 Youquan Song
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=20110422031250.GA30016@linux-youquan.bj.intel.com \
--to=youquan.song@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chaohong.guo@intel.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=joe@perches.com \
--cc=kent.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
--cc=yong.y.wang@linux.intel.com \
--cc=youquan.song@intel.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
Powered by JetHome