From: Thomas Gleixner <tglx@linutronix.de>
To: Kar Hin Ong <kar.hin.ong@ni.com>, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"x86\@kernel.org" <x86@kernel.org>,
"linux-pci\@vger.kernel.org" <linux-pci@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Julia Cartwright <julia.cartwright@ni.com>,
Keng Soon Cheah <keng.soon.cheah@ni.com>,
Gratian Crisan <gratian.crisan@ni.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: RE: RE: Re: "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system
Date: Thu, 16 Jan 2020 11:01:52 +0100 [thread overview]
Message-ID: <87muanwwhb.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <MN2PR04MB62551D8B240966B02ED71516C3360@MN2PR04MB6255.namprd04.prod.outlook.com>
Kar Hin Ong <kar.hin.ong@ni.com> writes:
>> I don't have access to the document you mentioned, but I know that chipsets
>> have a knob to control that behaviour. Just checked a few chipset docs and they
>> contain the same sentence, but then in the next paragraph they say:
>>
>> "If the I/OxAPIC entry is masked (via the mask bit in the corresponding
>> Redirection Table Entry), then the corresponding PCI Express
>> interrupt(s) is forwarded to the legacy ICH, provided the Disable PCI
>> INTx Routing to ICH bit is clear, Section 19.10.2.27, QPIPINTRC: Intel
>> QuickPath Interconnect Protocol Interrupt Control."
>>
>> That control bit is 0 after reset, so the legacy forwarding works.
>
> Intel support engineer do provide similar advice to us as a workaround
> to the CPU behaviour. They said we could enable the "Don'tRouteToPCH"
> bit in the BIOS to block the interrupt from propagating to PCH. This
> bit is located at "Coherent Interface Protocol Interrupt Control
> (cipintrc)" register of "Virtualization" device (Bus 0, Device 5,
> Function 0, Offset 0x14C).
>
> With the help of our BIOS engineer, after setting this bit in BIOS
> does prevent the interrupt forwarding.
>
> However, Intel told us that this workaround is not validated, i.e. the
> side effect of setting this bit is unknown.
What? That's ridiculous.
That bit is documented in various chipset documents and that legacy
rerouting is really just there to support OSes which do not support
multiple IO-APICs properly.
If setting this bit has unknown side effects then someone at Intel
should have a close look and fix their documentation.
Can the Intel people on Cc please take care of this?
As we have already quirks in drivers/pci/quirks.c which handle the same
issue on older chipsets, we really should add one for these kind of
systems to avoid fiddling with the BIOS (which you can, but most people
cannot).
Thanks,
tglx
next prev parent reply other threads:[~2020-01-16 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 3:53 "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system Kar Hin Ong
2019-10-31 23:05 ` Bjorn Helgaas
2019-11-01 7:46 ` Kar Hin Ong
2019-11-04 23:41 ` Thomas Gleixner
2019-11-07 9:38 ` Kar Hin Ong
2019-11-21 11:22 ` Kar Hin Ong
2020-01-15 23:05 ` Thomas Gleixner
2020-01-16 7:32 ` Kar Hin Ong
2020-01-16 10:01 ` Thomas Gleixner [this message]
2020-01-23 1:37 ` Sean V Kelley
2020-01-23 13:08 ` Thomas Gleixner
2020-02-09 15:37 ` Thomas Gleixner
2020-02-10 16:32 ` Sean V Kelley
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=87muanwwhb.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=gratian.crisan@ni.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=julia.cartwright@ni.com \
--cc=kar.hin.ong@ni.com \
--cc=keng.soon.cheah@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).