From: "tip-bot2 for Michael Roth" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Borislav Petkov <bp@suse.de>, Michael Roth <michael.roth@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/sev] x86/sev: Add missing __init annotations to SEV init routines
Date: Wed, 27 Apr 2022 11:56:23 -0000 [thread overview]
Message-ID: <165106058382.4207.3592489487323661828.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220422135624.114172-2-michael.roth@amd.com>
The following commit has been merged into the x86/sev branch of tip:
Commit-ID: 75d359ec4141b013727022a663762931f69e6510
Gitweb: https://git.kernel.org/tip/75d359ec4141b013727022a663762931f69e6510
Author: Michael Roth <michael.roth@amd.com>
AuthorDate: Fri, 22 Apr 2022 08:56:23 -05:00
Committer: Borislav Petkov <bp@suse.de>
CommitterDate: Wed, 27 Apr 2022 13:31:36 +02:00
x86/sev: Add missing __init annotations to SEV init routines
Currently, get_secrets_page() is only reachable from the following call
chain:
__init snp_init_platform_device():
get_secrets_page()
so mark it as __init as well. This is also needed since it calls
early_memremap(), which is also an __init routine.
Similarly, get_jump_table_addr() is only reachable from the following
call chain:
__init setup_real_mode():
sme_sev_setup_real_mode():
sev_es_setup_ap_jump_table():
get_jump_table_addr()
so mark get_jump_table_addr() and everything up that call chain as
__init as well. This is also needed since future patches will add a
call to get_secrets_page(), which needs to be __init due to the reasons
stated above.
Suggested-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Michael Roth <michael.roth@amd.com>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lore.kernel.org/r/20220422135624.114172-2-michael.roth@amd.com
---
arch/x86/kernel/sev.c | 6 +++---
arch/x86/realmode/init.c | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/sev.c b/arch/x86/kernel/sev.c
index 2fa87a0..b7fd191 100644
--- a/arch/x86/kernel/sev.c
+++ b/arch/x86/kernel/sev.c
@@ -558,7 +558,7 @@ void noinstr __sev_es_nmi_complete(void)
__sev_put_ghcb(&state);
}
-static u64 get_jump_table_addr(void)
+static u64 __init get_jump_table_addr(void)
{
struct ghcb_state state;
unsigned long flags;
@@ -1077,7 +1077,7 @@ void snp_set_wakeup_secondary_cpu(void)
apic->wakeup_secondary_cpu = wakeup_cpu_via_vmgexit;
}
-int sev_es_setup_ap_jump_table(struct real_mode_header *rmh)
+int __init sev_es_setup_ap_jump_table(struct real_mode_header *rmh)
{
u16 startup_cs, startup_ip;
phys_addr_t jump_table_pa;
@@ -2171,7 +2171,7 @@ static struct platform_device sev_guest_device = {
.id = -1,
};
-static u64 get_secrets_page(void)
+static u64 __init get_secrets_page(void)
{
u64 pa_data = boot_params.cc_blob_address;
struct cc_blob_sev_info info;
diff --git a/arch/x86/realmode/init.c b/arch/x86/realmode/init.c
index c5e29db..41d7669 100644
--- a/arch/x86/realmode/init.c
+++ b/arch/x86/realmode/init.c
@@ -67,7 +67,7 @@ void __init reserve_real_mode(void)
memblock_reserve(0, SZ_1M);
}
-static void sme_sev_setup_real_mode(struct trampoline_header *th)
+static void __init sme_sev_setup_real_mode(struct trampoline_header *th)
{
#ifdef CONFIG_AMD_MEM_ENCRYPT
if (cc_platform_has(CC_ATTR_HOST_MEM_ENCRYPT))
next prev parent reply other threads:[~2022-04-27 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:56 [PATCH v3 0/2] x86/sev: Fix AP Jump Table handling for SNP guests Michael Roth
2022-04-22 13:56 ` [PATCH v3 1/2] x86/sev: Add missing __init annotations to SEV init routines Michael Roth
2022-04-27 11:56 ` tip-bot2 for Michael Roth [this message]
2022-04-22 13:56 ` [PATCH v3 2/2] x86/sev: Get the AP jump table address from secrets page Michael Roth
2022-04-22 15:15 ` Tom Lendacky
2022-04-22 15:40 ` Michael Roth
2022-04-22 17:27 ` Tom Lendacky
2022-04-27 11:56 ` [tip: x86/sev] " tip-bot2 for Brijesh Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=165106058382.4207.3592489487323661828.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®