linux-kernel - Re: Workaround for Intel MPS errata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 05 Oct 2011 14:09:29 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Jon Mason <jdmason@...zu.us>
CC:	Jon Mason <mason@...i.com>, Sven Schnelle <svens@...ckframe.org>,
	Simon Kirby <sim@...tway.ca>,
	Eric Dumazet <eric.dumazet@...il.com>,
	Niels Ole Salscheider <niels_ole@...scheider-online.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Ben Hutchings <bhutchings@...arflare.com>
Subject: Re: Workaround for Intel MPS errata

On 10/05/2011 05:46 AM, Jon Mason wrote:
> Hey Avi,
> I believe this will fix the issue (assuming the errata is the issue in
> the first place).  You'll need to apply the patch on top of Linus'
> latest code and re-enable the MPS tuning (as it is now off by
> default).  This can be done by adding "pci=pcie_bus_safe" to your boot
> args.
>
> After thinking about it some more, a PCI quark is the correct way of
> doing things.  We must always disable read completion coalescing due
> to the possibility of hotplugging a device with a MPS of 256B.  Also,
> I believe everyone will think this is much cleaner.

Agree.

> Let me know how it goes and thanks again for testing this for me.

Works perfectly now.  Thanks.

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/