Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp1223442pxb; Tue, 1 Feb 2022 23:03:37 -0800 (PST) X-Google-Smtp-Source: ABdhPJxF5HqXWKpOFNf2eE5M3B67t4tt26+bWasOO7kckE5lCu6uDRXhavPLhRt+neyqEfpObqNO X-Received: by 2002:a63:380f:: with SMTP id f15mr23377519pga.60.1643785417241; Tue, 01 Feb 2022 23:03:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643785417; cv=none; d=google.com; s=arc-20160816; b=wvgDrAZd8+ufKcx+sLmcEAQd23voqvQJqOFpL+e1P8oqe7483gtXmkCycpwkvrFvi6 QDmxIiDs9M7UXT8lXoXeaPEhQzub0h0Wen4OFpxxGCDGHSYbYMsEMTg+3PJanJjIl+jO g+wYVflmIBmXh6NbAXMUoBunkVRnbER/Af5pjIbbQuDfMIg+GHNDZw8XbX/DSk7FD11S s9wheX2SQ3PUNuFvAmlTC956lN0wkoNfM8IKqu+PlqT3s9XYi6RNEsN02oMmCF7Vnn4a WoFo+URC/HKz2rBtfSchSVtJmqEL0TkFYzx+jVzUlH/0Cg28pgjLUVlKeVZ2rOPhvkDV P68w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:subject :from:references:cc:to:content-language:user-agent:mime-version:date :message-id:dkim-signature; bh=Nw5mpcGvZTrvRfZvDUQufjd36JMM7y1U9fVOzfNPR+A=; b=j/9GqkEBBOdLhBvBLGAMAAsMht3EkXWDxcKC3ewCKzh5Z6TkvweuCvCeGQGHF3c+b4 aMlQ8R5Sz+mQSlwCDQxzRJeABmh4Ummp4Xfoyp9r+ExCp8L9/zM11qrHxH7szfCjqToJ eFnF8E+30WeJTRvMFugzFZLdrje1qqMk0u2ZPh7ppoVf9Ah3dvv5McvhvggncpV4VZNW 6q6R34ogSY4hN97vXwHNKUZPkukjjtbPUfAUShqwg5JV47VvF72EURGWNAaRrnWeKHAC jmNuFhLt054I/hYUxusXdyjp6juFMQ5UJ7LOe5dsYnbjv1aOv04Ib2+GOuwE5usG95cz /3wg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=S0Fma3YH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id d15si18914424pgk.641.2022.02.01.23.03.24; Tue, 01 Feb 2022 23:03:37 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=S0Fma3YH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241595AbiBARka (ORCPT + 99 others); Tue, 1 Feb 2022 12:40:30 -0500 Received: from mga02.intel.com ([134.134.136.20]:11335 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241596AbiBARkX (ORCPT ); Tue, 1 Feb 2022 12:40:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643737224; x=1675273224; h=message-id:date:mime-version:to:cc:references:from: subject:in-reply-to:content-transfer-encoding; bh=w8HMLRlvFY4B4RAgkNDRGRRjjPKUPof7Fu2+mcJLrrs=; b=S0Fma3YH2Vn64uO76yjzMn5aQT/EYA+ostS20wnq4Bcu6ptkKI/wryzB RuVeM29V1P6ntnJiCFKiatesom8UKinwfw0u9XqI7FsDbTpS2KuEk3ST9 wr164hStx9v7+RU4Z4sxt3U22ehfJoUShMK4vfK74ChGHUSP6PM16gOuN MDlNlRxHgnP8X2B8TQYXWZN3db8KW31q+Gidpu1N99b5Y6E2Lfms0feOc JmWmMO2p6yNHmDW84Gln+x730RIZlQjRsCvokjBtkvEYpHvNRQGJK3o/l wbzeFUbx4wguCrJTOFJ5NwkZnVEWSD4CIK/YUdlWRtTpcmTXais7ZGc1M Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10245"; a="235142146" X-IronPort-AV: E=Sophos;i="5.88,334,1635231600"; d="scan'208";a="235142146" Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2022 09:40:09 -0800 X-IronPort-AV: E=Sophos;i="5.88,334,1635231600"; d="scan'208";a="583109790" Received: from kssimha-mobl1.amr.corp.intel.com (HELO [10.212.228.15]) ([10.212.228.15]) by fmsmga008-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2022 09:40:09 -0800 Message-ID: <87f171f1-c44b-5103-f9e5-20a6b5c257dd@intel.com> Date: Tue, 1 Feb 2022 09:40:06 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: ira.weiny@intel.com, Dave Hansen , "H. Peter Anvin" , Dan Williams Cc: Fenghua Yu , Rick Edgecombe , linux-kernel@vger.kernel.org References: <20220127175505.851391-1-ira.weiny@intel.com> <20220127175505.851391-17-ira.weiny@intel.com> From: Dave Hansen Subject: Re: [PATCH V8 16/44] mm/pkeys: Introduce pks_mk_readwrite() In-Reply-To: <20220127175505.851391-17-ira.weiny@intel.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/27/22 09:54, ira.weiny@intel.com wrote: > +static inline void pks_mk_readwrite(int pkey) > +{ > + pks_update_protection(pkey, PKEY_READ_WRITE); > +} I don't really like the "mk" terminology in here. Maybe it's from dealing with the PTE helpers, but "mk" to me means that it won't do anything observable by itself. We're also not starved for space here, and it's really odd to abbreviate "make->mk" but not do "readwrite->rw". This really is going off and changing a register value. I think: pks_set_readwrite() would be fine. This starts to get a bit redundant, but looks fine too: pks_set_key_readwrite()