From: "Rolf Eike Beer" <eike-kernel@sf-tec.de>
To: "Jon Mason" <mason@myri.com>
Cc: "Avi Kivity" <avi@redhat.com>,
"Sven Schnelle" <svens@stackframe.org>,
"Simon Kirby" <sim@hostway.ca>,
"Eric Dumazet" <eric.dumazet@gmail.com>,
"Niels Ole Salscheider" <niels_ole@salscheider-online.de>,
"Jesse Barnes" <jbarnes@virtuousgeek.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"Ben Hutchings" <bhutchings@solarflare.com>
Subject: Re: Workaround for Intel MPS errata
Date: Fri, 30 Sep 2011 09:03:24 +0200 [thread overview]
Message-ID: <fc03678ef8baaa29a8ab3c086ba6bb78.squirrel@webmail.sf-mail.de> (raw)
In-Reply-To: <20110930001633.GA11436@myri.com>
> Hey Avi,
> Can you try this patch? It should resolve the issue you are seeing.
>
> Thanks,
> Jon
>
> PCI: Workaround for Intel MPS errata
>
> Intel 5000 and 5100 series memory controllers have a known issue if
> read
> completion coalescing is enabled (the default setting) and the PCI-E
> Maximum Payload Size is set to 256B. To work around this issue,
> disable
> read completion coalescing if the MPS is 256B.
>
> http://www.intel.com/content/dam/doc/specification-update/5000-chipset-memory-controller-hub-specification-update.pdf
> http://www.intel.com/content/dam/doc/specification-update/5100-memory-controller-hub-chipset-specification-update.pdf
>
> Reported-by: Avi Kivity <avi@redhat.com>
> Signed-off-by: Jon Mason <mason@myri.com>
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index a919db2..13c733a 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -1361,6 +1361,80 @@ static int pcie_find_smpss(struct pci_dev *dev,
> void *data)
> return 0;
> }
>
> +static void pcie_errata_check(int mps)
> +{
While this whole function is about Intel 5x00 devices the name of it is
very generic (and in a very generic file). Maybe this can be changed, e.g.
"fixup:" renamed to "fixup_intel_5x00:". Also I wonder if that shouldn't
be a nop when CONFIG_PCI_QUIRKS is not set.
Eike
next prev parent reply other threads:[~2011-09-30 7:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-27 17:01 [REGRESSION] e1000e failure triggered by "PCI: Remove MRRS modification from MPS setting code" Avi Kivity
2011-09-27 17:59 ` Jon Mason
2011-09-27 18:28 ` Avi Kivity
2011-09-27 20:11 ` Jon Mason
2011-09-29 4:33 ` Benjamin Herrenschmidt
2011-09-29 13:53 ` Jon Mason
2011-09-30 0:16 ` Workaround for Intel MPS errata Jon Mason
2011-09-30 2:21 ` Jesse Brandeburg
2011-09-30 2:51 ` Jon Mason
2011-09-30 5:01 ` Bjorn Helgaas
2011-09-30 15:35 ` Jon Mason
2011-09-30 17:17 ` Bjorn Helgaas
2011-09-30 17:38 ` Jon Mason
2011-09-30 17:57 ` Bjorn Helgaas
2011-09-30 7:03 ` Rolf Eike Beer [this message]
2011-09-30 15:39 ` Jon Mason
2011-10-02 9:26 ` Avi Kivity
2011-10-03 4:58 ` Jon Mason
2011-10-03 10:11 ` Avi Kivity
2011-10-03 15:12 ` Jon Mason
2011-10-04 9:46 ` Avi Kivity
2011-10-04 13:06 ` Avi Kivity
2011-10-04 13:11 ` Jon Mason
2011-10-04 20:12 ` Jon Mason
2011-10-05 3:46 ` Jon Mason
2011-10-05 12:09 ` Avi Kivity
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=fc03678ef8baaa29a8ab3c086ba6bb78.squirrel@webmail.sf-mail.de \
--to=eike-kernel@sf-tec.de \
--cc=avi@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=eric.dumazet@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mason@myri.com \
--cc=niels_ole@salscheider-online.de \
--cc=sim@hostway.ca \
--cc=svens@stackframe.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome