Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965062AbWEJXFw (ORCPT ); Wed, 10 May 2006 19:05:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965063AbWEJXFv (ORCPT ); Wed, 10 May 2006 19:05:51 -0400 Received: from ozlabs.org ([203.10.76.45]:54159 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S965062AbWEJXFu (ORCPT ); Wed, 10 May 2006 19:05:50 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17506.29128.591758.502430@cargo.ozlabs.ibm.com> Date: Thu, 11 May 2006 09:05:44 +1000 From: Paul Mackerras To: Richard Henderson Cc: t@twiddle.net, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linuxppc-dev@ozlabs.org Subject: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables In-Reply-To: <20060510154702.GA28938@twiddle.net> References: <17505.26159.807484.477212@cargo.ozlabs.ibm.com> <20060510154702.GA28938@twiddle.net> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 671 Lines: 31 Richard Henderson writes: > How do you plan to address the compiler optimizing > > __thread int foo; > { > use(foo); > schedule(); > use(foo); > } > > into > > { > int *tmp = &foo; // tls arithmetic here > use(*tmp); > schedule(); > use(*tmp); > } Hmmm... Would it be sufficient to use a RELOC_HIDE in __get_cpu_var, like this? #define __get_cpu_var(x) (*(RELOC_HIDE(&per_cpu__##x, 0))) Paul. - 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/