From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934434AbbIVUWp (ORCPT ); Tue, 22 Sep 2015 16:22:45 -0400 Received: from www.sr71.net ([198.145.64.142]:41812 "EHLO blackbird.sr71.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933729AbbIVUWo (ORCPT ); Tue, 22 Sep 2015 16:22:44 -0400 Subject: Re: [PATCH 11/26] x86, pkeys: add functions for set/fetch PKRU To: Thomas Gleixner References: <20150916174903.E112E464@viggo.jf.intel.com> <20150916174906.4F375766@viggo.jf.intel.com> Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org From: Dave Hansen Message-ID: <5601B893.8050301@sr71.net> Date: Tue, 22 Sep 2015 13:22:43 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/22/2015 01:05 PM, Thomas Gleixner wrote: > On Wed, 16 Sep 2015, Dave Hansen wrote: >> This adds the raw instructions to access PKRU as well as some >> accessor functions that correctly handle when the CPU does >> not support the instruction. We don't use them here, but >> we will use read_pkru() in the next patch. >> >> I do not see an immediate use for write_pkru(). But, we put it >> here for partity with its twin. > > So that read_pkru() doesn't feel so lonely? I can't follow that logic. I was actually using it in a few places, but it fell out of later versions of the patch. I'm happy to kill it.