From: "H. Peter Anvin" Subject: Re: [RFC 16/22] x86/percpu: Adapt percpu for PIE support Date: Wed, 19 Jul 2017 20:03:16 -0700 Message-ID: References: <20170718223333.110371-1-thgarnie@google.com> <20170718223333.110371-17-thgarnie@google.com> <25a2974a-fbb4-ea4b-d090-582d6d0de7fd@zytor.com> <9b152d55-8a1a-75b5-58df-0fe33458107a@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Herbert Xu , "David S . Miller" , Thomas Gleixner , Ingo Molnar , Peter Zijlstra , Josh Poimboeuf , Arnd Bergmann , Matthias Kaehlcke , Boris Ostrovsky , Juergen Gross , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Joerg Roedel , Andy Lutomirski , Borislav Petkov , "Kirill A . Shutemov" , Borislav Petkov , Christian Borntraeger , "Rafael J . Wysocki" , Len Brown , Brian Gerst Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <9b152d55-8a1a-75b5-58df-0fe33458107a@zytor.com> Content-Language: en-US List-Id: linux-crypto.vger.kernel.org On 07/19/17 19:21, H. Peter Anvin wrote: > On 07/19/17 16:33, H. Peter Anvin wrote: >>> >>> I agree that it is odd but that's how the compiler generates code. I >>> will re-explore PIC options with mcmodel=small or medium, as mentioned >>> on other threads. >> >> Why should the way compiler generates code affect the way we do things >> in assembly? >> >> That being said, the compiler now has support for generating this kind >> of code explicitly via the __seg_gs pointer modifier. That should let >> us drop the __percpu_prefix and just use variables directly. I suspect >> we want to declare percpu variables as "volatile __seg_gs" to account >> for the possibility of CPU switches. >> >> Older compilers won't be able to work with this, of course, but I think >> that it is acceptable for those older compilers to not be able to >> support PIE. >> > > Grump. It turns out that the compiler doesn't do the right thing for > symbols marked with the __seg_[fg]s markers. __thread does the right > thing, but __thread a) has %fs: hard-coded, still, and b) I believe can > still cache %seg:0 arbitrarily long. I filed this bug report for gcc: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81490 It might still be possible to work around this by playing really ugly games with __thread, but I haven't yet figured out how best to do that. -hpa