From: Alex Williamson <alex.williamson@redhat.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Add ACS quirk for Intel 300 series chipset
Date: Wed, 15 Aug 2018 15:21:39 -0600 [thread overview]
Message-ID: <20180815152139.4e469fd4@t450s.home> (raw)
In-Reply-To: <20180427104423.2203-1-mika.westerberg@linux.intel.com>
On Fri, 27 Apr 2018 13:44:23 +0300
Mika Westerberg <mika.westerberg@linux.intel.com> wrote:
> Intel 300 series chipset still has the same ACS issue than the previous
> generations so extend the ACS quirk to cover it as well.
>
> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
> ---
> drivers/pci/quirks.c | 6 ++++++
> 1 file changed, 6 insertions(+)
There seems to be some suspicion whether this patch is correct, see
link below[1]. The user lists a kernel "4.14.36-1-lts" where lspci
shows the ACSCtl register with SV, RR, and CR enabled. AIUI how
previous Intel root ports were defective in this regard, a dword
register was used for the ACS capability and control field rather than
the spec defined word register, therefore the upper half of each
mal-sized register was reserved. I don't think lspci has gained any
insight into this quirk, so showing those control values enabled
suggests this hardware might actually not require the quirk.
The second listing for v4.17 (and I don't know if this is actually
v4.17.10 which would include the stable backport of this patch or
v4.17.0) shows the ACSCtl register as zero. This is what we'd see if
the hardware does have this errata OR if we applied the quirk to
hardware that doesn't require it. The existence of the first listing
kind of suggests the latter.
Is there a datasheet available to support this quirk? Thanks,
Alex
[1]https://www.reddit.com/r/VFIO/comments/97da1s/intel_c246_suspect_300_series_acs_quirk_breaks/
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index 2990ad1e7c99..7a0f41176369 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
> @@ -4230,6 +4230,11 @@ static int pci_quirk_qcom_rp_acs(struct pci_dev *dev, u16 acs_flags)
> * 0xa290-0xa29f PCI Express Root port #{0-16}
> * 0xa2e7-0xa2ee PCI Express Root port #{17-24}
> *
> + * The 300 series chipset suffers from the same bug so include those root
> + * ports here as well.
> + *
> + * 0xa32c-0xa343 PCI Express Root port #{0-24}
> + *
> * [1] http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-datasheet-vol-2.html
> * [2] http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-datasheet-vol-1.html
> * [3] http://www.intel.com/content/www/us/en/chipsets/100-series-chipset-spec-update.html
> @@ -4244,6 +4249,7 @@ static bool pci_quirk_intel_spt_pch_acs_match(struct pci_dev *dev)
> switch (dev->device) {
> case 0xa110 ... 0xa11f: case 0xa167 ... 0xa16a: /* Sunrise Point */
> case 0xa290 ... 0xa29f: case 0xa2e7 ... 0xa2ee: /* Union Point */
> + case 0xa32c ... 0xa343: /* 300 series */
> return true;
> }
>
next prev parent reply other threads:[~2018-08-16 0:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 10:44 [PATCH] PCI: Add ACS quirk for Intel 300 series chipset Mika Westerberg
2018-04-27 18:10 ` Bjorn Helgaas
2018-04-29 7:03 ` Mika Westerberg
2018-08-15 21:21 ` Alex Williamson [this message]
2018-08-15 22:43 ` Alex Williamson
2018-08-16 6:10 ` Mika Westerberg
2018-08-16 15:13 ` Alex Williamson
2018-08-16 19:28 ` Mika Westerberg
2018-08-16 20:25 ` Alex Williamson
2018-08-17 9:37 ` Mika Westerberg
2018-09-05 9:58 ` Mika Westerberg
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=20180815152139.4e469fd4@t450s.home \
--to=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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).