From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750761AbWGLWOT (ORCPT ); Wed, 12 Jul 2006 18:14:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751032AbWGLWOT (ORCPT ); Wed, 12 Jul 2006 18:14:19 -0400 Received: from ns2.suse.de ([195.135.220.15]:18653 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S1750750AbWGLWOS (ORCPT ); Wed, 12 Jul 2006 18:14:18 -0400 From: Andi Kleen To: Chuck Ebbert <76306.1226@compuserve.com> Subject: Re: [patch] let CONFIG_SECCOMP default to n II Date: Thu, 13 Jul 2006 00:14:14 +0200 User-Agent: KMail/1.9.3 Cc: Alan Cox , Arjan van de Ven , Ingo Molnar , Adrian Bunk , linux-kernel , Linus Torvalds , andrea References: <200607121739_MC3-1-C4D3-28B9@compuserve.com> <200607122357.48045.ak@suse.de> In-Reply-To: <200607122357.48045.ak@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607130014.14254.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wednesday 12 July 2006 23:57, Andi Kleen wrote: > > > We can just fold the TSC disable stuff into the new thread_flags test > > at context-switch time: > > I don't think it will work because you need to check state of > both previous and next task. The thread_flags test only checks the > state of the next task. Actually scratch that objection. It should work just fine and would indeed turn it into zero overhead for the common case. Still I don't think it's actually needed so there might be still a good case to remove it. -Andi