From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
wfg@linux.intel.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
x86@kernel.org
Subject: Re: [Bugfix 1/2] ACPI, PCI, irq: Do not share PCI IRQ with ISA IRQ
Date: Mon, 28 Sep 2015 15:57:03 +0200 [thread overview]
Message-ID: <3135859.72R7vY9K7x@vostro.rjw.lan> (raw)
In-Reply-To: <20150925234040.GB23134@localhost>
On Friday, September 25, 2015 06:40:40 PM Bjorn Helgaas wrote:
> On Thu, Sep 17, 2015 at 02:02:45PM +0800, Jiang Liu wrote:
> > Avoid IRQs occupied by ISA IRQs when allocating IRQs for PCI link devices,
> > otherwise it may cause interrupt storm due to incompatible pin attributes.
> >
> > This issue was triggered on a KVM virtual machine, which
> > 1) uses IRQ9 for SCI in high level mode.
> > 2) defines an PCI interrupt link device (LNKS) with IRQ9 as the only
> > possible irq.
> > 3) has an PCI device referring to link device LNKS.
> > So it causes interrupt storm when enabling the PCI device because PCI IRQ
> > works in low level mode.
> >
> > Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
Thanks!
Queued up both this and the [2/2] for 4.3-rc4.
Thanks,
Rafael
prev parent reply other threads:[~2015-09-28 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 6:02 Jiang Liu
2015-09-17 6:02 ` [Bugfix 2/2] ACPI / PCI: Remove duplicated penalty on SCI IRQ Jiang Liu
2015-09-25 23:41 ` Bjorn Helgaas
2015-09-25 23:40 ` [Bugfix 1/2] ACPI, PCI, irq: Do not share PCI IRQ with ISA IRQ Bjorn Helgaas
2015-09-28 13:57 ` Rafael J. Wysocki [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=3135859.72R7vY9K7x@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=jiang.liu@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=wfg@linux.intel.com \
--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
all inboxes | Powered by JetHome®