Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 22 Jul 2019 23:07:04 +0200
From:   Peter Zijlstra <peterz@infradead.org>
To:     Nadav Amit <namit@vmware.com>
Cc:     Andy Lutomirski <luto@kernel.org>, x86@kernel.org,
        linux-kernel@vger.kernel.org,
        Dave Hansen <dave.hansen@linux.intel.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>
Subject: Re: [RFC 7/7] x86/current: Aggressive caching of current
Message-ID: <20190722210704.GL6698@worktop.programming.kicks-ass.net>
References: <20190718174110.4635-1-namit@vmware.com>
 <20190718174110.4635-8-namit@vmware.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190718174110.4635-8-namit@vmware.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, Jul 18, 2019 at 10:41:10AM -0700, Nadav Amit wrote:
> The current_task is supposed to be constant in each thread and therefore
> does not need to be reread. There is already an attempt to cache it
> using inline assembly, using this_cpu_read_stable(), which hides the
> dependency on the read memory address.

Is that what it does?!, I never quite could understand
percpu_stable_op().