Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267904AbUIPLD6 (ORCPT ); Thu, 16 Sep 2004 07:03:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267918AbUIPLD6 (ORCPT ); Thu, 16 Sep 2004 07:03:58 -0400 Received: from colin2.muc.de ([193.149.48.15]:1810 "HELO colin2.muc.de") by vger.kernel.org with SMTP id S267904AbUIPLD4 (ORCPT ); Thu, 16 Sep 2004 07:03:56 -0400 Date: 16 Sep 2004 13:03:55 +0200 Date: Thu, 16 Sep 2004 13:03:55 +0200 From: Andi Kleen To: William Lee Irwin III , Albert Cahalan , Jakub Jelinek , Albert Cahalan , linux-kernel mailing list Subject: Re: get_current is __pure__, maybe __const__ even Message-ID: <20040916110355.GA20448@muc.de> References: <1095288600.1174.5968.camel@cube> <20040915231518.GB31909@devserv.devel.redhat.com> <20040915232956.GE9106@holomorphy.com> <1095300619.2191.6392.camel@cube> <20040916023604.GH9106@holomorphy.com> <20040916100419.A31029@flint.arm.linux.org.uk> <20040916091128.GA55409@muc.de> <20040916103045.B31029@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040916103045.B31029@flint.arm.linux.org.uk> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 583 Lines: 13 > The scheduler quite rightly expects, for any thread, that any variable > which may be stored in a CPU register before the context switch has the > same value as after the context switch. Just current isn't a varible, it's some inline assembly in a inline function. The question was if that function could be marked const/pure. -Andi - 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/