From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-cys01nam02on0078.outbound.protection.outlook.com ([104.47.37.78] helo=NAM02-CY1-obe.outbound.protection.outlook.com) by bombadil.infradead.org with esmtps (Exim 4.87 #1 (Red Hat Linux)) id 1dG3pL-0004aj-W4 for kexec@lists.infradead.org; Wed, 31 May 2017 13:38:21 +0000 Subject: Re: [PATCH v5 32/32] x86/mm: Add support to make use of Secure Memory Encryption References: <20170418211612.10190.82788.stgit@tlendack-t1.amdoffice.net> <20170418212223.10190.85121.stgit@tlendack-t1.amdoffice.net> <20170519112703.voajtn4t7uy6nwa3@pd.tnic> <7c522f65-c5c8-9362-e1eb-d0765e3ea6c9@amd.com> <20170530145459.tyuy6veqxnrqkhgw@pd.tnic> <115ca39d-6ae7-f603-a415-ead7c4e8193d@amd.com> <20170531084923.mmlpefxfx53f3okp@pd.tnic> From: Tom Lendacky Message-ID: <706d6ae0-bc4c-5ba7-529c-b0fc5e4ad464@amd.com> Date: Wed, 31 May 2017 08:37:50 -0500 MIME-Version: 1.0 In-Reply-To: <20170531084923.mmlpefxfx53f3okp@pd.tnic> Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=infradead.org@lists.infradead.org To: Borislav Petkov Cc: linux-efi@vger.kernel.org, Brijesh Singh , Toshimitsu Kani , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Matt Fleming , x86@kernel.org, linux-mm@kvack.org, Alexander Potapenko , "H. Peter Anvin" , Larry Woodman , linux-arch@vger.kernel.org, kvm@vger.kernel.org, Jonathan Corbet , Joerg Roedel , linux-doc@vger.kernel.org, kasan-dev@googlegroups.com, Ingo Molnar , Andrey Ryabinin , Dave Young , Rik van Riel , Arnd Bergmann , Konrad Rzeszutek Wilk , Andy Lutomirski , Thomas Gleixner , Dmitry Vyukov , kexec@lists.infradead.org, linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, "Michael S. Tsirkin" , Paolo Bonzini On 5/31/2017 3:49 AM, Borislav Petkov wrote: > On Tue, May 30, 2017 at 10:37:03AM -0500, Tom Lendacky wrote: >> I can define the command line option and the "on" and "off" values as >> character buffers in the function and initialize them on a per character >> basis (using a static string causes the same issues as referencing a >> string constant), i.e.: >> >> char cmdline_arg[] = {'m', 'e', 'm', '_', 'e', 'n', 'c', 'r', 'y', 'p', 't', '\0'}; >> char cmdline_off[] = {'o', 'f', 'f', '\0'}; >> char cmdline_on[] = {'o', 'n', '\0'}; >> >> It doesn't look the greatest, but it works and removes the need for the >> rip-relative addressing. > > Well, I'm not thrilled about this one either. It's like being between a > rock and a hard place. :-\ > > On the one hand, we need the encryption mask before we do the fixups and > OTOH we need to do the fixups in order to access the strings properly. > Yuck. > > Well, the only thing I can think of right now is maybe define > "mem_encrypt=" at the end of head_64.S and pass it in from asm to > sme_enable() and then do the "on"/"off" comparsion with local char > buffers. That could make it less ugly... I like keeping the command line option and the values together. It may not look the greatest but I like it more than defining the command line option in head_64.S and passing it in as an argument. OTOH, I don't think the rip-relative addressing was that bad, I can always go back to that... Thanks, Tom > _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec