From: Bjorn Helgaas <helgaas@kernel.org>
To: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Borislav Petkov <bp@suse.de>,
Jean Delvare <jdelvare@suse.com>, Jean Delvare <jdelvare@suse.de>
Subject: Re: [PATCH v3 RESEND] acpi,pci: warn about duplicate IRQ routing entries returned from _PRT
Date: Mon, 23 Jan 2023 14:33:01 -0600 [thread overview]
Message-ID: <20230123203301.GA909338@bhelgaas> (raw)
In-Reply-To: <20230121153314.6109-1-mat.jonczyk@o2.pl>
On Sat, Jan 21, 2023 at 04:33:14PM +0100, Mateusz Jończyk wrote:
> On some platforms, the ACPI _PRT function returns duplicate interrupt
> routing entries. Linux uses the first matching entry, but sometimes the
> second matching entry contains the correct interrupt vector.
>
> Print an error to dmesg if duplicate interrupt routing entries are
> present, so that we could check how many models are affected.
It shouldn't be too hard to use qemu to figure out whether Windows
uses the last matching entry, i.e., treating _PRT entries as
assignments. If so, maybe Linux could just do the same.
Is anybody up for that?
Bjorn
next prev parent reply other threads:[~2023-01-23 20:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 15:33 [PATCH v3 RESEND] acpi,pci: warn about duplicate IRQ routing entries returned from _PRT Mateusz Jończyk
2023-01-23 20:33 ` Bjorn Helgaas [this message]
2023-01-23 21:00 ` Mateusz Jończyk
2023-01-23 21:44 ` Bjorn Helgaas
2023-01-30 15:56 ` Rafael J. Wysocki
2023-01-30 17:45 ` Bjorn Helgaas
2023-01-30 19:36 ` Mateusz Jończyk
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=20230123203301.GA909338@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=jdelvare@suse.com \
--cc=jdelvare@suse.de \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mat.jonczyk@o2.pl \
--cc=rafael@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 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.