Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756411AbYHKW5X (ORCPT ); Mon, 11 Aug 2008 18:57:23 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752225AbYHKW5M (ORCPT ); Mon, 11 Aug 2008 18:57:12 -0400 Received: from mga14.intel.com ([143.182.124.37]:3696 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752036AbYHKW5L (ORCPT ); Mon, 11 Aug 2008 18:57:11 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.32,191,1217833200"; d="scan'208";a="32534765" Date: Mon, 11 Aug 2008 15:57:09 -0700 From: Suresh Siddha To: "H. Peter Anvin" Cc: Herbert Xu , "Siddha, Suresh B" , Wolfgang Walter , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Ingo Molnar , "viro@ZenIV.linux.org.uk" , "vegard.nossum@gmail.com" , austin zhang Subject: Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state changes Message-ID: <20080811225709.GO13158@linux-os.sc.intel.com> References: <200808081236.55172.wolfgang.walter@stwm.de> <20080808185356.GC607@linux-os.sc.intel.com> <489C97FB.2030408@zytor.com> <20080808231121.GA13158@linux-os.sc.intel.com> <20080809003829.GA25926@gondor.apana.org.au> <20080809142918.GA30387@gondor.apana.org.au> <20080809143259.GA30451@gondor.apana.org.au> <20080809175247.GD13158@linux-os.sc.intel.com> <20080810053048.GA3171@gondor.apana.org.au> <489E7F9C.9000708@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <489E7F9C.9000708@zytor.com> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 809 Lines: 18 On Sat, Aug 09, 2008 at 10:41:48PM -0700, H. Peter Anvin wrote: > Herbert Xu wrote: > > On Sat, Aug 09, 2008 at 10:52:48AM -0700, Suresh Siddha wrote: > >>> Actually I was mistaken, Intel has done the right thing by not > >>> generating a fault on crc32c with TS set. > >> Yes, the documentation seems to says so. But I am double checking > >> with experts inside, to make sure we got the SDM right. I got confirmation that crc32 instructions don't generate DNA when cr0.TS bit is set. So no changes required for Austin's patches in this context. thanks, suresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/