Skip to contentSkip to conversation

x86/sev: Fix AP Jump Table handling for SNP guests

PATCH Applied Michael Roth 3 participants 8 messages Apr 22, 2022 – Apr 27, 2022 x86

v3 of 4 Applied Latest is v4 →

lore
Share & tools
lore
#0 lore raw

v3 cover x86/sev: Fix AP Jump Table handling for SNP guests

This series is based on tip/master (commit 1912a07f8a)

SNP guests should only retrieve the AP Jump Table address from the secrets page, not via a GHCB request as with SEV-ES guests. This series reworks the handling accordingly, and fixes up some __init annotations for some of the SEV routines touched by that rework.

v3:
- Address missing __init annotations (Boris)

v2:
- add handling for memremap()/ioremap() failures (Boris)
- don't mix function calls with declarations (Boris)

 arch/x86/include/asm/sev.h              | 35 +++++++++++++++++++++++++++++++++++
 arch/x86/kernel/sev.c                   | 80 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--------------------------
 arch/x86/realmode/init.c                |  2 +-
 drivers/virt/coco/sev-guest/sev-guest.h | 35 -----------------------------------
 4 files changed, 90 insertions(+), 62 deletions(-)
#1 lore raw

PATCH v3 1/2 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.

---
 arch/x86/kernel/sev.c    | 6 +++---
 arch/x86/realmode/init.c | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
arch/x86/kernel/sev.c +3 -3
index 2fa87a07ab30..b7fd1915560d 100644
@@ -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;
arch/x86/realmode/init.c +1 -1
index c5e29db02a46..41d7669a97ad 100644
@@ -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))
Signature · 1 line
2.25.1
merge bot Applied
#2 lore raw

[tip: x86/sev] x86/sev: Add missing __init annotations to SEV init routines

The following commit has been merged into the x86/sev branch of tip:

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 <[email protected]>
AuthorDate:    Fri, 22 Apr 2022 08:56:23 -05:00
Committer:     Borislav Petkov <[email protected]>
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.

---
 arch/x86/kernel/sev.c    | 6 +++---
 arch/x86/realmode/init.c | 2 +-
 2 files changed, 4 insertions(+), 4 deletions(-)
arch/x86/kernel/sev.c +3 -3
index 2fa87a0..b7fd191 100644
@@ -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;
arch/x86/realmode/init.c +1 -1
index c5e29db..41d7669 100644
@@ -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))
#3 lore raw

PATCH v3 2/2 x86/sev: Get the AP jump table address from secrets page

In reply to Michael Roth

From: Brijesh Singh <[email protected]>

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a hypervisor must provide the AP jump table physical address through the SNP secrets pages.

Fixes 0afb6b660a6b ("x86/sev: Use SEV-SNP AP creation to start secondary CPUs")
[ mroth: improve error handling when ioremap()/memremap() return NULL ]
[ mroth: don't mix function calls with declarations ]
[ mroth: add missing __init ]
---
 arch/x86/include/asm/sev.h              | 35 ++++++++++++
 arch/x86/kernel/sev.c                   | 76 +++++++++++++++++--------
 drivers/virt/coco/sev-guest/sev-guest.h | 35 ------------
 3 files changed, 87 insertions(+), 59 deletions(-)
arch/x86/include/asm/sev.h +35 -0
index 6e3dda4f82b5..19514524f0f8 100644
@@ -99,6 +99,41 @@ struct sev_guest_platform_data {
 	u64 secrets_gpa;
 };
 
+/*
+ * The secrets page contains 96-bytes of reserved field that can be used by
+ * the guest OS. The guest OS uses the area to save the message sequence
+ * number for each VMPCK.
+ *
+ * See the GHCB spec section Secret page layout for the format for this area.
+ */
+struct secrets_os_area {
+	u32 msg_seqno_0;
+	u32 msg_seqno_1;
+	u32 msg_seqno_2;
+	u32 msg_seqno_3;
+	u64 ap_jump_table_pa;
+	u8 rsvd[40];
+	u8 guest_usage[32];
+} __packed;
+
+#define VMPCK_KEY_LEN		32
+
+/* See the SNP spec version 0.9 for secrets page format */
+struct snp_secrets_page_layout {
+	u32 version;
+	u32 imien	: 1,
+	    rsvd1	: 31;
+	u32 fms;
+	u32 rsvd2;
+	u8 gosvw[16];
+	u8 vmpck0[VMPCK_KEY_LEN];
+	u8 vmpck1[VMPCK_KEY_LEN];
+	u8 vmpck2[VMPCK_KEY_LEN];
+	u8 vmpck3[VMPCK_KEY_LEN];
+	struct secrets_os_area os_area;
+	u8 rsvd3[3840];
+} __packed;
+
 #ifdef CONFIG_AMD_MEM_ENCRYPT
 extern struct static_key_false sev_es_enable_key;
 extern void __sev_es_ist_enter(struct pt_regs *regs);
arch/x86/kernel/sev.c +52 -24

94 lines not on this page · raw message

drivers/virt/coco/sev-guest/sev-guest.h +0 -35
index d39bdd013765..21bda26fdb95 100644
@@ -60,39 +60,4 @@ struct snp_guest_msg {
 	u8 payload[4000];
 } __packed;
 
-/*
- * The secrets page contains 96-bytes of reserved field that can be used by
- * the guest OS. The guest OS uses the area to save the message sequence
- * number for each VMPCK.
- *
- * See the GHCB spec section Secret page layout for the format for this area.
- */
-struct secrets_os_area {
-	u32 msg_seqno_0;
-	u32 msg_seqno_1;
-	u32 msg_seqno_2;
-	u32 msg_seqno_3;
-	u64 ap_jump_table_pa;
-	u8 rsvd[40];
-	u8 guest_usage[32];
-} __packed;
-
-#define VMPCK_KEY_LEN		32
-
-/* See the SNP spec version 0.9 for secrets page format */
-struct snp_secrets_page_layout {
-	u32 version;
-	u32 imien	: 1,
-	    rsvd1	: 31;
-	u32 fms;
-	u32 rsvd2;
-	u8 gosvw[16];
-	u8 vmpck0[VMPCK_KEY_LEN];
-	u8 vmpck1[VMPCK_KEY_LEN];
-	u8 vmpck2[VMPCK_KEY_LEN];
-	u8 vmpck3[VMPCK_KEY_LEN];
-	struct secrets_os_area os_area;
-	u8 rsvd3[3840];
-} __packed;
-
 #endif /* __VIRT_SEVGUEST_H__ */
Signature · 1 line
2.25.1
Reviewed-by on v3 2/2
#4 lore raw

Re: [PATCH v3 2/2] x86/sev: Get the AP jump table address from secrets page

Quoted 4 lines · Michael Roth

From: Brijesh Singh <[email protected]>

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a hypervisor must provide the AP jump table physical address through

I missed this on the first version. It's not the hypervisor, but the guest BIOS that directly provides the AP jump table physical address, in our case OVMF sets the address in the SNP secrets page. This allows communication between UEFI/BIOS and OS without hypervisor involvement.

Quoted 8 lines

the SNP secrets pages.

Fixes 0afb6b660a6b ("x86/sev: Use SEV-SNP AP creation to start secondary CPUs")
[ mroth: improve error handling when ioremap()/memremap() return NULL ]
[ mroth: don't mix function calls with declarations ]
[ mroth: add missing __init ]

With the commit message change:

#5 lore raw

Re: [PATCH v3 2/2] x86/sev: Get the AP jump table address from secrets page

Quoted 10 lines · Tom Lendacky
Quoted 4 lines · Michael Roth

From: Brijesh Singh <[email protected]>

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a hypervisor must provide the AP jump table physical address through

I missed this on the first version. It's not the hypervisor, but the guest BIOS that directly provides the AP jump table physical address, in our case OVMF sets the address in the SNP secrets page. This allows communication between UEFI/BIOS and OS without hypervisor involvement.

How about this wording for the commit message?

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a guest should not rely on the hypervisor to provide the address of the AP jump table. Instead, if a guest BIOS wants provide an AP jump table, it should record the address in the SNP secrets page so the guest operating system can obtain it directly from there.

Fix this on the guest kernel side by having SNP guests use the AP jump table address published in the secrets page rather than issuing a GHCB request to get it.

Quoted 13 lines
Quoted 9 lines

the SNP secrets pages.

Fixes 0afb6b660a6b ("x86/sev: Use SEV-SNP AP creation to start secondary CPUs")
[ mroth: improve error handling when ioremap()/memremap() return NULL ]
[ mroth: don't mix function calls with declarations ]
[ mroth: add missing __init ]

With the commit message change:

#6 lore raw

Re: [PATCH v3 2/2] x86/sev: Get the AP jump table address from secrets page

Quoted 20 lines · Michael Roth
Quoted 10 lines · Tom Lendacky
Quoted 4 lines · Michael Roth

From: Brijesh Singh <[email protected]>

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a hypervisor must provide the AP jump table physical address through

I missed this on the first version. It's not the hypervisor, but the guest BIOS that directly provides the AP jump table physical address, in our case OVMF sets the address in the SNP secrets page. This allows communication between UEFI/BIOS and OS without hypervisor involvement.

How about this wording for the commit message?

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a guest should not rely on the hypervisor to provide the address of the AP jump table. Instead, if a guest BIOS wants provide an AP jump table, it should record the address in the SNP secrets page so the guest operating system can obtain it directly from there.

Quoted 3 lines

Fix this on the guest kernel side by having SNP guests use the AP jump table address published in the secrets page rather than issuing a GHCB request to get it.

That sounds good to me.

Thanks,
Tom

Quoted 14 lines
Quoted 14 lines
Quoted 10 lines

the SNP secrets pages.

Fixes 0afb6b660a6b ("x86/sev: Use SEV-SNP AP creation to start secondary CPUs")
[ mroth: improve error handling when ioremap()/memremap() return NULL ]
[ mroth: don't mix function calls with declarations ]
[ mroth: add missing __init ]

With the commit message change:

merge bot Applied
#7 lore raw

[tip: x86/sev] x86/sev: Get the AP jump table address from secrets page

In reply to Michael Roth
The following commit has been merged into the x86/sev branch of tip:

The following commit has been merged into the x86/sev branch of tip:

Commit-ID:     c2106a231c2ba36ff9af50cdf2867b9a5f8150a6
Gitweb:        https://git.kernel.org/tip/c2106a231c2ba36ff9af50cdf2867b9a5f8150a6
Author:        Brijesh Singh <[email protected]>
AuthorDate:    Fri, 22 Apr 2022 08:56:24 -05:00
Committer:     Borislav Petkov <[email protected]>
CommitterDate: Wed, 27 Apr 2022 13:31:38 +02:00

x86/sev: Get the AP jump table address from secrets page

The GHCB specification section 2.7 states that when SEV-SNP is enabled, a guest should not rely on the hypervisor to provide the address of the AP jump table. Instead, if a guest BIOS wants to provide an AP jump table, it should record the address in the SNP secrets page so the guest operating system can obtain it directly from there.

Fix this on the guest kernel side by having SNP guests use the AP jump table address published in the secrets page rather than issuing a GHCB request to get it.

[ mroth:
- Improve error handling when ioremap()/memremap() return NULL
- Don't mix function calls with declarations
- Add missing __init
- Tweak commit message ]

Fixes 0afb6b660a6b ("x86/sev: Use SEV-SNP AP creation to start secondary CPUs")
---
 arch/x86/include/asm/sev.h              | 35 +++++++++++-
 arch/x86/kernel/sev.c                   | 76 ++++++++++++++++--------
 drivers/virt/coco/sev-guest/sev-guest.h | 35 +-----------
 3 files changed, 87 insertions(+), 59 deletions(-)
arch/x86/include/asm/sev.h +35 -0
index 6e3dda4..1951452 100644
@@ -99,6 +99,41 @@ struct sev_guest_platform_data {
 	u64 secrets_gpa;
 };
 
+/*
+ * The secrets page contains 96-bytes of reserved field that can be used by
+ * the guest OS. The guest OS uses the area to save the message sequence
+ * number for each VMPCK.
+ *
+ * See the GHCB spec section Secret page layout for the format for this area.
+ */
+struct secrets_os_area {
+	u32 msg_seqno_0;
+	u32 msg_seqno_1;
+	u32 msg_seqno_2;
+	u32 msg_seqno_3;
+	u64 ap_jump_table_pa;
+	u8 rsvd[40];
+	u8 guest_usage[32];
+} __packed;
+
+#define VMPCK_KEY_LEN		32
+
+/* See the SNP spec version 0.9 for secrets page format */
+struct snp_secrets_page_layout {
+	u32 version;
+	u32 imien	: 1,
+	    rsvd1	: 31;
+	u32 fms;
+	u32 rsvd2;
+	u8 gosvw[16];
+	u8 vmpck0[VMPCK_KEY_LEN];
+	u8 vmpck1[VMPCK_KEY_LEN];
+	u8 vmpck2[VMPCK_KEY_LEN];
+	u8 vmpck3[VMPCK_KEY_LEN];
+	struct secrets_os_area os_area;
+	u8 rsvd3[3840];
+} __packed;
+
 #ifdef CONFIG_AMD_MEM_ENCRYPT
 extern struct static_key_false sev_es_enable_key;
 extern void __sev_es_ist_enter(struct pt_regs *regs);
arch/x86/kernel/sev.c +52 -24

94 lines not on this page · raw message

drivers/virt/coco/sev-guest/sev-guest.h +0 -35
index d39bdd0..21bda26 100644
@@ -60,39 +60,4 @@ struct snp_guest_msg {
 	u8 payload[4000];
 } __packed;
 
-/*
- * The secrets page contains 96-bytes of reserved field that can be used by
- * the guest OS. The guest OS uses the area to save the message sequence
- * number for each VMPCK.
- *
- * See the GHCB spec section Secret page layout for the format for this area.
- */
-struct secrets_os_area {
-	u32 msg_seqno_0;
-	u32 msg_seqno_1;
-	u32 msg_seqno_2;
-	u32 msg_seqno_3;
-	u64 ap_jump_table_pa;
-	u8 rsvd[40];
-	u8 guest_usage[32];
-} __packed;
-
-#define VMPCK_KEY_LEN		32
-
-/* See the SNP spec version 0.9 for secrets page format */
-struct snp_secrets_page_layout {
-	u32 version;
-	u32 imien	: 1,
-	    rsvd1	: 31;
-	u32 fms;
-	u32 rsvd2;
-	u8 gosvw[16];
-	u8 vmpck0[VMPCK_KEY_LEN];
-	u8 vmpck1[VMPCK_KEY_LEN];
-	u8 vmpck2[VMPCK_KEY_LEN];
-	u8 vmpck3[VMPCK_KEY_LEN];
-	struct secrets_os_area os_area;
-	u8 rsvd3[3840];
-} __packed;
-
 #endif /* __VIRT_SEVGUEST_H__ */