From: Kar Hin Ong <kar.hin.ong@ni.com>
To: Thomas Gleixner <tglx@linutronix.de>, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-x86_64@vger.kernel.org" <linux-x86_64@vger.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>
Subject: RE: Re: "oneshot" interrupt causes another interrupt to be fired erroneously in Haswell system
Date: Thu, 21 Nov 2019 11:22:19 +0000 [thread overview]
Message-ID: <MN2PR04MB6255F9C4B0449BA0CE36CFA2C34E0@MN2PR04MB6255.namprd04.prod.outlook.com> (raw)
In-Reply-To: <MN2PR04MB625594021250E0FB92EC955DC3780@MN2PR04MB6255.namprd04.prod.outlook.com>
> > The workarounds for this are enabled by PCI quirls and either
> > CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y or 'ioapicreroute' on
> the
> > command line.
> >
> > It might be wortha try to add the PCI ID of that box to the quirk
> > list, i.e. the PCI ID matches in drivers/pci/quirks.c which belong to
> > the
> > function: quirk_reroute_to_boot_interrupts_intel().
>
> Do you mean adding the PCI ID of the device that actually fires interrupt? It
> can be any PCI card though (example: external ETH controller, data
> acquisition module, etc).
> Or you mean to add the ID of all PCIe root ports that routed to IOAPIC 2?
>
> Based on Haswell specification, seems like every entry on IOAPIC 2 will
> experience this problem.
> If to reroute every entry on IOAPIC 2 to IOAPIC 1, probably we should just
> disable IOAPIC 2 instead?
Hi Thomas, Bjorn,
Any thoughts on this?
Thanks.
Kar Hin Ong
next prev parent reply other threads:[~2019-11-21 11:28 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 [this message]
2020-01-15 23:05 ` Thomas Gleixner
2020-01-16 7:32 ` Kar Hin Ong
2020-01-16 10:01 ` Thomas Gleixner
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=MN2PR04MB6255F9C4B0449BA0CE36CFA2C34E0@MN2PR04MB6255.namprd04.prod.outlook.com \
--to=kar.hin.ong@ni.com \
--cc=dave.hansen@linux.intel.com \
--cc=helgaas@kernel.org \
--cc=hpa@zytor.com \
--cc=julia.cartwright@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=linux-x86_64@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).