From: Ingo Molnar <mingo@kernel.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] x86/apic changes for v3.14
Date: Mon, 24 Mar 2014 10:24:37 +0100 [thread overview]
Message-ID: <20140324092437.GA9344@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.10.1403222327130.21669@eddie.linux-mips.org>
* Maciej W. Rozycki <macro@linux-mips.org> wrote:
> IMPLICATION: There is a possibility of clearing the Error register
> status since the write to the register is not specifically blocked.
>
> WORKAROUND: Writes should not occur to the Pentium processor APIC
> Error register.
>
> STATUS: For the steppings affected see the Summary Table of Changes
> at the beginning of this section."
>
> The steppings affected are actually: B1, B3 and B5. Do we want to
> keep supporting them? I think yes, we already handle the erratum
> elsewhere (lapic_setup_esr). So how about:
>
> if (lapic_get_maxlvt() > 3) /* Due to the Pentium erratum 3AP. */
> apic_write(APIC_ESR, 0);
> v = apic_read(APIC_ESR);
>
> instead? I can make a patch if that would make your life easier.
Sure, a patch would be helpful.
> There's room for optimisation here, but I think it's not worth the
> effort as this is a slow path, APIC error interrupts are not
> supposed to happen and are I believe extremely uncommon with FSB
> message delivery.
Agreed.
Thanks,
Ingo
prev parent reply other threads:[~2014-03-24 9:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 13:42 [GIT PULL] x86/apic changes for v3.14 Ingo Molnar
2014-03-23 0:00 ` Maciej W. Rozycki
2014-03-24 9:24 ` Ingo Molnar [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=20140324092437.GA9344@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.