From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932740AbcFRACm (ORCPT ); Fri, 17 Jun 2016 20:02:42 -0400 Received: from terminus.zytor.com ([198.137.202.10]:50494 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751095AbcFRACk (ORCPT ); Fri, 17 Jun 2016 20:02:40 -0400 User-Agent: K-9 Mail for Android In-Reply-To: <1466205799.24271.84.camel@kernel.crashing.org> References: <20160617230431.GG14480@ZenIV.linux.org.uk> <4CCEB83C-FBCF-4095-8770-892387438060@zytor.com> <1466205799.24271.84.camel@kernel.crashing.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: [off-list] a path toward killing thread_info From: "H. Peter Anvin" Date: Fri, 17 Jun 2016 17:02:00 -0700 To: Benjamin Herrenschmidt , Al Viro , Andy Lutomirski CC: Kees Cook , Peter Zijlstra , "linux-kernel@vger.kernel.org" , Ingo Molnar Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On June 17, 2016 4:23:19 PM PDT, Benjamin Herrenschmidt wrote: >On Fri, 2016-06-17 at 16:10 -0700, H. Peter Anvin wrote: >>  >> Yes. >> >> I did a half-finished patchset to do this once, in that I defined >> accessor functions which used container_of instead of pointers on >> architectures where this merge was enabled. > >How do you get to "current" in that case ? A normal per-cpu ? > >Cheers, >Ben. Yes. We already do that on x86-64 at least. -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.