From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751114AbdEaJwB (ORCPT ); Wed, 31 May 2017 05:52:01 -0400 Received: from mail.skyhub.de ([5.9.137.197]:44058 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751104AbdEaJv5 (ORCPT ); Wed, 31 May 2017 05:51:57 -0400 Date: Wed, 31 May 2017 11:51:48 +0200 From: Borislav Petkov To: Tom Lendacky Cc: linux-arch@vger.kernel.org, linux-efi@vger.kernel.org, kvm@vger.kernel.org, linux-doc@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com, linux-mm@kvack.org, iommu@lists.linux-foundation.org, Rik van Riel , Radim =?utf-8?B?S3LEjW3DocWZ?= , Toshimitsu Kani , Arnd Bergmann , Jonathan Corbet , Matt Fleming , "Michael S. Tsirkin" , Joerg Roedel , Konrad Rzeszutek Wilk , Paolo Bonzini , Larry Woodman , Brijesh Singh , Ingo Molnar , Andy Lutomirski , "H. Peter Anvin" , Andrey Ryabinin , Alexander Potapenko , Dave Young , Thomas Gleixner , Dmitry Vyukov Subject: Re: [PATCH v5 29/32] x86/mm: Add support to encrypt the kernel in-place Message-ID: <20170531095148.pba6ju6im4qxbwfg@pd.tnic> References: <20170418211612.10190.82788.stgit@tlendack-t1.amdoffice.net> <20170418212149.10190.70894.stgit@tlendack-t1.amdoffice.net> <20170518124626.hqyqqbjpy7hmlpqc@pd.tnic> <7e2ae014-525c-76f2-9fce-2124596db2d2@amd.com> <20170526162522.p7prrqqalx2ivfxl@pd.tnic> <33c075b1-71f6-b5d0-b1fa-d742d0659d38@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <33c075b1-71f6-b5d0-b1fa-d742d0659d38@amd.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 30, 2017 at 11:39:07AM -0500, Tom Lendacky wrote: > Yes, it's from objtool: > > arch/x86/mm/mem_encrypt_boot.o: warning: objtool: .text+0xd2: return > instruction outside of a callable function Oh, well, let's make it a global symbol then. Who knows, we might have to live-patch it someday :-) --- diff --git a/arch/x86/mm/mem_encrypt_boot.S b/arch/x86/mm/mem_encrypt_boot.S index fb58f9f953e3..7720b0050840 100644 --- a/arch/x86/mm/mem_encrypt_boot.S +++ b/arch/x86/mm/mem_encrypt_boot.S @@ -47,9 +47,9 @@ ENTRY(sme_encrypt_execute) movq %rdx, %r12 /* Kernel length */ /* Copy encryption routine into the workarea */ - movq %rax, %rdi /* Workarea encryption routine */ - leaq .Lenc_start(%rip), %rsi /* Encryption routine */ - movq $(.Lenc_stop - .Lenc_start), %rcx /* Encryption routine length */ + movq %rax, %rdi /* Workarea encryption routine */ + leaq __enc_copy(%rip), %rsi /* Encryption routine */ + movq $(.L__enc_copy_end - __enc_copy), %rcx /* Encryption routine length */ rep movsb /* Setup registers for call */ @@ -70,8 +70,7 @@ ENTRY(sme_encrypt_execute) ret ENDPROC(sme_encrypt_execute) -.Lenc_start: -ENTRY(sme_enc_routine) +ENTRY(__enc_copy) /* * Routine used to encrypt kernel. * This routine must be run outside of the kernel proper since @@ -147,5 +146,5 @@ ENTRY(sme_enc_routine) wrmsr ret -ENDPROC(sme_enc_routine) -.Lenc_stop: +.L__enc_copy_end: +ENDPROC(__enc_copy) -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.