From: Don Dutile <ddutile@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, Jan Beulich <jbeulich@suse.com>,
Joerg Roedel <joro@8bytes.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Malcolm Crossley <malcolm.crossley@citrix.com>,
Prarit Bhargava <prarit@redhat.com>,
Don Zickus <dzickus@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"maintainer:X86 ARCHITECTURE..." <x86@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] iommu/vt-d: Expand interrupt remapping quirk to cover x58 chipset
Date: Wed, 10 Jul 2013 13:31:36 -0400 [thread overview]
Message-ID: <51DD9A78.5040308@redhat.com> (raw)
In-Reply-To: <1373397069-8968-1-git-send-email-nhorman@tuxdriver.com>
On 07/09/2013 03:11 PM, Neil Horman wrote:
> Recently we added an early quirk to detect 5500/5520 chipsets with early
> revisions that had problems with irq draining with interrupt remapping enabled:
>
> commit 03bbcb2e7e292838bb0244f5a7816d194c911d62
> Author: Neil Horman<nhorman@tuxdriver.com>
> Date: Tue Apr 16 16:38:32 2013 -0400
>
> iommu/vt-d: add quirk for broken interrupt remapping on 55XX chipsets
>
> It turns out this same problem is present in the intel X58 chipset as well. See
> errata 69 here:
> http://www.intel.com/content/www/us/en/chipsets/x58-express-specification-update.html
>
> This patch extends the pci early quirk so that the chip devices/revisions
> specified in the above update are also covered in the same way:
>
> Signed-off-by: Neil Horman<nhorman@tuxdriver.com>
> Reviewed-by: Jan Beulich<jbeulich@suse.com>
> CC: Jan Beulich<jbeulich@suse.com>
> CC: Joerg Roedel<joro@8bytes.org>
> CC: Andrew Cooper<andrew.cooper3@citrix.com>
> CC: Malcolm Crossley<malcolm.crossley@citrix.com>
> CC: Prarit Bhargava<prarit@redhat.com>
> CC: Don Zickus<dzickus@redhat.com>
> CC: Don Dutile<ddutile@redhat.com>
> CC: Thomas Gleixner<tglx@linutronix.de>
> CC: Ingo Molnar<mingo@redhat.com>
> CC: "H. Peter Anvin"<hpa@zytor.com>
> CC: x86@kernel.org (maintainer:X86 ARCHITECTURE...)
> CC: stable@vger.kernel.org
> ---
> arch/x86/kernel/early-quirks.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/early-quirks.c b/arch/x86/kernel/early-quirks.c
> index 94ab6b9..743d583 100644
> --- a/arch/x86/kernel/early-quirks.c
> +++ b/arch/x86/kernel/early-quirks.c
> @@ -196,15 +196,23 @@ static void __init ati_bugs_contd(int num, int slot, int func)
> static void __init intel_remapping_check(int num, int slot, int func)
> {
> u8 revision;
> + u16 device;
>
> + device = read_pci_config_16(num, slot, func, PCI_DEVICE_ID);
> revision = read_pci_config_byte(num, slot, func, PCI_REVISION_ID);
>
> /*
> - * Revision 0x13 of this chipset supports irq remapping
> - * but has an erratum that breaks its behavior, flag it as such
> + * Revision 13 of all triggering devices id in this quirk have
> + * a problem draining interrupts when irq remapping is enabled,
> + * and should be flagged as broken. Additionally revisions 0x12
> + * and 0x22 of device id 0x3405 has this problem.
> */
> if (revision == 0x13)
> set_irq_remapping_broken();
> + else if ((device == 0x3405)&&
> + ((revision == 0x12) ||
> + (revision == 0x22)))
> + set_irq_remapping_broken();
>
> }
>
When discussing the original-seen errata w/Intel on 55xx chips, the
statements made were any chip with rev C1(revision = 0x21) or greater had the
correct
hw implementation for the intr-pending flush.
We knew the bug existed in the A3 (rev=0x13) rev of the chip, but the
true check should be:
revision < 0x21
I suspect there were multiple revs of the x58, of which B2(0x12) & C2(0x22)
were shipped to oem's, system vendors, etc.
But, in case there were any chip revisions in between these well-known values
out there, I suggest the 0x3405 check be changed to:
revision < 0x22
Since it's unlikely that hw degressed in design over revisions, it seems
more correct to check for revs less than a rev-value having an errata,
or conversely, a chip value >= rev-value do not have the errata.
IOW, an equal check may not provide sufficient.
- Don
> @@ -239,8 +247,11 @@ static struct chipset early_qrk[] __initdata = {
> PCI_CLASS_SERIAL_SMBUS, PCI_ANY_ID, 0, ati_bugs_contd },
> { PCI_VENDOR_ID_INTEL, 0x3403, PCI_CLASS_BRIDGE_HOST,
> PCI_BASE_CLASS_BRIDGE, 0, intel_remapping_check },
> + { PCI_VENDOR_ID_INTEL, 0x3405, PCI_CLASS_BRIDGE_HOST,
> + PCI_BASE_CLASS_BRIDGE, 0, intel_remapping_check },
> { PCI_VENDOR_ID_INTEL, 0x3406, PCI_CLASS_BRIDGE_HOST,
> PCI_BASE_CLASS_BRIDGE, 0, intel_remapping_check },
> +
> {}
> };
>
next prev parent reply other threads:[~2013-07-10 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 19:11 [PATCH] iommu/vt-d: Expand interrupt remapping quirk to cover x58 chipset Neil Horman
2013-07-10 17:31 ` Don Dutile [this message]
2013-07-11 10:59 ` Neil Horman
2013-07-16 11:33 ` Neil Horman
2013-07-17 11:13 ` Neil Horman
2013-07-17 13:04 ` Don Dutile
2013-07-24 3:55 ` [tip:x86/urgent] x86/iommu/vt-d: " tip-bot for Neil Horman
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=51DD9A78.5040308@redhat.com \
--to=ddutile@redhat.com \
--cc=andrew.cooper3@citrix.com \
--cc=dzickus@redhat.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malcolm.crossley@citrix.com \
--cc=mingo@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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 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.