From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754221AbbK0Ilz (ORCPT ); Fri, 27 Nov 2015 03:41:55 -0500 Received: from mail-wm0-f50.google.com ([74.125.82.50]:37565 "EHLO mail-wm0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751101AbbK0Ilu (ORCPT ); Fri, 27 Nov 2015 03:41:50 -0500 Date: Fri, 27 Nov 2015 09:41:45 +0100 From: Ingo Molnar To: "Jason A. Donenfeld" Cc: Thomas Gleixner , mingo@redhat.com, hpa@zytor.com, LKML Subject: Re: irq_fpu_usable() is irreliable Message-ID: <20151127084145.GA26693@gmail.com> References: <20151118065508.GA18849@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Jason A. Donenfeld wrote: > Hi Ingo, > > The plot thickens, once again. > > > > Also, what CPU does the test system have, Intel or AMD? The FPU behavior can be > > > very different in the two cases. > > Intel 3820QM, but inside VMWare Workstation 12. > > Trying this on bare metal, the problem goes away! Though the VM is 4.2 > and my bare metal is 4.3. Perhaps your recent changes did something. > > But more likely, there's some funny business happening with VMWare. > Any speculation about this? Fascinating issue... I have no idea unfortunately :-( You might want to take it up with the vmware guys. Thanks, Ingo