Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752082AbaATI0x (ORCPT ); Mon, 20 Jan 2014 03:26:53 -0500 Received: from merlin.infradead.org ([205.233.59.134]:50414 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765AbaATI0t (ORCPT ); Mon, 20 Jan 2014 03:26:49 -0500 Date: Mon, 20 Jan 2014 09:26:20 +0100 From: Peter Zijlstra To: Len Brown Cc: Stephen Rothwell , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , linux-next@vger.kernel.org, "linux-kernel@vger.kernel.org" Subject: Re: linux-next: build failure after merge of the tip tree Message-ID: <20140120082620.GB30183@twins.programming.kicks-ass.net> References: <20140116145829.5e4fcab103b1c5c77501ee77@canb.auug.org.au> <20140116121955.GQ31570@twins.programming.kicks-ass.net> <20140117074628.88698f59939c9002b7c12968@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 19, 2014 at 11:45:43PM -0500, Len Brown wrote: > +static void mwait_idle(void) > +{ > + mwait_idle_with_hints(0, 0); > +} > + > > The reason the patch above will crash Core2 machines is because > core2 machines don't support mwait_idle_with_hints(). > > The calling sequence for old and new MWAIT instructions is different. > The former must be invoked with interrupts enabled, > and the later can be invoked with interrupts disabled, > which is a feature that Linux takes advantage of. What old and new? They're the same byte sequence: 0x0f 0x01 0xc9 And your 'old' __sti_mwait(0,0) has the exact same arguments as mwait_idle_with_hints(0,0). -- 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/