From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934730AbbIVUkJ (ORCPT ); Tue, 22 Sep 2015 16:40:09 -0400 Received: from canardo.mork.no ([148.122.252.1]:55028 "EHLO canardo.mork.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934612AbbIVUkH convert rfc822-to-8bit (ORCPT ); Tue, 22 Sep 2015 16:40:07 -0400 From: =?utf-8?Q?Bj=C3=B8rn_Mork?= To: Linus Torvalds Cc: Tejun Heo , Herbert Xu , David Miller , Cong Wang , Tom Herbert , kafai@fb.com, kernel-team@fb.com, Linux Kernel Mailing List , Network Development , =?utf-8?B?SmnFmcOtIFDDrXJrbw==?= , Nicolas Dichtel , Thomas Graf , Scott Feldman Subject: Re: [PATCH v2] netlink: Replace rhash_portid with bound Organization: m References: <20150920.225521.1063980101511317898.davem@davemloft.net> <20150921060636.GA30807@gondor.apana.org.au> <20150920.231104.525285577747035896.davem@davemloft.net> <20150921133415.GA1740@gondor.apana.org.au> <20150921182022.GB13263@mtj.duckdns.org> <20150922033856.GA7851@gondor.apana.org.au> <20150922161056.GB9761@mtj.duckdns.org> <20150922185357.GD17659@mtj.duckdns.org> <20150922195059.GF17659@mtj.duckdns.org> Date: Tue, 22 Sep 2015 22:36:59 +0200 In-Reply-To: (Linus Torvalds's message of "Tue, 22 Sep 2015 13:03:18 -0700") Message-ID: <87wpvii42c.fsf@nemi.mork.no> User-Agent: Gnus/5.130013 (Ma Gnus v0.13) Emacs/24.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.11 (canardo.mork.no [IPv6:2001:4641::1]); Tue, 22 Sep 2015 22:37:08 +0200 (CEST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds writes: > The PPRO_FENCE_BUG thing is rather questionable. I'm not sure it's > even documented, but I can't find the official PPro errata now. I > think I discussed it with Andy Glew back when Intel was starting to > document the memory ordering rules. > > I'd be willing to get rid of it. It was apparently just an early > stepping or two. > > Anybody with better google-fu than me who can find the official Intel > PPro errata? http://download.intel.com/design/archives/processors/pro/docs/24268935.pdf Says "NoFix" for erratas 66 and 92. Bjørn