From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Date: Fri, 14 Jun 2019 11:56:47 +0000 Subject: Re: [PATCH, RFC 49/62] mm, x86: export several MKTME variables Message-Id: <20190614115647.GI3436@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit List-Id: References: <20190508144422.13171-1-kirill.shutemov@linux.intel.com> <20190508144422.13171-50-kirill.shutemov@linux.intel.com> In-Reply-To: <20190508144422.13171-50-kirill.shutemov@linux.intel.com> To: "Kirill A. Shutemov" Cc: Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Borislav Petkov , Andy Lutomirski , David Howells , Kees Cook , Dave Hansen , Kai Huang , Jacob Pan , Alison Schofield , linux-mm@kvack.org, kvm@vger.kernel.org, keyrings@vger.kernel.org, linux-kernel@vger.kernel.org On Wed, May 08, 2019 at 05:44:09PM +0300, Kirill A. Shutemov wrote: > From: Kai Huang > > KVM needs those variables to get/set memory encryption mask. > > Signed-off-by: Kai Huang > Signed-off-by: Kirill A. Shutemov > --- > arch/x86/mm/mktme.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/arch/x86/mm/mktme.c b/arch/x86/mm/mktme.c > index df70651816a1..12f4266cf7ea 100644 > --- a/arch/x86/mm/mktme.c > +++ b/arch/x86/mm/mktme.c > @@ -7,13 +7,16 @@ > > /* Mask to extract KeyID from physical address. */ > phys_addr_t mktme_keyid_mask; > +EXPORT_SYMBOL_GPL(mktme_keyid_mask); > /* > * Number of KeyIDs available for MKTME. > * Excludes KeyID-0 which used by TME. MKTME KeyIDs start from 1. > */ > int mktme_nr_keyids; > +EXPORT_SYMBOL_GPL(mktme_nr_keyids); > /* Shift of KeyID within physical address. */ > int mktme_keyid_shift; > +EXPORT_SYMBOL_GPL(mktme_keyid_shift); > > DEFINE_STATIC_KEY_FALSE(mktme_enabled_key); > EXPORT_SYMBOL_GPL(mktme_enabled_key); NAK, don't export variables. Who owns the values, who enforces this?