Add Secure TSC support for SNP guests
v11 cover Add Secure TSC support for SNP guests
This patchset is also available at:
https://github.com/AMDESE/linux-kvm/tree/sectsc-guest-latest
and is based on v6.11-rc1
Overview
--------
Secure TSC allows guests to securely use RDTSC/RDTSCP instructions as the parameters being used cannot be changed by hypervisor once the guest is launched. More details in the AMD64 APM Vol 2, Section "Secure TSC".
In order to enable secure TSC, SEV-SNP guests need to send TSC_INFO guest message before the APs are booted. Details from the TSC_INFO response will then be used to program the VMSA before the APs are brought up. See "SEV Secure Nested Paging Firmware ABI Specification" document (currently at
https://www.amd.com/system/files/TechDocs/56860.pdf) section "TSC Info"
SEV-guest driver has the implementation for guest and AMD Security Processor communication. As the TSC_INFO needs to be initialized during early boot before APs are started, move the guest messaging code from sev-guest driver to sev/core.c and provide well defined APIs to the sev-guest driver.
Patches:
01-04: sev-guest driver cleanup and enhancements
05: Use AES GCM library
06-07: SNP init error handling and cache secrets page address 08-10: Preparatory patches for code movement
11-12: Patches moving SNP guest messaging code from SEV guest driver to
SEV common code
13-20: SecureTSC enablement patches.
Testing SecureTSC
-----------------
SecureTSC hypervisor patches based on top of SEV-SNP Guest MEMFD series:
https://github.com/AMDESE/linux-kvm/tree/sectsc-host-latest
QEMU changes:
https://github.com/nikunjad/qemu/tree/snp-securetsc-latest
QEMU commandline SEV-SNP with SecureTSC:
qemu-system-x86_64 -cpu EPYC-Milan-v2 -smp 4 \
-object memory-backend-memfd,id=ram1,size=1G,share=true,prealloc=false,reserve=false \
-object sev-snp-guest,id=sev0,cbitpos=51,reduced-phys-bits=1,secure-tsc=on \
-machine q35,confidential-guest-support=sev0,memory-backend=ram1 \
...Changelog:
----------
v11:
* Rebased on top of v6.11-rc1
* Added Acked-by/Reviewed-by
* Moved SEV Guest driver cleanups in the beginning of the series
* Commit message updates
* Enforced PAGE_SIZE constraints for snp_guest_msg
* After offline discussion with Boris, redesigned and exported SEV guest messaging APIs to sev-guest driver
* Dropped VMPCK rework patches
* Make sure movement of SEV core routines does not break the SEV Guest driver midway of the series.
v10: https://lore.kernel.org/lkml/[email protected]/
* Rebased on top of tip/x86/sev
* Added Reviewed-by from Tom
* Commit message updates
* Change the condition for better readability in get_vmpck()
* Make vmpck_id as u32 again and use VMPCK_MAX_NUM as the default value
Nikunj A Dadhania (20):
virt: sev-guest: Replace dev_dbg with pr_debug
virt: sev-guest: Rename local guest message variables
virt: sev-guest: Fix user-visible strings
virt: sev-guest: Ensure the SNP guest messages do not exceed a page
virt: sev-guest: Use AES GCM crypto library
x86/sev: Handle failures from snp_init()
x86/sev: Cache the secrets page address
virt: sev-guest: Consolidate SNP guest messaging parameters to a
struct
virt: sev-guest: Reduce the scope of SNP command mutex
virt: sev-guest: Carve out SNP message context structure x86/sev: Carve out and export SNP guest messaging init routines x86/sev: Relocate SNP guest messaging routines to common code x86/cc: Add CC_ATTR_GUEST_SECURE_TSC
x86/sev: Add Secure TSC support for SNP guests
x86/sev: Change TSC MSR behavior for Secure TSC enabled guests x86/sev: Prevent RDTSC/RDTSCP interception for Secure TSC enabled
guests
x86/sev: Allow Secure TSC feature for SNP guests x86/sev: Mark Secure TSC as reliable clocksource x86/kvmclock: Skip kvmclock when Secure TSC is available x86/cpu/amd: Do not print FW_BUG for Secure TSC
arch/x86/include/asm/sev-common.h | 1 + arch/x86/include/asm/sev.h | 166 +++++- arch/x86/include/asm/svm.h | 6 +- include/linux/cc_platform.h | 8 + arch/x86/boot/compressed/sev.c | 3 +- arch/x86/coco/core.c | 3 + arch/x86/coco/sev/core.c | 590 ++++++++++++++++++-- arch/x86/coco/sev/shared.c | 10 + arch/x86/kernel/cpu/amd.c | 3 +- arch/x86/kernel/kvmclock.c | 2 +- arch/x86/mm/mem_encrypt.c | 4 + arch/x86/mm/mem_encrypt_amd.c | 4 + arch/x86/mm/mem_encrypt_identity.c | 7 + drivers/virt/coco/sev-guest/sev-guest.c | 695 +++--------------------- arch/x86/Kconfig | 1 + drivers/virt/coco/sev-guest/Kconfig | 3 - 16 files changed, 820 insertions(+), 686 deletions(-)
base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
Signature · 1 line
2.34.1
PATCH v11 1/20 virt: sev-guest: Replace dev_dbg with pr_debug
In preparation of moving code to arch/x86/coco/sev/core.c, replace dev_dbg with pr_debug.
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +5 -4
@@ -296,8 +296,9 @@ static int verify_and_dec_payload(struct snp_guest_dev *snp_dev, void *payload,struct snp_guest_msg_hdr *req_hdr = &req->hdr;struct snp_guest_msg_hdr *resp_hdr = &resp->hdr; -dev_dbg (snp_dev->dev,"response [seqno %lld type %d version %d sz %d]\n" , - resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, resp_hdr->msg_sz); +pr_debug ("response [seqno %lld type %d version %d sz %d]\n" , + resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, + resp_hdr->msg_sz);/* Copy response from shared memory to encrypted memory. */ memcpy (resp, snp_dev->response,sizeof (*resp));
@@ -343,8 +344,8 @@ static int enc_payload(struct snp_guest_dev *snp_dev, u64 seqno, int version, u8if (!hdr->msg_seqno)return -ENOSR ; -dev_dbg (snp_dev->dev,"request [seqno %lld type %d version %d sz %d]\n" , - hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz); +pr_debug ("request [seqno %lld type %d version %d sz %d]\n" , + hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz);return __enc_payload (snp_dev, req, payload, sz); }
Signature · 1 line
2.34.1
[tip: x86/sev] virt: sev-guest: Replace dev_dbg() with pr_debug()
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: dc6d20b900b72bea89ebd8154ba9bde1029f330b Gitweb: https://git.kernel.org/tip/dc6d20b900b72bea89ebd8154ba9bde1029f330b Author: Nikunj A Dadhania <[email protected]> AuthorDate: Wed, 31 Jul 2024 20:37:52 +05:30 Committer: Borislav Petkov (AMD) <[email protected]> CommitterDate: Tue, 27 Aug 2024 10:22:20 +02:00
virt: sev-guest: Replace dev_dbg() with pr_debug()
In preparation for moving code to arch/x86/coco/sev/core.c, replace dev_dbg with pr_debug.
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +5 -4
@@ -296,8 +296,9 @@ static int verify_and_dec_payload(struct snp_guest_dev *snp_dev, void *payload,struct snp_guest_msg_hdr *req_hdr = &req->hdr;struct snp_guest_msg_hdr *resp_hdr = &resp->hdr; -dev_dbg (snp_dev->dev,"response [seqno %lld type %d version %d sz %d]\n" , - resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, resp_hdr->msg_sz); +pr_debug ("response [seqno %lld type %d version %d sz %d]\n" , + resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, + resp_hdr->msg_sz);/* Copy response from shared memory to encrypted memory. */ memcpy (resp, snp_dev->response,sizeof (*resp));
@@ -343,8 +344,8 @@ static int enc_payload(struct snp_guest_dev *snp_dev, u64 seqno, int version, u8if (!hdr->msg_seqno)return -ENOSR ; -dev_dbg (snp_dev->dev,"request [seqno %lld type %d version %d sz %d]\n" , - hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz); +pr_debug ("request [seqno %lld type %d version %d sz %d]\n" , + hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz);return __enc_payload (snp_dev, req, payload, sz); }
PATCH v11 2/20 virt: sev-guest: Rename local guest message variables
In reply to Nikunj A DadhaniaRename local guest message variables for more clarity
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 117 ++++++++++++------------ 1 file changed, 59 insertions(+), 58 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +59 -58
@@ -291,45 +291,45 @@ static int dec_payload(struct snp_guest_dev *snp_dev, struct snp_guest_msg *msg,static int verify_and_dec_payload (struct snp_guest_dev *snp_dev,void *payload,u32 sz) {struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_guest_msg *resp = &snp_dev->secret_response; -struct snp_guest_msg *req = &snp_dev->secret_request; -struct snp_guest_msg_hdr *req_hdr = &req->hdr; -struct snp_guest_msg_hdr *resp_hdr = &resp->hdr; +struct snp_guest_msg *resp_msg = &snp_dev->secret_response; +struct snp_guest_msg *req_msg = &snp_dev->secret_request; +struct snp_guest_msg_hdr *req_msg_hdr = &req_msg->hdr; +struct snp_guest_msg_hdr *resp_msg_hdr = &resp_msg->hdr;pr_debug ("response [seqno %lld type %d version %d sz %d]\n" , - resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, - resp_hdr->msg_sz); + resp_msg_hdr->msg_seqno, resp_msg_hdr->msg_type, resp_msg_hdr->msg_version, + resp_msg_hdr->msg_sz);/* Copy response from shared memory to encrypted memory. */ -memcpy (resp, snp_dev->response,sizeof (*resp)); +memcpy (resp_msg, snp_dev->response,sizeof (*resp_msg));/* Verify that the sequence counter is incremented by 1 */ -if (unlikely (resp_hdr->msg_seqno != (req_hdr->msg_seqno +1 ))) +if (unlikely (resp_msg_hdr->msg_seqno != (req_msg_hdr->msg_seqno +1 )))return -EBADMSG ;/* Verify response message type and version number. */ -if (resp_hdr->msg_type != (req_hdr->msg_type +1 ) || - resp_hdr->msg_version != req_hdr->msg_version) +if (resp_msg_hdr->msg_type != (req_msg_hdr->msg_type +1 ) || + resp_msg_hdr->msg_version != req_msg_hdr->msg_version)return -EBADMSG ;/* * If the message size is greater than our buffer length then return * an error. */ -if (unlikely ((resp_hdr->msg_sz + crypto->a_len) > sz)) +if (unlikely ((resp_msg_hdr->msg_sz + crypto->a_len) > sz))return -EBADMSG ;/* Decrypt the payload */ -return dec_payload (snp_dev, resp, payload, resp_hdr->msg_sz + crypto->a_len); +return dec_payload (snp_dev, resp_msg, payload, resp_msg_hdr->msg_sz + crypto->a_len); }static int enc_payload (struct snp_guest_dev *snp_dev,u64 seqno,int version,u8 type,void *payload,size_t sz) { -struct snp_guest_msg *req = &snp_dev->secret_request; -struct snp_guest_msg_hdr *hdr = &req->hdr; +struct snp_guest_msg *msg = &snp_dev->secret_request; +struct snp_guest_msg_hdr *hdr = &msg->hdr; -memset (req,0 ,sizeof (*req)); +memset (msg,0 ,sizeof (*msg)); hdr->algo =SNP_AEAD_AES_256_GCM ; hdr->hdr_version =MSG_HDR_VER ;
@@ -347,7 +347,7 @@ static int enc_payload(struct snp_guest_dev *snp_dev, u64 seqno, int version, u8pr_debug ("request [seqno %lld type %d version %d sz %d]\n" , hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz); -return __enc_payload (snp_dev, req, payload, sz); +return __enc_payload (snp_dev, msg, payload, sz); } static int __handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code,
@@ -496,8 +496,8 @@ struct snp_req_resp {static int get_report (struct snp_guest_dev *snp_dev,struct snp_guest_request_ioctl *arg) {struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_report_req *req = &snp_dev->req.report; -struct snp_report_resp *resp; +struct snp_report_req *report_req = &snp_dev->req.report; +struct snp_report_resp *report_resp;int rc, resp_len;lockdep_assert_held (&snp_cmd_mutex);
@@ -505,7 +505,7 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_ioif (!arg->req_data || !arg->resp_data)return -EINVAL ; -if (copy_from_user (req, (void __user *)arg->req_data,sizeof (*req))) +if (copy_from_user (report_req, (void __user *)arg->req_data,sizeof (*report_req)))return -EFAULT ;/*
@@ -513,30 +513,29 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_io* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp->data) + crypto->a_len; - resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); -if (!resp) + resp_len =sizeof (report_resp->data) + crypto->a_len; + report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); +if (!report_resp)return -ENOMEM ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg, -SNP_MSG_REPORT_REQ , req,sizeof (*req), resp->data, - resp_len); + rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + report_req,sizeof (*report_req), report_resp->data, resp_len);if (rc) goto e_free; -if (copy_to_user ((void __user *)arg->resp_data, resp,sizeof (*resp))) +if (copy_to_user ((void __user *)arg->resp_data, report_resp,sizeof (*report_resp))) rc = -EFAULT ; e_free: -kfree (resp); +kfree (report_resp);return rc; }static int get_derived_key (struct snp_guest_dev *snp_dev,struct snp_guest_request_ioctl *arg) { -struct snp_derived_key_req *req = &snp_dev->req.derived_key; +struct snp_derived_key_req *derived_key_req = &snp_dev->req.derived_key;struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_derived_key_resp resp = {0 }; +struct snp_derived_key_resp derived_key_resp = {0 };int rc, resp_len;/* Response data is 64 bytes and max authsize for GCM is 16 bytes. */ u8 buf[64 +16 ];
@@ -551,25 +550,27 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp.data) + crypto->a_len; + resp_len =sizeof (derived_key_resp.data) + crypto->a_len;if (sizeof (buf) < resp_len)return -ENOMEM ; -if (copy_from_user (req, (void __user *)arg->req_data,sizeof (*req))) +if (copy_from_user (derived_key_req, (void __user *)arg->req_data, +sizeof (*derived_key_req)))return -EFAULT ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg, -SNP_MSG_KEY_REQ , req,sizeof (*req), buf, resp_len); + rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_KEY_REQ , + derived_key_req,sizeof (*derived_key_req), buf, resp_len);if (rc)return rc; -memcpy (resp.data, buf,sizeof (resp.data)); -if (copy_to_user ((void __user *)arg->resp_data, &resp,sizeof (resp))) +memcpy (derived_key_resp.data, buf,sizeof (derived_key_resp.data)); +if (copy_to_user ((void __user *)arg->resp_data, &derived_key_resp, +sizeof (derived_key_resp))) rc = -EFAULT ;/* The response buffer contains the sensitive data, explicitly clear it. */ memzero_explicit (buf,sizeof (buf)); -memzero_explicit (&resp,sizeof (resp)); +memzero_explicit (&derived_key_resp,sizeof (derived_key_resp));return rc; }
@@ -577,9 +578,9 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques struct snp_req_resp *io) { -struct snp_ext_report_req *req = &snp_dev->req.ext_report; +struct snp_ext_report_req *report_req = &snp_dev->req.ext_report;struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_report_resp *resp; +struct snp_report_resp *report_resp;int ret, npages =0 , resp_len;sockptr_t certs_address;
@@ -588,22 +589,22 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesif (sockptr_is_null (io->req_data) ||sockptr_is_null (io->resp_data))return -EINVAL ; -if (copy_from_sockptr (req, io->req_data,sizeof (*req))) +if (copy_from_sockptr (report_req, io->req_data,sizeof (*report_req)))return -EFAULT ;/* caller does not want certificate data */ -if (!req->certs_len || !req->certs_address) +if (!report_req->certs_len || !report_req->certs_address) goto cmd; -if (req->certs_len >SEV_FW_BLOB_MAX_SIZE || - !IS_ALIGNED (req->certs_len,PAGE_SIZE )) +if (report_req->certs_len >SEV_FW_BLOB_MAX_SIZE || + !IS_ALIGNED (report_req->certs_len,PAGE_SIZE ))return -EINVAL ;if (sockptr_is_kernel (io->resp_data)) { - certs_address =KERNEL_SOCKPTR ((void *)req->certs_address); + certs_address =KERNEL_SOCKPTR ((void *)report_req->certs_address); }else { - certs_address =USER_SOCKPTR ((void __user *)req->certs_address); -if (!access_ok (certs_address.user, req->certs_len)) + certs_address =USER_SOCKPTR ((void __user *)report_req->certs_address); +if (!access_ok (certs_address.user, report_req->certs_len))return -EFAULT ; }
@@ -613,45 +614,45 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques* the host. If host does not supply any certs in it, then copy * zeros to indicate that certificate data was not provided. */ -memset (snp_dev->certs_data,0 , req->certs_len); - npages = req->certs_len >>PAGE_SHIFT ; +memset (snp_dev->certs_data,0 , report_req->certs_len); + npages = report_req->certs_len >>PAGE_SHIFT ; cmd:/* * The intermediate response buffer is used while decrypting the * response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp->data) + crypto->a_len; - resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); -if (!resp) + resp_len =sizeof (report_resp->data) + crypto->a_len; + report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); +if (!report_resp)return -ENOMEM ; snp_dev->input.data_npages = npages; - ret =handle_guest_request (snp_dev,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg, -SNP_MSG_REPORT_REQ , &req->data, -sizeof (req->data), resp->data, resp_len); + ret =handle_guest_request (snp_dev,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + &report_req->data,sizeof (report_req->data), + report_resp->data, resp_len);/* If certs length is invalid then copy the returned length */ if (arg->vmm_error ==SNP_GUEST_VMM_ERR_INVALID_LEN ) { - req->certs_len = snp_dev->input.data_npages <<PAGE_SHIFT ; + report_req->certs_len = snp_dev->input.data_npages <<PAGE_SHIFT ; -if (copy_to_sockptr (io->req_data, req,sizeof (*req))) +if (copy_to_sockptr (io->req_data, report_req,sizeof (*report_req))) ret = -EFAULT ; }if (ret) goto e_free; -if (npages &©_to_sockptr (certs_address, snp_dev->certs_data, req->certs_len)) { +if (npages &©_to_sockptr (certs_address, snp_dev->certs_data, report_req->certs_len)) { ret = -EFAULT ; goto e_free; } -if (copy_to_sockptr (io->resp_data, resp,sizeof (*resp))) +if (copy_to_sockptr (io->resp_data, report_resp,sizeof (*report_resp))) ret = -EFAULT ; e_free: -kfree (resp); +kfree (report_resp);return ret; }
Signature · 1 line
2.34.1
[tip: x86/sev] virt: sev-guest: Rename local guest message variables
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: a1bbb2236bb97c0afee4cdf8fd732ff5f9cd60ac Gitweb: https://git.kernel.org/tip/a1bbb2236bb97c0afee4cdf8fd732ff5f9cd60ac Author: Nikunj A Dadhania <[email protected]> AuthorDate: Wed, 31 Jul 2024 20:37:53 +05:30 Committer: Borislav Petkov (AMD) <[email protected]> CommitterDate: Tue, 27 Aug 2024 10:34:41 +02:00
virt: sev-guest: Rename local guest message variables
Rename local guest message variables for more clarity.
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 117 +++++++++++------------ 1 file changed, 59 insertions(+), 58 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +59 -58
@@ -291,45 +291,45 @@ static int dec_payload(struct snp_guest_dev *snp_dev, struct snp_guest_msg *msg,static int verify_and_dec_payload (struct snp_guest_dev *snp_dev,void *payload,u32 sz) {struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_guest_msg *resp = &snp_dev->secret_response; -struct snp_guest_msg *req = &snp_dev->secret_request; -struct snp_guest_msg_hdr *req_hdr = &req->hdr; -struct snp_guest_msg_hdr *resp_hdr = &resp->hdr; +struct snp_guest_msg *resp_msg = &snp_dev->secret_response; +struct snp_guest_msg *req_msg = &snp_dev->secret_request; +struct snp_guest_msg_hdr *req_msg_hdr = &req_msg->hdr; +struct snp_guest_msg_hdr *resp_msg_hdr = &resp_msg->hdr;pr_debug ("response [seqno %lld type %d version %d sz %d]\n" , - resp_hdr->msg_seqno, resp_hdr->msg_type, resp_hdr->msg_version, - resp_hdr->msg_sz); + resp_msg_hdr->msg_seqno, resp_msg_hdr->msg_type, resp_msg_hdr->msg_version, + resp_msg_hdr->msg_sz);/* Copy response from shared memory to encrypted memory. */ -memcpy (resp, snp_dev->response,sizeof (*resp)); +memcpy (resp_msg, snp_dev->response,sizeof (*resp_msg));/* Verify that the sequence counter is incremented by 1 */ -if (unlikely (resp_hdr->msg_seqno != (req_hdr->msg_seqno +1 ))) +if (unlikely (resp_msg_hdr->msg_seqno != (req_msg_hdr->msg_seqno +1 )))return -EBADMSG ;/* Verify response message type and version number. */ -if (resp_hdr->msg_type != (req_hdr->msg_type +1 ) || - resp_hdr->msg_version != req_hdr->msg_version) +if (resp_msg_hdr->msg_type != (req_msg_hdr->msg_type +1 ) || + resp_msg_hdr->msg_version != req_msg_hdr->msg_version)return -EBADMSG ;/* * If the message size is greater than our buffer length then return * an error. */ -if (unlikely ((resp_hdr->msg_sz + crypto->a_len) > sz)) +if (unlikely ((resp_msg_hdr->msg_sz + crypto->a_len) > sz))return -EBADMSG ;/* Decrypt the payload */ -return dec_payload (snp_dev, resp, payload, resp_hdr->msg_sz + crypto->a_len); +return dec_payload (snp_dev, resp_msg, payload, resp_msg_hdr->msg_sz + crypto->a_len); }static int enc_payload (struct snp_guest_dev *snp_dev,u64 seqno,int version,u8 type,void *payload,size_t sz) { -struct snp_guest_msg *req = &snp_dev->secret_request; -struct snp_guest_msg_hdr *hdr = &req->hdr; +struct snp_guest_msg *msg = &snp_dev->secret_request; +struct snp_guest_msg_hdr *hdr = &msg->hdr; -memset (req,0 ,sizeof (*req)); +memset (msg,0 ,sizeof (*msg)); hdr->algo =SNP_AEAD_AES_256_GCM ; hdr->hdr_version =MSG_HDR_VER ;
@@ -347,7 +347,7 @@ static int enc_payload(struct snp_guest_dev *snp_dev, u64 seqno, int version, u8pr_debug ("request [seqno %lld type %d version %d sz %d]\n" , hdr->msg_seqno, hdr->msg_type, hdr->msg_version, hdr->msg_sz); -return __enc_payload (snp_dev, req, payload, sz); +return __enc_payload (snp_dev, msg, payload, sz); } static int __handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code,
@@ -496,8 +496,8 @@ struct snp_req_resp {static int get_report (struct snp_guest_dev *snp_dev,struct snp_guest_request_ioctl *arg) {struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_report_req *req = &snp_dev->req.report; -struct snp_report_resp *resp; +struct snp_report_req *report_req = &snp_dev->req.report; +struct snp_report_resp *report_resp;int rc, resp_len;lockdep_assert_held (&snp_cmd_mutex);
@@ -505,7 +505,7 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_ioif (!arg->req_data || !arg->resp_data)return -EINVAL ; -if (copy_from_user (req, (void __user *)arg->req_data,sizeof (*req))) +if (copy_from_user (report_req, (void __user *)arg->req_data,sizeof (*report_req)))return -EFAULT ;/*
@@ -513,30 +513,29 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_io* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp->data) + crypto->a_len; - resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); -if (!resp) + resp_len =sizeof (report_resp->data) + crypto->a_len; + report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); +if (!report_resp)return -ENOMEM ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg, -SNP_MSG_REPORT_REQ , req,sizeof (*req), resp->data, - resp_len); + rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + report_req,sizeof (*report_req), report_resp->data, resp_len);if (rc) goto e_free; -if (copy_to_user ((void __user *)arg->resp_data, resp,sizeof (*resp))) +if (copy_to_user ((void __user *)arg->resp_data, report_resp,sizeof (*report_resp))) rc = -EFAULT ; e_free: -kfree (resp); +kfree (report_resp);return rc; }static int get_derived_key (struct snp_guest_dev *snp_dev,struct snp_guest_request_ioctl *arg) { -struct snp_derived_key_req *req = &snp_dev->req.derived_key; +struct snp_derived_key_req *derived_key_req = &snp_dev->req.derived_key;struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_derived_key_resp resp = {0 }; +struct snp_derived_key_resp derived_key_resp = {0 };int rc, resp_len;/* Response data is 64 bytes and max authsize for GCM is 16 bytes. */ u8 buf[64 +16 ];
@@ -551,25 +550,27 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp.data) + crypto->a_len; + resp_len =sizeof (derived_key_resp.data) + crypto->a_len;if (sizeof (buf) < resp_len)return -ENOMEM ; -if (copy_from_user (req, (void __user *)arg->req_data,sizeof (*req))) +if (copy_from_user (derived_key_req, (void __user *)arg->req_data, +sizeof (*derived_key_req)))return -EFAULT ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg, -SNP_MSG_KEY_REQ , req,sizeof (*req), buf, resp_len); + rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_KEY_REQ , + derived_key_req,sizeof (*derived_key_req), buf, resp_len);if (rc)return rc; -memcpy (resp.data, buf,sizeof (resp.data)); -if (copy_to_user ((void __user *)arg->resp_data, &resp,sizeof (resp))) +memcpy (derived_key_resp.data, buf,sizeof (derived_key_resp.data)); +if (copy_to_user ((void __user *)arg->resp_data, &derived_key_resp, +sizeof (derived_key_resp))) rc = -EFAULT ;/* The response buffer contains the sensitive data, explicitly clear it. */ memzero_explicit (buf,sizeof (buf)); -memzero_explicit (&resp,sizeof (resp)); +memzero_explicit (&derived_key_resp,sizeof (derived_key_resp));return rc; }
@@ -577,9 +578,9 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques struct snp_req_resp *io) { -struct snp_ext_report_req *req = &snp_dev->req.ext_report; +struct snp_ext_report_req *report_req = &snp_dev->req.ext_report;struct snp_guest_crypto *crypto = snp_dev->crypto; -struct snp_report_resp *resp; +struct snp_report_resp *report_resp;int ret, npages =0 , resp_len;sockptr_t certs_address;
@@ -588,22 +589,22 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesif (sockptr_is_null (io->req_data) ||sockptr_is_null (io->resp_data))return -EINVAL ; -if (copy_from_sockptr (req, io->req_data,sizeof (*req))) +if (copy_from_sockptr (report_req, io->req_data,sizeof (*report_req)))return -EFAULT ;/* caller does not want certificate data */ -if (!req->certs_len || !req->certs_address) +if (!report_req->certs_len || !report_req->certs_address) goto cmd; -if (req->certs_len >SEV_FW_BLOB_MAX_SIZE || - !IS_ALIGNED (req->certs_len,PAGE_SIZE )) +if (report_req->certs_len >SEV_FW_BLOB_MAX_SIZE || + !IS_ALIGNED (report_req->certs_len,PAGE_SIZE ))return -EINVAL ;if (sockptr_is_kernel (io->resp_data)) { - certs_address =KERNEL_SOCKPTR ((void *)req->certs_address); + certs_address =KERNEL_SOCKPTR ((void *)report_req->certs_address); }else { - certs_address =USER_SOCKPTR ((void __user *)req->certs_address); -if (!access_ok (certs_address.user, req->certs_len)) + certs_address =USER_SOCKPTR ((void __user *)report_req->certs_address); +if (!access_ok (certs_address.user, report_req->certs_len))return -EFAULT ; }
@@ -613,45 +614,45 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques* the host. If host does not supply any certs in it, then copy * zeros to indicate that certificate data was not provided. */ -memset (snp_dev->certs_data,0 , req->certs_len); - npages = req->certs_len >>PAGE_SHIFT ; +memset (snp_dev->certs_data,0 , report_req->certs_len); + npages = report_req->certs_len >>PAGE_SHIFT ; cmd:/* * The intermediate response buffer is used while decrypting the * response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (resp->data) + crypto->a_len; - resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); -if (!resp) + resp_len =sizeof (report_resp->data) + crypto->a_len; + report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT ); +if (!report_resp)return -ENOMEM ; snp_dev->input.data_npages = npages; - ret =handle_guest_request (snp_dev,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg, -SNP_MSG_REPORT_REQ , &req->data, -sizeof (req->data), resp->data, resp_len); + ret =handle_guest_request (snp_dev,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + &report_req->data,sizeof (report_req->data), + report_resp->data, resp_len);/* If certs length is invalid then copy the returned length */ if (arg->vmm_error ==SNP_GUEST_VMM_ERR_INVALID_LEN ) { - req->certs_len = snp_dev->input.data_npages <<PAGE_SHIFT ; + report_req->certs_len = snp_dev->input.data_npages <<PAGE_SHIFT ; -if (copy_to_sockptr (io->req_data, req,sizeof (*req))) +if (copy_to_sockptr (io->req_data, report_req,sizeof (*report_req))) ret = -EFAULT ; }if (ret) goto e_free; -if (npages &©_to_sockptr (certs_address, snp_dev->certs_data, req->certs_len)) { +if (npages &©_to_sockptr (certs_address, snp_dev->certs_data, report_req->certs_len)) { ret = -EFAULT ; goto e_free; } -if (copy_to_sockptr (io->resp_data, resp,sizeof (*resp))) +if (copy_to_sockptr (io->resp_data, report_resp,sizeof (*report_resp))) ret = -EFAULT ; e_free: -kfree (resp); +kfree (report_resp);return ret; }
Re: [PATCH v11 02/20] virt: sev-guest: Rename local guest message variables
In reply to Nikunj A DadhaniaQuoted 5 lines · Nikunj A Dadhania
Rename local guest message variables for more clarity
No functional change.
Signed-off-by Nikunj A Dadhania <[email protected]>
Quoted 4 lines
--- drivers/virt/coco/sev-guest/sev-guest.c | 117 ++++++++++++------------ 1 file changed, 59 insertions(+), 58 deletions(-)
PATCH v11 3/20 virt: sev-guest: Fix user-visible strings
In reply to Nikunj A DadhaniaUser-visible abbreviations should be in capitals, ensure messages are readable and clear.
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +4 -4
@@ -114,7 +114,7 @@ static bool is_vmpck_empty(struct snp_guest_dev *snp_dev)*/ static void snp_disable_vmpck (struct snp_guest_dev *snp_dev) { -dev_alert (snp_dev->dev,"Disabling vmpck_id %d to prevent IV reuse.\n" , +dev_alert (snp_dev->dev,"Disabling VMPCK%d communication key to prevent IV reuse.\n" , vmpck_id);memzero_explicit (snp_dev->vmpck,VMPCK_KEY_LEN ); snp_dev->vmpck =NULL ;
@@ -1117,13 +1117,13 @@ static int __init sev_guest_probe(struct platform_device *pdev) ret = -EINVAL ; snp_dev->vmpck =get_vmpck (vmpck_id, secrets, &snp_dev->os_area_msg_seqno);if (!snp_dev->vmpck) { -dev_err (dev,"invalid vmpck id %d\n" , vmpck_id); +dev_err (dev,"Invalid VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }/* Verify that VMPCK is not zero. */ if (is_vmpck_empty (snp_dev)) { -dev_err (dev,"vmpck id %d is null\n" , vmpck_id); +dev_err (dev,"Empty VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }
@@ -1174,7 +1174,7 @@ static int __init sev_guest_probe(struct platform_device *pdev)if (ret) goto e_free_cert_data; -dev_info (dev,"Initialized SEV guest driver (using vmpck_id %d)\n" , vmpck_id); +dev_info (dev,"Initialized SEV guest driver (using VMPCK%d communication key)\n" , vmpck_id);return 0 ; e_free_cert_data:
Signature · 1 line
2.34.1
[tip: x86/sev] virt: sev-guest: Fix user-visible strings
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: 5f7c38f81df206b370d97a827251bd4bc50ff46b Gitweb: https://git.kernel.org/tip/5f7c38f81df206b370d97a827251bd4bc50ff46b Author: Nikunj A Dadhania <[email protected]> AuthorDate: Wed, 31 Jul 2024 20:37:54 +05:30 Committer: Borislav Petkov (AMD) <[email protected]> CommitterDate: Tue, 27 Aug 2024 10:35:06 +02:00
virt: sev-guest: Fix user-visible strings
User-visible abbreviations should be in capitals, ensure messages are readable and clear.
No functional change.
--- drivers/virt/coco/sev-guest/sev-guest.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +4 -4
@@ -114,7 +114,7 @@ static bool is_vmpck_empty(struct snp_guest_dev *snp_dev)*/ static void snp_disable_vmpck (struct snp_guest_dev *snp_dev) { -dev_alert (snp_dev->dev,"Disabling vmpck_id %d to prevent IV reuse.\n" , +dev_alert (snp_dev->dev,"Disabling VMPCK%d communication key to prevent IV reuse.\n" , vmpck_id);memzero_explicit (snp_dev->vmpck,VMPCK_KEY_LEN ); snp_dev->vmpck =NULL ;
@@ -1117,13 +1117,13 @@ static int __init sev_guest_probe(struct platform_device *pdev) ret = -EINVAL ; snp_dev->vmpck =get_vmpck (vmpck_id, secrets, &snp_dev->os_area_msg_seqno);if (!snp_dev->vmpck) { -dev_err (dev,"invalid vmpck id %d\n" , vmpck_id); +dev_err (dev,"Invalid VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }/* Verify that VMPCK is not zero. */ if (is_vmpck_empty (snp_dev)) { -dev_err (dev,"vmpck id %d is null\n" , vmpck_id); +dev_err (dev,"Empty VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }
@@ -1174,7 +1174,7 @@ static int __init sev_guest_probe(struct platform_device *pdev)if (ret) goto e_free_cert_data; -dev_info (dev,"Initialized SEV guest driver (using vmpck_id %d)\n" , vmpck_id); +dev_info (dev,"Initialized SEV guest driver (using VMPCK%d communication key)\n" , vmpck_id);return 0 ; e_free_cert_data:
Re: [PATCH v11 03/20] virt: sev-guest: Fix user-visible strings
In reply to Nikunj A DadhaniaQuoted 6 lines · Nikunj A Dadhania
User-visible abbreviations should be in capitals, ensure messages are readable and clear.
No functional change.
Signed-off-by Nikunj A Dadhania <[email protected]>
Quoted 4 lines
--- drivers/virt/coco/sev-guest/sev-guest.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
PATCH v11 4/20 virt: sev-guest: Ensure the SNP guest messages do not exceed a page
In reply to Nikunj A DadhaniaCurrently, snp_guest_msg includes a message header (96 bytes) and a payload (4000 bytes). There is an implicit assumption here that the SNP message header will always be 96 bytes, and with that assumption the payload array size has been set to 4000 bytes magic number. If any new member is added to the SNP message header, the SNP guest message will span more than a page.
Instead of using magic number '4000' for the payload, declare the snp_guest_msg in a way that payload plus the message header do not exceed a page.
--- arch/x86/include/asm/sev.h | 2 +- drivers/virt/coco/sev-guest/sev-guest.c | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-)
arch/x86/include/asm/sev.h +1 -1
@@ -164,7 +164,7 @@ struct snp_guest_msg_hdr {struct snp_guest_msg {struct snp_guest_msg_hdr hdr; -u8 payload[4000 ]; +u8 payload[PAGE_SIZE -sizeof (struct snp_guest_msg_hdr )]; } __packed;struct sev_guest_platform_data {
drivers/virt/coco/sev-guest/sev-guest.c +3 -0
@@ -1131,6 +1131,9 @@ static int __init sev_guest_probe(struct platform_device *pdev) snp_dev->dev = dev; snp_dev->secrets = secrets; +/* Ensure SNP guest messages do not span more than a page */ +BUILD_BUG_ON (sizeof (struct snp_guest_msg ) >PAGE_SIZE ); +/* Allocate the shared page used for the request and response message. */ snp_dev->request =alloc_shared_pages (dev,sizeof (struct snp_guest_msg ));if (!snp_dev->request)
Signature · 1 line
2.34.1
[tip: x86/sev] virt: sev-guest: Ensure the SNP guest messages do not exceed a page
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: 2b9ac0b84c2cae91bbaceab62df4de6d503421ec Gitweb: https://git.kernel.org/tip/2b9ac0b84c2cae91bbaceab62df4de6d503421ec Author: Nikunj A Dadhania <[email protected]> AuthorDate: Wed, 31 Jul 2024 20:37:55 +05:30 Committer: Borislav Petkov (AMD) <[email protected]> CommitterDate: Tue, 27 Aug 2024 10:35:38 +02:00
virt: sev-guest: Ensure the SNP guest messages do not exceed a page
Currently, struct snp_guest_msg includes a message header (96 bytes) and a payload (4000 bytes). There is an implicit assumption here that the SNP message header will always be 96 bytes, and with that assumption the payload array size has been set to 4000 bytes - a magic number. If any new member is added to the SNP message header, the SNP guest message will span more than a page.
Instead of using a magic number for the payload, declare struct snp_guest_msg in a way that payload plus the message header do not exceed a page.
[ bp: Massage. ]
--- arch/x86/include/asm/sev.h | 2 +- drivers/virt/coco/sev-guest/sev-guest.c | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-)
arch/x86/include/asm/sev.h +1 -1
@@ -164,7 +164,7 @@ struct snp_guest_msg_hdr {struct snp_guest_msg {struct snp_guest_msg_hdr hdr; -u8 payload[4000 ]; +u8 payload[PAGE_SIZE -sizeof (struct snp_guest_msg_hdr )]; } __packed;struct sev_guest_platform_data {
drivers/virt/coco/sev-guest/sev-guest.c +2 -0
@@ -1092,6 +1092,8 @@ static int __init sev_guest_probe(struct platform_device *pdev)void __iomem *mapping;int ret; +BUILD_BUG_ON (sizeof (struct snp_guest_msg ) >PAGE_SIZE ); +if (!cc_platform_has (CC_ATTR_GUEST_SEV_SNP ))return -ENODEV ;
PATCH v11 5/20 virt: sev-guest: Use AES GCM crypto library
In reply to Nikunj A DadhaniaThe sev-guest driver encryption code uses the crypto API for SNP guest messaging with the AMD Security processor. In order to enable secure TSC, SEV-SNP guests need to send such a TSC_INFO message before the APs are booted. Details from the TSC_INFO response will then be used to program the VMSA before the APs are brought up.
However, the crypto API is not available this early in the boot process.
In preparation for moving the encryption code out of sev-guest to support secure TSC and to ease review, switch to using the AES GCM library implementation instead.
Drop __enc_payload() and dec_payload() helpers as both are small and can be moved to the respective callers.
--- arch/x86/include/asm/sev.h | 3 + drivers/virt/coco/sev-guest/sev-guest.c | 175 ++++++------------------ drivers/virt/coco/sev-guest/Kconfig | 4 +- 3 files changed, 43 insertions(+), 139 deletions(-)
arch/x86/include/asm/sev.h +3 -0
@@ -120,6 +120,9 @@ struct snp_req_data { };#define MAX_AUTHTAG_LEN 32 +#define AUTHTAG_LEN 16 +#define AAD_LEN 48 +#define MSG_HDR_VER 1/* See SNP spec SNP_GUEST_REQUEST section for the structure */ enum msg_type {
drivers/virt/coco/sev-guest/sev-guest.c +39 -136
297 lines not on this page · raw message
drivers/virt/coco/sev-guest/Kconfig +1 -3
@@ -2,9 +2,7 @@ config SEV_GUEST tristate "AMD SEV Guest driver" default m depends on AMD_MEM_ENCRYPT - select CRYPTO - select CRYPTO_AEAD2 - select CRYPTO_GCM + select CRYPTO_LIB_AESGCM select TSM_REPORTS help SEV-SNP firmware provides the guest a mechanism to communicate with
Signature · 1 line
2.34.1
PATCH v11 6/20 x86/sev: Handle failures from snp_init()
In reply to Nikunj A DadhaniaAddress the ignored failures from snp_init() in sme_enable(). Add error handling for scenarios where snp_init() fails to retrieve the SEV-SNP CC blob or encounters issues while parsing the CC blob. This change ensures that SNP guests will error out early, preventing delayed error reporting or undefined behavior.
--- arch/x86/mm/mem_encrypt_identity.c | 7 +++++++ 1 file changed, 7 insertions(+)
arch/x86/mm/mem_encrypt_identity.c +7 -0
@@ -535,6 +535,13 @@ void __head sme_enable(struct boot_params *bp)if (snp && !(msr &MSR_AMD64_SEV_SNP_ENABLED ))snp_abort (); +/* +* The SEV-SNP CC blob should be present and parsing CC blob should +* succeed when SEV-SNP is enabled. +*/ +if (!snp && (msr &MSR_AMD64_SEV_SNP_ENABLED )) +snp_abort (); +/* Check if memory encryption is enabled */ if (feature_mask ==AMD_SME_BIT ) {if (!(bp->hdr.xloadflags &XLF_MEM_ENCRYPTION ))
Signature · 1 line
2.34.1
Borislav Petkov
maintainerRe: [PATCH v11 06/20] x86/sev: Handle failures from snp_init()
Quoted 3 lines · Nikunj A Dadhania
Address the ignored failures from
snp_init()insme_enable(). Add error handling for scenarios wheresnp_init()fails to retrieve the SEV-SNP CC blob or encounters issues while parsing the CC blob.
Is this a real issue you've encountered or?
Quoted 1 line
This change ensures
Avoid having "This patch" or "This commit" or "This <whatever>" in the commit message. It is tautologically useless.
Also, do
$ git grep 'This patch' Documentation/process
for more details.
Quoted 13 lines
that SNP guests will error out early, preventing delayed error reporting or undefined behavior.
Signed-off-by Nikunj A Dadhania <[email protected]>--- arch/x86/mm/mem_encrypt_identity.c | 7 +++++++ 1 file changed, 7 insertions(+)arch/x86/mm/mem_encrypt_identity.c +0
-0
arch/x86/mm/mem_encrypt_identity.c void __head sme_enable(struct boot_params *bp) · line 543
Quoted 9 lines
arch/x86/mm/mem_encrypt_identity.c +6
-0@@ -535,6 +535,13 @@ void __head sme_enable(struct boot_params *bp)if (snp && !(msr &MSR_AMD64_SEV_SNP_ENABLED ))snp_abort (); +/* +* The SEV-SNP CC blob should be present and parsing CC blob should +* succeed when SEV-SNP is enabled. +*/ +if (!snp && (msr &MSR_AMD64_SEV_SNP_ENABLED )) +snp_abort ();
Any chance you could combine the above and this test?
Perhaps look around at the code before adding your check - there might be some opportunity for aggregation and improvement...
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v11 06/20] x86/sev: Handle failures from snp_init()
Hi Boris,
Quoted 6 lines · Borislav Petkov
Quoted 3 lines · Nikunj A Dadhania
Address the ignored failures from
snp_init()insme_enable(). Add error handling for scenarios wheresnp_init()fails to retrieve the SEV-SNP CC blob or encounters issues while parsing the CC blob.Is this a real issue you've encountered or?
As per you comment [1], you had suggested to error out early in snp_init() instead of waiting till snp_init_platform_device(). As snp_init() was ignoring the failure case, I have added this patch. Following patch adds secrets page parsing from CC blob. When the parsing fails, snp_init() will return failure.
Quoted 5 lines
Quoted 2 lines
This change ensures
Avoid having "This patch" or "This commit" or "This <whatever>" in the commit message. It is tautologically useless.
Sure, will do.
Quoted 17 lines
Quoted 5 lines
arch/x86/mm/mem_encrypt_identity.c +0
-0arch/x86/mm/mem_encrypt_identity.c void __head sme_enable(struct boot_params *bp) · line 543
Quoted 9 lines
arch/x86/mm/mem_encrypt_identity.c +6
-0@@ -535,6 +535,13 @@ void __head sme_enable(struct boot_params *bp)if (snp && !(msr &MSR_AMD64_SEV_SNP_ENABLED ))snp_abort (); +/* +* The SEV-SNP CC blob should be present and parsing CC blob should +* succeed when SEV-SNP is enabled. +*/ +if (!snp && (msr &MSR_AMD64_SEV_SNP_ENABLED )) +snp_abort ();Any chance you could combine the above and this test?
Quoted 2 lines
Perhaps look around at the code before adding your check - there might be some opportunity for aggregation and improvement...
Sure, how about the below patch ?
From: Nikunj A Dadhania <[email protected]>
Date: Wed, 22 May 2024 12:43:42 +0530
Subject: [PATCH] x86/sev: Handle failures from snp_init()
Address the ignored failures from snp_init() in sme_enable(). Add error handling for scenarios where snp_init() fails to retrieve the SEV-SNP CC blob or encounters issues while parsing the CC blob. Ensure that SNP guests will error out early, preventing delayed error reporting or undefined behavior.
--- arch/x86/mm/mem_encrypt_identity.c | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-)
arch/x86/mm/mem_encrypt_identity.c +11 -4
@@ -495,7 +495,7 @@ void __head sme_enable(struct boot_params *bp)unsigned int eax, ebx, ecx, edx;unsigned long feature_mask;unsigned long me_mask; -bool snp; +bool snp, snp_enabled;u64 msr; snp =snp_init (bp);
@@ -529,10 +529,17 @@ void __head sme_enable(struct boot_params *bp)/* Check the SEV MSR whether SEV or SME is enabled */ RIP_REL_REF (sev_status) = msr =__rdmsr (MSR_AMD64_SEV ); - feature_mask = (msr &MSR_AMD64_SEV_ENABLED ) ?AMD_SEV_BIT :AMD_SME_BIT ; + snp_enabled = msr &MSR_AMD64_SEV_SNP_ENABLED ; + feature_mask = snp_enabled ?AMD_SEV_BIT :AMD_SME_BIT ; -/* The SEV-SNP CC blob should never be present unless SEV-SNP is enabled. */ -if (snp && !(msr &MSR_AMD64_SEV_SNP_ENABLED )) +/* +* The SEV-SNP CC blob should never be present unless SEV-SNP is enabled. +* +* The SEV-SNP CC blob should be present and parsing CC blob should +* succeed when SEV-SNP is enabled. +*/ +if ((snp && !snp_enabled) || + (!snp && snp_enabled))snp_abort ();/* Check if memory encryption is enabled */
Signature · 4 lines
2.34.1 1. https://lore.kernel.org/lkml/20240416144542.GFZh6PFjPNT9Zt3iUl@fat_crate.local/
Borislav Petkov
maintainerRe: [PATCH v11 06/20] x86/sev: Handle failures from snp_init()
Review
Quoted 3 lines · Nikunj A. Dadhania
(quoted diff) +2
-0+ if ((snp && !snp_enabled) || + (!snp && snp_enabled)) snp_abort();
And which boolean function is that?
arch/x86/mm/mem_encrypt_identity.c +5 -9
@@ -495,10 +495,10 @@ void __head sme_enable(struct boot_params *bp)unsigned int eax, ebx, ecx, edx;unsigned long feature_mask;unsigned long me_mask; -bool snp; +bool snp_en;u64 msr; - snp =snp_init (bp); + snp_en =snp_init (bp);/* Check for the SME/SEV support leaf */ eax =0x80000000 ;
@@ -531,15 +531,11 @@ void __head sme_enable(struct boot_params *bp)RIP_REL_REF (sev_status) = msr =__rdmsr (MSR_AMD64_SEV ); feature_mask = (msr &MSR_AMD64_SEV_ENABLED ) ?AMD_SEV_BIT :AMD_SME_BIT ; -/* The SEV-SNP CC blob should never be present unless SEV-SNP is enabled. */ -if (snp && !(msr &MSR_AMD64_SEV_SNP_ENABLED )) -snp_abort (); -/* -* The SEV-SNP CC blob should be present and parsing CC blob should -* succeed when SEV-SNP is enabled. +* Any discrepancies between the presence of a CC blob and SNP +* enablement abort the guest. */ -if (!snp && (msr &MSR_AMD64_SEV_SNP_ENABLED )) +if (snp_en ^ (msr &MSR_AMD64_SEV_SNP_ENABLED ))snp_abort ();/* Check if memory encryption is enabled */
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v11 06/20] x86/sev: Handle failures from snp_init()
Quoted 6 lines · Borislav Petkov
Review
Quoted 3 lines · Nikunj A. Dadhania
(quoted diff) +2
-0+ if ((snp && !snp_enabled) || + (!snp && snp_enabled)) snp_abort();And which boolean function is that?
Ah.. missed that.
arch/x86/mm/mem_encrypt_identity.c void __head sme_enable(struct boot_params *bp) · line 541
Quoted 12 lines
arch/x86/mm/mem_encrypt_identity.c +3
-3/* -* The SEV-SNP CC blob should be present and parsing CC blob should -* succeed when SEV-SNP is enabled. +* Any discrepancies between the presence of a CC blob and SNP +* enablement abort the guest. */ -if (!snp && (msr &MSR_AMD64_SEV_SNP_ENABLED )) +if (snp_en ^ (msr &MSR_AMD64_SEV_SNP_ENABLED ))snp_abort ();/* Check if memory encryption is enabled */
Do you want me to send the patch again with above change?
Regards
Nikunj
Borislav Petkov
maintainerRe: [PATCH v11 06/20] x86/sev: Handle failures from snp_init()
Quoted 1 line · Nikunj A. Dadhania
Do you want me to send the patch again with above change?
After I've gone through the whole set, sure.
Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquettePATCH v11 7/20 x86/sev: Cache the secrets page address
In reply to Nikunj A DadhaniaInstead of calling get_secrets_page(), which parses the CC blob every time to get the secrets page physical address (secrets_pa), save the secrets page physical address during snp_init() from the CC blob. Since get_secrets_page() is no longer used, remove the function.
--- arch/x86/coco/sev/core.c | 51 +++++++++------------------------------- 1 file changed, 11 insertions(+), 40 deletions(-)
arch/x86/coco/sev/core.c +11 -40
@@ -92,6 +92,9 @@ static struct ghcb *boot_ghcb __section(".data");/* Bitmap of SEV features supported by the hypervisor */ static u64 sev_hv_features__ro_after_init ; +/* Secrets page physical address from the CC blob */ +static u64 secrets_pa__ro_after_init ; +/* #VC handler runtime per-CPU data */ struct sev_es_runtime_data {struct ghcb ghcb_page;
@@ -722,45 +725,13 @@ void noinstr __sev_es_nmi_complete(void)__sev_put_ghcb (&state); } -static u64 __init get_secrets_page (void ) -{ -u64 pa_data = boot_params.cc_blob_address; -struct cc_blob_sev_info info; -void *map; - -/* -* The CC blob contains the address of the secrets page, check if the -* blob is present. -*/ -if (!pa_data) -return 0 ; - - map =early_memremap (pa_data,sizeof (info)); -if (!map) { -pr_err ("Unable to locate SNP secrets page: failed to map the Confidential Computing blob.\n" ); -return 0 ; - } -memcpy (&info, map,sizeof (info)); -early_memunmap (map,sizeof (info)); - -/* smoke-test the secrets page passed */ -if (!info.secrets_phys || info.secrets_len !=PAGE_SIZE ) -return 0 ; - -return info.secrets_phys; -} -static u64 __init get_snp_jump_table_addr (void ) {struct snp_secrets_page *secrets;void __iomem *mem; -u64 pa, addr; - - pa =get_secrets_page (); -if (!pa) -return 0 ; +u64 addr; - mem =ioremap_encrypted (pa,PAGE_SIZE ); + mem =ioremap_encrypted (secrets_pa,PAGE_SIZE );if (!mem) {pr_err ("Unable to locate AP jump table address: failed to map the SNP secrets page.\n" );return 0 ;
@@ -2300,6 +2271,11 @@ bool __head snp_init(struct boot_params *bp)if (!cc_info)return false; +if (cc_info->secrets_phys && cc_info->secrets_len ==PAGE_SIZE ) + secrets_pa = cc_info->secrets_phys; +else +return false; +setup_cpuid_table (cc_info);svsm_setup (cc_info);
@@ -2513,16 +2489,11 @@ static struct platform_device sev_guest_device = {static int __init snp_init_platform_device (void ) {struct sev_guest_platform_data data; -u64 gpa;if (!cc_platform_has (CC_ATTR_GUEST_SEV_SNP ))return -ENODEV ; - gpa =get_secrets_page (); -if (!gpa) -return -ENODEV ; - - data.secrets_gpa = gpa; + data.secrets_gpa = secrets_pa;if (platform_device_add_data (&sev_guest_device, &data,sizeof (data)))return -ENODEV ;
Signature · 1 line
2.34.1
PATCH v11 8/20 virt: sev-guest: Consolidate SNP guest messaging parameters to a struct
In reply to Nikunj A DadhaniaAdd a snp_guest_req structure to eliminate the need to pass a long list of parameters. This structure will be used to call the SNP Guest message request API, simplifying the function arguments.
Update the snp_issue_guest_request() prototype to include the new guest request structure.
--- arch/x86/include/asm/sev.h | 19 +++++++- arch/x86/coco/sev/core.c | 9 ++-- drivers/virt/coco/sev-guest/sev-guest.c | 62 ++++++++++++++++--------- 3 files changed, 61 insertions(+), 29 deletions(-)
arch/x86/include/asm/sev.h +17 -2
@@ -174,6 +174,19 @@ struct sev_guest_platform_data {u64 secrets_gpa; }; +struct snp_guest_req { +void *req_buf; +size_t req_sz; + +void *resp_buf; +size_t resp_sz; + +u64 exit_code; +unsigned int vmpck_id; +u8 msg_version; +u8 msg_type; +}; +/* * 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
@@ -395,7 +408,8 @@ void snp_set_wakeup_secondary_cpu(void);bool snp_init (struct boot_params *bp);void __noreturn snp_abort (void );void snp_dmi_setup (void ); -int snp_issue_guest_request (u64 exit_code,struct snp_req_data *input,struct snp_guest_request_ioctl *rio); +int snp_issue_guest_request (struct snp_guest_req *req,struct snp_req_data *input, +struct snp_guest_request_ioctl *rio);int snp_issue_svsm_attest_req (u64 call_id,struct svsm_call *call,struct svsm_attest_call *input);void snp_accept_memory (phys_addr_t start,phys_addr_t end);u64 snp_get_unsupported_features (u64 status);
@@ -425,7 +439,8 @@ static inline void snp_set_wakeup_secondary_cpu(void) { }static inline bool snp_init (struct boot_params *bp) {return false; }static inline void snp_abort (void ) { }static inline void snp_dmi_setup (void ) { } -static inline int snp_issue_guest_request (u64 exit_code,struct snp_req_data *input,struct snp_guest_request_ioctl *rio) +static inline int snp_issue_guest_request (struct snp_guest_req *req,struct snp_req_data *input, +struct snp_guest_request_ioctl *rio) {return -ENOTTY ; }
arch/x86/coco/sev/core.c +5 -4
@@ -2417,7 +2417,8 @@ int snp_issue_svsm_attest_req(u64 call_id, struct svsm_call *call, }EXPORT_SYMBOL_GPL (snp_issue_svsm_attest_req); -int snp_issue_guest_request (u64 exit_code,struct snp_req_data *input,struct snp_guest_request_ioctl *rio) +int snp_issue_guest_request (struct snp_guest_req *req,struct snp_req_data *input, +struct snp_guest_request_ioctl *rio) {struct ghcb_state state;struct es_em_ctxt ctxt;
@@ -2441,12 +2442,12 @@ int snp_issue_guest_request(u64 exit_code, struct snp_req_data *input, struct snvc_ghcb_invalidate (ghcb); -if (exit_code ==SVM_VMGEXIT_EXT_GUEST_REQUEST ) { +if (req->exit_code ==SVM_VMGEXIT_EXT_GUEST_REQUEST ) {ghcb_set_rax (ghcb, input->data_gpa);ghcb_set_rbx (ghcb, input->data_npages); } - ret =sev_es_ghcb_hv_call (ghcb, &ctxt, exit_code, input->req_gpa, input->resp_gpa); + ret =sev_es_ghcb_hv_call (ghcb, &ctxt, req->exit_code, input->req_gpa, input->resp_gpa);if (ret) goto e_put;
@@ -2461,7 +2462,7 @@ int snp_issue_guest_request(u64 exit_code, struct snp_req_data *input, struct sncase SNP_GUEST_VMM_ERR (SNP_GUEST_VMM_ERR_INVALID_LEN ):/* Number of expected pages are returned in RBX */ -if (exit_code ==SVM_VMGEXIT_EXT_GUEST_REQUEST ) { +if (req->exit_code ==SVM_VMGEXIT_EXT_GUEST_REQUEST ) { input->data_npages =ghcb_get_rbx (ghcb); ret = -ENOSPC ;break ;
drivers/virt/coco/sev-guest/sev-guest.c +39 -23
152 lines not on this page · raw message
Signature · 1 line
2.34.1
Borislav Petkov
maintainerRe: [PATCH v11 08/20] virt: sev-guest: Consolidate SNP guest messaging parameters to a struct
Quoted 8 lines · Nikunj A Dadhania
drivers/virt/coco/sev-guest/sev-guest.c +8
-0+static int handle_guest_request (struct snp_guest_dev *snp_dev,u64 exit_code, +struct snp_guest_request_ioctl *rio,u8 type, +void *req_buf,size_t req_sz,void *resp_buf, +u32 resp_sz) +{ +struct snp_guest_req req = { + .msg_version = rio->msg_version, + .msg_type = type,
drivers/virt/coco/sev-guest/sev-guest.c static int handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code, · line 409
Quoted 10 lines
drivers/virt/coco/sev-guest/sev-guest.c +10
-0+ .vmpck_id = vmpck_id, + .req_buf = req_buf, + .req_sz = req_sz, + .resp_buf = resp_buf, + .resp_sz = resp_sz, + .exit_code = exit_code, + }; + +return snp_send_guest_request (snp_dev, &req, rio); +}
Right, except you don't need that silly routine copying stuff around either but simply do the right thing at each call site from the get-go.
using the following coding pattern:
struct snp_guest_req req = { };
/* assign all members required for the respective call: */
req.<member> = ...;
...
err = snp_send_guest_request(snp_dev, &req, rio);
if (err)
...Thx.
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteRe: [PATCH v11 08/20] virt: sev-guest: Consolidate SNP guest messaging parameters to a struct
Quoted 25 lines · Borislav Petkov
Quoted 8 lines · Nikunj A Dadhania
drivers/virt/coco/sev-guest/sev-guest.c +8
-0+static int handle_guest_request (struct snp_guest_dev *snp_dev,u64 exit_code, +struct snp_guest_request_ioctl *rio,u8 type, +void *req_buf,size_t req_sz,void *resp_buf, +u32 resp_sz) +{ +struct snp_guest_req req = { + .msg_version = rio->msg_version, + .msg_type = type,drivers/virt/coco/sev-guest/sev-guest.c static int handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code, · line 409
Quoted 10 lines
drivers/virt/coco/sev-guest/sev-guest.c +10
-0+ .vmpck_id = vmpck_id, + .req_buf = req_buf, + .req_sz = req_sz, + .resp_buf = resp_buf, + .resp_sz = resp_sz, + .exit_code = exit_code, + }; + +return snp_send_guest_request (snp_dev, &req, rio); +}Right, except you don't need that silly routine copying stuff around either but simply do the right thing at each call site from the get-go.
using the following coding pattern:
Quoted 9 lines
struct snp_guest_req req = { };
/* assign all members required for the respective call: */
req.<member> = ...;
...
err = snp_send_guest_request(snp_dev, &req, rio);
if (err)
...Sure, will update all the call sites.
Regards
Nikunj
PATCH v11 9/20 virt: sev-guest: Reduce the scope of SNP command mutex
In reply to Nikunj A DadhaniaThe SNP command mutex is used to serialize access to the shared buffer, command handling, and message sequence number.
All shared buffer, command handling, and message sequence updates are done within snp_send_guest_request(), so moving the mutex to this function is appropriate and maintains the critical section.
Since the mutex is now taken at a later point in time, remove the lockdep checks that occur before taking the mutex.
--- drivers/virt/coco/sev-guest/sev-guest.c | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-)
drivers/virt/coco/sev-guest/sev-guest.c +2 -15
@@ -345,6 +345,8 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_guesu64 seqno;int rc; +guard (mutex)(&snp_cmd_mutex); +/* Get message sequence and verify that its a non-zero */ seqno =snp_get_msg_seqno (snp_dev);if (!seqno)
@@ -419,8 +421,6 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_iostruct snp_report_resp *report_resp;int rc, resp_len; -lockdep_assert_held (&snp_cmd_mutex); -if (!arg->req_data || !arg->resp_data)return -EINVAL ;
@@ -458,8 +458,6 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque/* Response data is 64 bytes and max authsize for GCM is 16 bytes. */ u8 buf[64 +16 ]; -lockdep_assert_held (&snp_cmd_mutex); -if (!arg->req_data || !arg->resp_data)return -EINVAL ;
@@ -501,8 +499,6 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesint ret, npages =0 , resp_len;sockptr_t certs_address; -lockdep_assert_held (&snp_cmd_mutex); -if (sockptr_is_null (io->req_data) ||sockptr_is_null (io->resp_data))return -EINVAL ;
@@ -590,12 +586,9 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longif (!input.msg_version)return -EINVAL ; -mutex_lock (&snp_cmd_mutex); -/* Check if the VMPCK is not empty */ if (is_vmpck_empty (snp_dev)) {dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -mutex_unlock (&snp_cmd_mutex);return -ENOTTY ; }
@@ -620,8 +613,6 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longbreak ; } -mutex_unlock (&snp_cmd_mutex); -if (input.exitinfo2 &©_to_user (argp, &input,sizeof (input)))return -EFAULT ;
@@ -736,8 +727,6 @@ static int sev_svsm_report_new(struct tsm_report *report, void *data) man_len =SZ_4K ; certs_len =SEV_FW_BLOB_MAX_SIZE ; -guard (mutex)(&snp_cmd_mutex); -if (guid_is_null (&desc->service_guid)) { call_id =SVSM_ATTEST_CALL (SVSM_ATTEST_SERVICES ); }else {
@@ -872,8 +861,6 @@ static int sev_report_new(struct tsm_report *report, void *data)if (!buf)return -ENOMEM ; -guard (mutex)(&snp_cmd_mutex); -/* Check if the VMPCK is not empty */ if (is_vmpck_empty (snp_dev)) {dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" );
Signature · 1 line
2.34.1
Re: [PATCH v11 09/20] virt: sev-guest: Reduce the scope of SNP command mutex
Quoted 56 lines · Nikunj A Dadhania
The SNP command mutex is used to serialize access to the shared buffer, command handling, and message sequence number.
All shared buffer, command handling, and message sequence updates are done within
snp_send_guest_request(), so moving the mutex to this function is appropriate and maintains the critical section.Since the mutex is now taken at a later point in time, remove the lockdep checks that occur before taking the mutex.
Signed-off-by Nikunj A Dadhania <[email protected]>--- drivers/virt/coco/sev-guest/sev-guest.c | 17 ++--------------- 1 file changed, 2 insertions(+), 15 deletions(-)drivers/virt/coco/sev-guest/sev-guest.c +2
-6@@ -345,6 +345,8 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_guesu64 seqno;int rc; +guard (mutex)(&snp_cmd_mutex); +/* Get message sequence and verify that its a non-zero */ seqno =snp_get_msg_seqno (snp_dev);if (!seqno)@@ -419,8 +421,6 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_iostruct snp_report_resp *report_resp;int rc, resp_len; -lockdep_assert_held (&snp_cmd_mutex); -if (!arg->req_data || !arg->resp_data)return -EINVAL ;@@ -458,8 +458,6 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque/* Response data is 64 bytes and max authsize for GCM is 16 bytes. */ u8 buf[64 +16 ]; -lockdep_assert_held (&snp_cmd_mutex); -if (!arg->req_data || !arg->resp_data)return -EINVAL ;@@ -501,8 +499,6 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesint ret, npages =0 , resp_len;sockptr_t certs_address; -lockdep_assert_held (&snp_cmd_mutex); -if (sockptr_is_null (io->req_data) ||sockptr_is_null (io->resp_data))return -EINVAL ;
drivers/virt/coco/sev-guest/sev-guest.c static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned long · line 590
Quoted 7 lines
drivers/virt/coco/sev-guest/sev-guest.c +0
-2@@ -590,12 +586,9 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longif (!input.msg_version)return -EINVAL ; -mutex_lock (&snp_cmd_mutex); -/* Check if the VMPCK is not empty */ if (is_vmpck_empty (snp_dev)) {
Are we ok with this being outside of the lock now?
I believe is_vmpck_empty() can get a false and then be waiting on the mutex while snp_disable_vmpck() is called. Suddenly the code thinks the VMPCK is valid when it isn't anymore. Not sure if that matters, as the guest request will fail anyway?
Thanks,
Tom
Quoted 32 lines
drivers/virt/coco/sev-guest/sev-guest.c +0
-7dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -mutex_unlock (&snp_cmd_mutex);return -ENOTTY ; }@@ -620,8 +613,6 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longbreak ; } -mutex_unlock (&snp_cmd_mutex); -if (input.exitinfo2 &©_to_user (argp, &input,sizeof (input)))return -EFAULT ;@@ -736,8 +727,6 @@ static int sev_svsm_report_new(struct tsm_report *report, void *data) man_len =SZ_4K ; certs_len =SEV_FW_BLOB_MAX_SIZE ; -guard (mutex)(&snp_cmd_mutex); -if (guid_is_null (&desc->service_guid)) { call_id =SVSM_ATTEST_CALL (SVSM_ATTEST_SERVICES ); }else {@@ -872,8 +861,6 @@ static int sev_report_new(struct tsm_report *report, void *data)if (!buf)return -ENOMEM ; -guard (mutex)(&snp_cmd_mutex); -/* Check if the VMPCK is not empty */ if (is_vmpck_empty (snp_dev)) {dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" );
Re: [PATCH v11 09/20] virt: sev-guest: Reduce the scope of SNP command mutex
Hi Tom,
Quoted 11 lines · Tom Lendacky
Review static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned long · line 590
Quoted 8 lines · Nikunj A Dadhania
(quoted diff) +0
-2@@ -590,12 +586,9 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned long if (!input.msg_version) return -EINVAL; - mutex_lock(&snp_cmd_mutex); - /* Check if the VMPCK is not empty */ if (is_vmpck_empty(snp_dev)) {Are we ok with this being outside of the lock now?
We can move the check inside the lock, and get_* will try to prepare the message and after grabbing the lock if the the VMPCK is empty we would fail. Something like below:
drivers/virt/coco/sev-guest/sev-guest.c +6 -12
@@ -347,6 +347,12 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_guesguard (mutex)(&snp_cmd_mutex); +/* Check if the VMPCK is not empty */ +if (is_vmpck_empty (snp_dev)) { +dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); +return -ENOTTY ; + } +/* Get message sequence and verify that its a non-zero */ seqno =snp_get_msg_seqno (snp_dev);if (!seqno)
@@ -594,12 +600,6 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longif (!input.msg_version)return -EINVAL ; -/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { -dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -return -ENOTTY ; - } -switch (ioctl) {case SNP_GET_REPORT : ret =get_report (snp_dev, &input);
@@ -869,12 +869,6 @@ static int sev_report_new(struct tsm_report *report, void *data)if (!buf)return -ENOMEM ; -/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { -dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -return -ENOTTY ; - } - cert_table = buf + report_size;struct snp_ext_report_req ext_req = { .data = { .vmpl = desc->privlevel },
Quoted 4 lines
I believe
is_vmpck_empty()can get a false and then be waiting on the mutex whilesnp_disable_vmpck()is called. Suddenly the code thinks the VMPCK is valid when it isn't anymore. Not sure if that matters, as the guest request will fail anyway?
The above code will fail early.
Quoted 4 lines
Thanks,
Tom
Regards
Nikunj
Re: [PATCH v11 09/20] virt: sev-guest: Reduce the scope of SNP command mutex
Quoted 15 lines · Nikunj A. Dadhania
Hi Tom,
Quoted 11 lines · Tom Lendacky
drivers/virt/coco/sev-guest/sev-guest.c static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned long · line 590
Quoted 8 lines · Nikunj A Dadhania
drivers/virt/coco/sev-guest/sev-guest.c +0
-2@@ -590,12 +586,9 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longif (!input.msg_version)return -EINVAL ; -mutex_lock (&snp_cmd_mutex); -/* Check if the VMPCK is not empty */ if (is_vmpck_empty (snp_dev)) {Are we ok with this being outside of the lock now?
Quoted 3 lines
We can move the check inside the lock, and get_* will try to prepare the message and after grabbing the lock if the the VMPCK is empty we would fail. Something like below:
Yep, works for me.
Thanks,
Tom
Quoted 61 lines
drivers/virt/coco/sev-guest/sev-guest.c +6
-12@@ -347,6 +347,12 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_guesguard (mutex)(&snp_cmd_mutex); +/* Check if the VMPCK is not empty */ +if (is_vmpck_empty (snp_dev)) { +dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); +return -ENOTTY ; + } +/* Get message sequence and verify that its a non-zero */ seqno =snp_get_msg_seqno (snp_dev);if (!seqno)@@ -594,12 +600,6 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longif (!input.msg_version)return -EINVAL ; -/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { -dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -return -ENOTTY ; - } -switch (ioctl) {case SNP_GET_REPORT : ret =get_report (snp_dev, &input);@@ -869,12 +869,6 @@ static int sev_report_new(struct tsm_report *report, void *data)if (!buf)return -ENOMEM ; -/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { -dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" ); -return -ENOTTY ; - } - cert_table = buf + report_size;struct snp_ext_report_req ext_req = { .data = { .vmpl = desc->privlevel },Quoted 6 lines
I believe
is_vmpck_empty()can get a false and then be waiting on the mutex whilesnp_disable_vmpck()is called. Suddenly the code thinks the VMPCK is valid when it isn't anymore. Not sure if that matters, as the guest request will fail anyway?The above code will fail early.
Quoted 4 lines
Thanks,
TomRegards
Nikunj
PATCH v11 10/20 virt: sev-guest: Carve out SNP message context structure
In reply to Nikunj A DadhaniaCurrently, the sev-guest driver is the only user of SNP guest messaging. snp_guest_dev structure holds all the allocated buffers, secrets page and VMPCK details. In preparation of adding messaging allocation and initialization APIs, decouple snp_guest_dev from messaging-related information by carving out guest message context structure(snp_msg_desc).
Incorporate this newly added context into snp_send_guest_request() and all related functions, replacing the use of the snp_guest_dev.
No functional change.
--- arch/x86/include/asm/sev.h | 21 +++ drivers/virt/coco/sev-guest/sev-guest.c | 183 ++++++++++++------------ 2 files changed, 111 insertions(+), 93 deletions(-)
arch/x86/include/asm/sev.h +21 -0
@@ -234,6 +234,27 @@ struct snp_secrets_page {u8 rsvd4[3744 ]; } __packed; +struct snp_msg_desc { +/* request and response are in unencrypted memory */ +struct snp_guest_msg *request, *response; + +/* +* Avoid information leakage by double-buffering shared messages +* in fields that are in regular encrypted memory. +*/ +struct snp_guest_msg secret_request, secret_response; + +struct snp_secrets_page *secrets; +struct snp_req_data input; + +void *certs_data; + +struct aesgcm_ctx *ctx; + +u32 *os_area_msg_seqno; +u8 *vmpck; +}; +/* * The SVSM Calling Area (CA) related structures. */
drivers/virt/coco/sev-guest/sev-guest.c +90 -93
491 lines not on this page · raw message
Signature · 1 line
2.34.1
Re: [PATCH v11 10/20] virt: sev-guest: Carve out SNP message context structure
Quoted 2 lines · Nikunj A Dadhania
Currently, the sev-guest driver is the only user of SNP guest messaging.
snp_guest_devstructure holds all the allocated buffers, secrets page and
The snp_guest_dev structure...
Quoted 1 line
VMPCK details. In preparation of adding messaging allocation and
s/of/for/
Quoted 2 lines
initialization APIs, decouple
snp_guest_devfrom messaging-related information by carving out guest message contextstructure(snp_msg_desc).
s/out guest/out the guest/
Quoted 7 lines
Incorporate this newly added context into
snp_send_guest_request()and all related functions, replacing the use of thesnp_guest_dev.No functional change.
Signed-off-by Nikunj A Dadhania <[email protected]>
Quoted 564 lines
--- arch/x86/include/asm/sev.h | 21 +++ drivers/virt/coco/sev-guest/sev-guest.c | 183 ++++++++++++------------ 2 files changed, 111 insertions(+), 93 deletions(-)arch/x86/include/asm/sev.h +21
-0@@ -234,6 +234,27 @@ struct snp_secrets_page {u8 rsvd4[3744 ]; } __packed; +struct snp_msg_desc { +/* request and response are in unencrypted memory */ +struct snp_guest_msg *request, *response; + +/* +* Avoid information leakage by double-buffering shared messages +* in fields that are in regular encrypted memory. +*/ +struct snp_guest_msg secret_request, secret_response; + +struct snp_secrets_page *secrets; +struct snp_req_data input; + +void *certs_data; + +struct aesgcm_ctx *ctx; + +u32 *os_area_msg_seqno; +u8 *vmpck; +}; +/* * The SVSM Calling Area (CA) related structures. */ drivers/virt/coco/sev-guest/sev-guest.c +90
-93@@ -40,26 +40,13 @@ struct snp_guest_dev {struct device *dev;struct miscdevice misc; -void *certs_data; -struct aesgcm_ctx *ctx; -/* request and response are in unencrypted memory */ -struct snp_guest_msg *request, *response; - -/* -* Avoid information leakage by double-buffering shared messages -* in fields that are in regular encrypted memory. -*/ -struct snp_guest_msg secret_request, secret_response; +struct snp_msg_desc *msg_desc; -struct snp_secrets_page *secrets; -struct snp_req_data input;union {struct snp_report_req report;struct snp_derived_key_req derived_key;struct snp_ext_report_req ext_report; } req; -u32 *os_area_msg_seqno; -u8 *vmpck; };/* @@ -76,12 +63,12 @@ MODULE_PARM_DESC(vmpck_id, "The VMPCK ID to use when communicating with the PSP./* Mutex to serialize the shared buffer access and command handling. */ static DEFINE_MUTEX (snp_cmd_mutex); -static bool is_vmpck_empty (struct snp_guest_dev *snp_dev) +static bool is_vmpck_empty (struct snp_msg_desc *mdesc) {char zero_key[VMPCK_KEY_LEN ] = {0 }; -if (snp_dev->vmpck) -return !memcmp (snp_dev->vmpck, zero_key,VMPCK_KEY_LEN ); +if (mdesc->vmpck) +return !memcmp (mdesc->vmpck, zero_key,VMPCK_KEY_LEN );return true; }@@ -103,30 +90,30 @@ static bool is_vmpck_empty(struct snp_guest_dev *snp_dev)* vulnerable. If the sequence number were incremented for a fresh IV the ASP * will reject the request. */ -static void snp_disable_vmpck (struct snp_guest_dev *snp_dev) +static void snp_disable_vmpck (struct snp_msg_desc *mdesc) { -dev_alert (snp_dev->dev,"Disabling VMPCK%d communication key to prevent IV reuse.\n" , +pr_alert ("Disabling VMPCK%d communication key to prevent IV reuse.\n" , vmpck_id); -memzero_explicit (snp_dev->vmpck,VMPCK_KEY_LEN ); - snp_dev->vmpck =NULL ; +memzero_explicit (mdesc->vmpck,VMPCK_KEY_LEN ); + mdesc->vmpck =NULL ; } -static inline u64 __snp_get_msg_seqno (struct snp_guest_dev *snp_dev) +static inline u64 __snp_get_msg_seqno (struct snp_msg_desc *mdesc) {u64 count;lockdep_assert_held (&snp_cmd_mutex);/* Read the current message sequence counter from secrets pages */ - count = *snp_dev->os_area_msg_seqno; + count = *mdesc->os_area_msg_seqno;return count +1 ; }/* Return a non-zero on success */ -static u64 snp_get_msg_seqno (struct snp_guest_dev *snp_dev) +static u64 snp_get_msg_seqno (struct snp_msg_desc *mdesc) { -u64 count =__snp_get_msg_seqno (snp_dev); +u64 count =__snp_get_msg_seqno (mdesc);/* * The message sequence counter for the SNP guest request is a 64-bit @@ -137,20 +124,20 @@ static u64 snp_get_msg_seqno(struct snp_guest_dev *snp_dev)* invalid number and will fail the message request. */ if (count >=UINT_MAX ) { -dev_err (snp_dev->dev,"request message sequence counter overflow\n" ); +pr_err ("request message sequence counter overflow\n" );return 0 ; }return count; } -static void snp_inc_msg_seqno (struct snp_guest_dev *snp_dev) +static void snp_inc_msg_seqno (struct snp_msg_desc *mdesc) {/* * The counter is also incremented by the PSP, so increment it by 2 * and save in secrets page. */ - *snp_dev->os_area_msg_seqno +=2 ; + *mdesc->os_area_msg_seqno +=2 ; }static inline struct snp_guest_dev *to_snp_dev (struct file *file)@@ -177,13 +164,13 @@ static struct aesgcm_ctx *snp_init_crypto(u8 *key, size_t keylen)return ctx; } -static int verify_and_dec_payload (struct snp_guest_dev *snp_dev,struct snp_guest_req *req) +static int verify_and_dec_payload (struct snp_msg_desc *mdesc,struct snp_guest_req *req) { -struct snp_guest_msg *resp_msg = &snp_dev->secret_response; -struct snp_guest_msg *req_msg = &snp_dev->secret_request; +struct snp_guest_msg *resp_msg = &mdesc->secret_response; +struct snp_guest_msg *req_msg = &mdesc->secret_request;struct snp_guest_msg_hdr *req_msg_hdr = &req_msg->hdr;struct snp_guest_msg_hdr *resp_msg_hdr = &resp_msg->hdr; -struct aesgcm_ctx *ctx = snp_dev->ctx; +struct aesgcm_ctx *ctx = mdesc->ctx;u8 iv[GCM_AES_IV_SIZE ] = {}; pr_debug("response [seqno %lld type %d version %d sz %d]\n",@@ -191,7 +178,7 @@ static int verify_and_dec_payload(struct snp_guest_dev *snp_dev, struct snp_gues resp_msg_hdr->msg_sz);/* Copy response from shared memory to encrypted memory. */ -memcpy (resp_msg, snp_dev->response,sizeof (*resp_msg)); +memcpy (resp_msg, mdesc->response,sizeof (*resp_msg));/* Verify that the sequence counter is incremented by 1 */ if (unlikely (resp_msg_hdr->msg_seqno != (req_msg_hdr->msg_seqno +1 )))@@ -218,11 +205,11 @@ static int verify_and_dec_payload(struct snp_guest_dev *snp_dev, struct snp_guesreturn 0 ; } -static int enc_payload (struct snp_guest_dev *snp_dev,u64 seqno,struct snp_guest_req *req) +static int enc_payload (struct snp_msg_desc *mdesc,u64 seqno,struct snp_guest_req *req) { -struct snp_guest_msg *msg = &snp_dev->secret_request; +struct snp_guest_msg *msg = &mdesc->secret_request;struct snp_guest_msg_hdr *hdr = &msg->hdr; -struct aesgcm_ctx *ctx = snp_dev->ctx; +struct aesgcm_ctx *ctx = mdesc->ctx;u8 iv[GCM_AES_IV_SIZE ] = {};memset (msg,0 ,sizeof (*msg));@@ -253,7 +240,7 @@ static int enc_payload(struct snp_guest_dev *snp_dev, u64 seqno, struct snp_guesreturn 0 ; } -static int __handle_guest_request (struct snp_guest_dev *snp_dev,struct snp_guest_req *req, +static int __handle_guest_request (struct snp_msg_desc *mdesc,struct snp_guest_req *req,struct snp_guest_request_ioctl *rio) {unsigned long req_start = jiffies;@@ -268,7 +255,7 @@ static int __handle_guest_request(struct snp_guest_dev *snp_dev, struct snp_gues* sequence number must be incremented or the VMPCK must be deleted to * prevent reuse of the IV. */ - rc =snp_issue_guest_request (req, &snp_dev->input, rio); + rc =snp_issue_guest_request (req, &mdesc->input, rio);switch (rc) {case -ENOSPC :/* @@ -278,7 +265,7 @@ static int __handle_guest_request(struct snp_guest_dev *snp_dev, struct snp_gues* order to increment the sequence number and thus avoid * IV reuse. */ - override_npages = snp_dev->input.data_npages; + override_npages = mdesc->input.data_npages; req->exit_code =SVM_VMGEXIT_GUEST_REQUEST ;/* @@ -318,7 +305,7 @@ static int __handle_guest_request(struct snp_guest_dev *snp_dev, struct snp_gues* structure and any failure will wipe the VMPCK, preventing further * use anyway. */ -snp_inc_msg_seqno (snp_dev); +snp_inc_msg_seqno (mdesc);if (override_err) { rio->exitinfo2 = override_err;@@ -334,12 +321,12 @@ static int __handle_guest_request(struct snp_guest_dev *snp_dev, struct snp_gues }if (override_npages) - snp_dev->input.data_npages = override_npages; + mdesc->input.data_npages = override_npages;return rc; } -static int snp_send_guest_request (struct snp_guest_dev *snp_dev,struct snp_guest_req *req, +static int snp_send_guest_request (struct snp_msg_desc *mdesc,struct snp_guest_req *req,struct snp_guest_request_ioctl *rio) {u64 seqno;@@ -348,15 +335,15 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_guesguard (mutex)(&snp_cmd_mutex);/* Get message sequence and verify that its a non-zero */ - seqno =snp_get_msg_seqno (snp_dev); + seqno =snp_get_msg_seqno (mdesc);if (!seqno)return -EIO ;/* Clear shared memory's response for the host to populate. */ -memset (snp_dev->response,0 ,sizeof (struct snp_guest_msg )); +memset (mdesc->response,0 ,sizeof (struct snp_guest_msg )); -/* Encrypt the userspace provided payload in snp_dev->secret_request. */ - rc =enc_payload (snp_dev, seqno, req); +/* Encrypt the userspace provided payload in mdesc->secret_request. */ + rc =enc_payload (mdesc, seqno, req);if (rc)return rc;@@ -364,34 +351,33 @@ static int snp_send_guest_request(struct snp_guest_dev *snp_dev, struct snp_gues* Write the fully encrypted request to the shared unencrypted * request page. */ -memcpy (snp_dev->request, &snp_dev->secret_request, -sizeof (snp_dev->secret_request)); +memcpy (mdesc->request, &mdesc->secret_request, +sizeof (mdesc->secret_request)); - rc =__handle_guest_request (snp_dev, req, rio); + rc =__handle_guest_request (mdesc, req, rio);if (rc) {if (rc == -EIO && rio->exitinfo2 ==SNP_GUEST_VMM_ERR (SNP_GUEST_VMM_ERR_INVALID_LEN ))return rc; -dev_alert (snp_dev->dev, -"Detected error from ASP request. rc: %d, exitinfo2: 0x%llx\n" , - rc, rio->exitinfo2); +pr_alert ("Detected error from ASP request. rc: %d, exitinfo2: 0x%llx\n" , + rc, rio->exitinfo2); -snp_disable_vmpck (snp_dev); +snp_disable_vmpck (mdesc);return rc; } - rc =verify_and_dec_payload (snp_dev, req); + rc =verify_and_dec_payload (mdesc, req);if (rc) { -dev_alert (snp_dev->dev,"Detected unexpected decode failure from ASP. rc: %d\n" , rc); -snp_disable_vmpck (snp_dev); +pr_alert ("Detected unexpected decode failure from ASP. rc: %d\n" , rc); +snp_disable_vmpck (mdesc);return rc; }return 0 ; } -static int handle_guest_request (struct snp_guest_dev *snp_dev,u64 exit_code, +static int handle_guest_request (struct snp_msg_desc *mdesc,u64 exit_code,struct snp_guest_request_ioctl *rio,u8 type,void *req_buf,size_t req_sz,void *resp_buf,u32 resp_sz)@@ -407,7 +393,7 @@ static int handle_guest_request(struct snp_guest_dev *snp_dev, u64 exit_code, .exit_code = exit_code, }; -return snp_send_guest_request (snp_dev, &req, rio); +return snp_send_guest_request (mdesc, &req, rio); }struct snp_req_resp {@@ -418,6 +404,7 @@ struct snp_req_resp {static int get_report (struct snp_guest_dev *snp_dev,struct snp_guest_request_ioctl *arg) {struct snp_report_req *report_req = &snp_dev->req.report; +struct snp_msg_desc *mdesc = snp_dev->msg_desc;struct snp_report_resp *report_resp;int rc, resp_len;@@ -432,12 +419,12 @@ static int get_report(struct snp_guest_dev *snp_dev, struct snp_guest_request_io* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (report_resp->data) + snp_dev->ctx->authsize; + resp_len =sizeof (report_resp->data) + mdesc->ctx->authsize; report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT );if (!report_resp)return -ENOMEM ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + rc =handle_guest_request (mdesc,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , report_req,sizeof (*report_req), report_resp->data, resp_len);if (rc) goto e_free;@@ -454,6 +441,7 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque {struct snp_derived_key_req *derived_key_req = &snp_dev->req.derived_key;struct snp_derived_key_resp derived_key_resp = {0 }; +struct snp_msg_desc *mdesc = snp_dev->msg_desc;int rc, resp_len;/* Response data is 64 bytes and max authsize for GCM is 16 bytes. */ u8 buf[64 +16 ];@@ -466,7 +454,7 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (derived_key_resp.data) + snp_dev->ctx->authsize; + resp_len =sizeof (derived_key_resp.data) + mdesc->ctx->authsize;if (sizeof (buf) < resp_len)return -ENOMEM ;@@ -474,7 +462,7 @@ static int get_derived_key(struct snp_guest_dev *snp_dev, struct snp_guest_reque sizeof(*derived_key_req)))return -EFAULT ; - rc =handle_guest_request (snp_dev,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_KEY_REQ , + rc =handle_guest_request (mdesc,SVM_VMGEXIT_GUEST_REQUEST , arg,SNP_MSG_KEY_REQ , derived_key_req,sizeof (*derived_key_req), buf, resp_len);if (rc)return rc;@@ -495,6 +483,7 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques {struct snp_ext_report_req *report_req = &snp_dev->req.ext_report; +struct snp_msg_desc *mdesc = snp_dev->msg_desc;struct snp_report_resp *report_resp;int ret, npages =0 , resp_len;sockptr_t certs_address;@@ -527,7 +516,7 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques* the host. If host does not supply any certs in it, then copy * zeros to indicate that certificate data was not provided. */ -memset (snp_dev->certs_data,0 , report_req->certs_len); +memset (mdesc->certs_data,0 , report_req->certs_len); npages = report_req->certs_len >>PAGE_SHIFT ; cmd:/* @@ -535,19 +524,19 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_reques* response payload. Make sure that it has enough space to cover the * authtag. */ - resp_len =sizeof (report_resp->data) + snp_dev->ctx->authsize; + resp_len =sizeof (report_resp->data) + mdesc->ctx->authsize; report_resp =kzalloc (resp_len,GFP_KERNEL_ACCOUNT );if (!report_resp)return -ENOMEM ; - snp_dev->input.data_npages = npages; - ret =handle_guest_request (snp_dev,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , + mdesc->input.data_npages = npages; + ret =handle_guest_request (mdesc,SVM_VMGEXIT_EXT_GUEST_REQUEST , arg,SNP_MSG_REPORT_REQ , &report_req->data,sizeof (report_req->data), report_resp->data, resp_len);/* If certs length is invalid then copy the returned length */ if (arg->vmm_error ==SNP_GUEST_VMM_ERR_INVALID_LEN ) { - report_req->certs_len = snp_dev->input.data_npages <<PAGE_SHIFT ; + report_req->certs_len = mdesc->input.data_npages <<PAGE_SHIFT ;if (copy_to_sockptr (io->req_data, report_req,sizeof (*report_req))) ret = -EFAULT ;@@ -556,7 +545,7 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesif (ret) goto e_free; -if (npages &©_to_sockptr (certs_address, snp_dev->certs_data, report_req->certs_len)) { +if (npages &©_to_sockptr (certs_address, mdesc->certs_data, report_req->certs_len)) { ret = -EFAULT ; goto e_free; }@@ -572,6 +561,7 @@ static int get_ext_report(struct snp_guest_dev *snp_dev, struct snp_guest_requesstatic long snp_guest_ioctl (struct file *file,unsigned int ioctl,unsigned long arg) {struct snp_guest_dev *snp_dev =to_snp_dev (file); +struct snp_msg_desc *mdesc = snp_dev->msg_desc;void __user *argp = (void __user *)arg;struct snp_guest_request_ioctl input;struct snp_req_resp io;@@ -587,7 +577,7 @@ static long snp_guest_ioctl(struct file *file, unsigned int ioctl, unsigned longreturn -EINVAL ;/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { +if (is_vmpck_empty (mdesc)) {dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" );return -ENOTTY ; }@@ -862,7 +852,7 @@ static int sev_report_new(struct tsm_report *report, void *data)return -ENOMEM ;/* Check if the VMPCK is not empty */ -if (is_vmpck_empty (snp_dev)) { +if (is_vmpck_empty (snp_dev->msg_desc)) {dev_err_ratelimited (snp_dev->dev,"VMPCK is disabled\n" );return -ENOTTY ; }@@ -992,6 +982,7 @@ static int __init sev_guest_probe(struct platform_device *pdev)struct snp_secrets_page *secrets;struct device *dev = &pdev->dev;struct snp_guest_dev *snp_dev; +struct snp_msg_desc *mdesc;struct miscdevice *misc;void __iomem *mapping;int ret;@@ -1014,46 +1005,50 @@ static int __init sev_guest_probe(struct platform_device *pdev)if (!snp_dev) goto e_unmap; + mdesc =devm_kzalloc (&pdev->dev,sizeof (struct snp_msg_desc ),GFP_KERNEL ); +if (!mdesc) + goto e_unmap; +/* Adjust the default VMPCK key based on the executing VMPL level */ if (vmpck_id ==-1 ) vmpck_id = snp_vmpl; ret = -EINVAL ; - snp_dev->vmpck =get_vmpck (vmpck_id, secrets, &snp_dev->os_area_msg_seqno); -if (!snp_dev->vmpck) { + mdesc->vmpck =get_vmpck (vmpck_id, secrets, &mdesc->os_area_msg_seqno); +if (!mdesc->vmpck) {dev_err (dev,"Invalid VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }/* Verify that VMPCK is not zero. */ -if (is_vmpck_empty (snp_dev)) { +if (is_vmpck_empty (mdesc)) {dev_err (dev,"Empty VMPCK%d communication key\n" , vmpck_id); goto e_unmap; }platform_set_drvdata (pdev, snp_dev); snp_dev->dev = dev; - snp_dev->secrets = secrets; + mdesc->secrets = secrets;/* Ensure SNP guest messages do not span more than a page */ BUILD_BUG_ON (sizeof (struct snp_guest_msg ) >PAGE_SIZE );/* Allocate the shared page used for the request and response message. */ - snp_dev->request =alloc_shared_pages (dev,sizeof (struct snp_guest_msg )); -if (!snp_dev->request) + mdesc->request =alloc_shared_pages (dev,sizeof (struct snp_guest_msg )); +if (!mdesc->request) goto e_unmap; - snp_dev->response =alloc_shared_pages (dev,sizeof (struct snp_guest_msg )); -if (!snp_dev->response) + mdesc->response =alloc_shared_pages (dev,sizeof (struct snp_guest_msg )); +if (!mdesc->response) goto e_free_request; - snp_dev->certs_data =alloc_shared_pages (dev,SEV_FW_BLOB_MAX_SIZE ); -if (!snp_dev->certs_data) + mdesc->certs_data =alloc_shared_pages (dev,SEV_FW_BLOB_MAX_SIZE ); +if (!mdesc->certs_data) goto e_free_response; ret = -EIO ; - snp_dev->ctx =snp_init_crypto (snp_dev->vmpck,VMPCK_KEY_LEN ); -if (!snp_dev->ctx) + mdesc->ctx =snp_init_crypto (mdesc->vmpck,VMPCK_KEY_LEN ); +if (!mdesc->ctx) goto e_free_cert_data; misc = &snp_dev->misc;@@ -1062,9 +1057,9 @@ static int __init sev_guest_probe(struct platform_device *pdev) misc->fops = &snp_guest_fops;/* Initialize the input addresses for guest request */ - snp_dev->input.req_gpa =__pa (snp_dev->request); - snp_dev->input.resp_gpa =__pa (snp_dev->response); - snp_dev->input.data_gpa =__pa (snp_dev->certs_data); + mdesc->input.req_gpa =__pa (mdesc->request); + mdesc->input.resp_gpa =__pa (mdesc->response); + mdesc->input.data_gpa =__pa (mdesc->certs_data);/* Set the privlevel_floor attribute based on the vmpck_id */ sev_tsm_ops.privlevel_floor = vmpck_id;@@ -1081,17 +1076,18 @@ static int __init sev_guest_probe(struct platform_device *pdev)if (ret) goto e_free_ctx; + snp_dev->msg_desc = mdesc;dev_info (dev,"Initialized SEV guest driver (using VMPCK%d communication key)\n" , vmpck_id);return 0 ; e_free_ctx: -kfree (snp_dev->ctx); +kfree (mdesc->ctx); e_free_cert_data: -free_shared_pages (snp_dev->certs_data,SEV_FW_BLOB_MAX_SIZE ); +free_shared_pages (mdesc->certs_data,SEV_FW_BLOB_MAX_SIZE ); e_free_response: -free_shared_pages (snp_dev->response,sizeof (struct snp_guest_msg )); +free_shared_pages (mdesc->response,sizeof (struct snp_guest_msg )); e_free_request: -free_shared_pages (snp_dev->request,sizeof (struct snp_guest_msg )); +free_shared_pages (mdesc->request,sizeof (struct snp_guest_msg )); e_unmap:iounmap (mapping);return ret;@@ -1100,11 +1096,12 @@ static int __init sev_guest_probe(struct platform_device *pdev) static void __exit sev_guest_remove(struct platform_device *pdev) {struct snp_guest_dev *snp_dev =platform_get_drvdata (pdev); +struct snp_msg_desc *mdesc = snp_dev->msg_desc; -free_shared_pages (snp_dev->certs_data,SEV_FW_BLOB_MAX_SIZE ); -free_shared_pages (snp_dev->response,sizeof (struct snp_guest_msg )); -free_shared_pages (snp_dev->request,sizeof (struct snp_guest_msg )); -kfree (snp_dev->ctx); +free_shared_pages (mdesc->certs_data,SEV_FW_BLOB_MAX_SIZE ); +free_shared_pages (mdesc->response,sizeof (struct snp_guest_msg )); +free_shared_pages (mdesc->request,sizeof (struct snp_guest_msg )); +kfree (mdesc->ctx);misc_deregister (&snp_dev->misc); }
PATCH v11 11/20 x86/sev: Carve out and export SNP guest messaging init routines
In reply to Nikunj A DadhaniaCurrently, the SEV guest driver is the only user of SNP guest messaging. All routines for initializing SNP guest messaging are implemented within the SEV guest driver. To add Secure TSC guest support, these initialization routines need to be available during early boot.
Carve out common SNP guest messaging buffer allocations and message initialization routines to core/sev.c and export them. These newly added APIs set up the SNP message context (snp_msg_desc), which contains all the necessary details for sending SNP guest messages.
At present, the SEV guest platform data structure is used to pass the secrets page physical address to SEV guest driver. Since the secrets page address is locally available to the initialization routine, use the cached address. Remove the unused SEV guest platform data structure.
--- arch/x86/include/asm/sev.h | 71 ++++++++- arch/x86/coco/sev/core.c | 133 +++++++++++++++- drivers/virt/coco/sev-guest/sev-guest.c | 194 +++--------------------- 3 files changed, 213 insertions(+), 185 deletions(-)
arch/x86/include/asm/sev.h +67 -4
@@ -14,6 +14,7 @@#include <asm/insn.h> #include <asm/sev-common.h> #include <asm/coco.h> +#include <asm/set_memory.h> #define GHCB_PROTOCOL_MIN 1ULL#define GHCB_PROTOCOL_MAX 2ULL
@@ -170,10 +171,6 @@ struct snp_guest_msg {u8 payload[PAGE_SIZE -sizeof (struct snp_guest_msg_hdr )]; } __packed; -struct sev_guest_platform_data { -u64 secrets_gpa; -}; -struct snp_guest_req {void *req_buf;size_t req_sz;
@@ -253,6 +250,7 @@ struct snp_msg_desc {u32 *os_area_msg_seqno;u8 *vmpck; +int vmpck_id; };/*
@@ -438,6 +436,63 @@ u64 sev_get_status(void);void sev_show_status (void );void snp_update_svsm_ca (void ); +static inline void free_shared_pages (void *buf,size_t sz) +{ +unsigned int npages =PAGE_ALIGN (sz) >>PAGE_SHIFT ; +int ret; + +if (!buf) +return ; + + ret =set_memory_encrypted ((unsigned long )buf, npages); +if (ret) { +WARN_ONCE (ret,"failed to restore encryption mask (leak it)\n" ); +return ; + } + +__free_pages (virt_to_page (buf),get_order (sz)); +} + +static inline void *alloc_shared_pages (size_t sz) +{ +unsigned int npages =PAGE_ALIGN (sz) >>PAGE_SHIFT ; +struct page *page; +int ret; + + page =alloc_pages (GFP_KERNEL_ACCOUNT ,get_order (sz)); +if (!page) +return NULL ; + + ret =set_memory_decrypted ((unsigned long )page_address (page), npages); +if (ret) { +pr_err ("failed to mark page shared, ret=%d\n" , ret); +__free_pages (page,get_order (sz)); +return NULL ; + } + +return page_address (page); +} + +static inline bool is_vmpck_empty (struct snp_msg_desc *mdesc) +{ +char zero_key[VMPCK_KEY_LEN ] = {0 }; + +if (mdesc->vmpck) +return !memcmp (mdesc->vmpck, zero_key,VMPCK_KEY_LEN ); + +return true; +} + +int snp_msg_init (struct snp_msg_desc *mdesc,int vmpck_id); +struct snp_msg_desc *snp_msg_alloc (void ); + +static inline void snp_msg_cleanup (struct snp_msg_desc *mdesc) +{ + mdesc->vmpck =NULL ; + mdesc->os_area_msg_seqno =NULL ; +kfree (mdesc->ctx); +} +#else /* !CONFIG_AMD_MEM_ENCRYPT */ #define snp_vmpl 0
@@ -474,6 +529,14 @@ static inline u64 snp_get_unsupported_features(u64 status) { return 0; }static inline u64 sev_get_status (void ) {return 0 ; }static inline void sev_show_status (void ) { }static inline void snp_update_svsm_ca (void ) { } +static inline void free_shared_pages (void *buf,size_t sz) { } +static inline void *alloc_shared_pages (size_t sz) {return NULL ; } +static inline bool is_vmpck_empty (struct snp_msg_desc *mdesc) {return false; } + +static inline int snp_msg_init (struct snp_msg_desc *mdesc,int vmpck_id) {return -1 ; } +static inline struct snp_msg_desc *snp_msg_alloc (void ) {return NULL ; } + +static inline void snp_msg_cleanup (struct snp_msg_desc *mdesc) { }#endif /* CONFIG_AMD_MEM_ENCRYPT */
arch/x86/coco/sev/core.c +127 -6
157 lines not on this page · raw message
drivers/virt/coco/sev-guest/sev-guest.c +19 -175
278 lines not on this page · raw message
Signature · 1 line
2.34.1
Re: [PATCH v11 11/20] x86/sev: Carve out and export SNP guest messaging init routines
Quoted 10 lines · Nikunj A Dadhania
Currently, the SEV guest driver is the only user of SNP guest messaging. All routines for initializing SNP guest messaging are implemented within the SEV guest driver. To add Secure TSC guest support, these initialization routines need to be available during early boot.
Carve out common SNP guest messaging buffer allocations and message initialization routines to
core/sev.cand export them. These newly added APIs set up the SNP message context (snp_msg_desc), which contains all the necessary details for sending SNP guest messages.
Quoted 6 lines
At present, the SEV guest platform data structure is used to pass the secrets page physical address to SEV guest driver. Since the secrets page address is locally available to the initialization routine, use the cached address. Remove the unused SEV guest platform data structure.
Signed-off-by Nikunj A Dadhania <[email protected]>
Quoted 6 lines
--- arch/x86/include/asm/sev.h | 71 ++++++++- arch/x86/coco/sev/core.c | 133 +++++++++++++++- drivers/virt/coco/sev-guest/sev-guest.c | 194 +++--------------------- 3 files changed, 213 insertions(+), 185 deletions(-)
PATCH v11 12/20 x86/sev: Relocate SNP guest messaging routines to common code
In reply to Nikunj A DadhaniaAt present, the SEV guest driver exclusively handles SNP guest messaging. All routines for sending guest messages are embedded within the guest driver. To support Secure TSC, SEV-SNP guests must communicate with the AMD Security Processor during early boot. However, these guest messaging functions are not accessible during early boot since they are currently part of the guest driver.
Hence, relocate the core SNP guest messaging functions to SEV common code and provide an API for sending SNP guest messages.
No functional change, but just an export symbol.
--- arch/x86/include/asm/sev.h | 8 + arch/x86/coco/sev/core.c | 284 +++++++++++++++++++++++ drivers/virt/coco/sev-guest/sev-guest.c | 286 ------------------------ arch/x86/Kconfig | 1 + drivers/virt/coco/sev-guest/Kconfig | 1 - 5 files changed, 293 insertions(+), 287 deletions(-)
arch/x86/include/asm/sev.h +8 -0
@@ -125,6 +125,9 @@ struct snp_req_data {#define AAD_LEN 48#define MSG_HDR_VER 1 +#define SNP_REQ_MAX_RETRY_DURATION (60*HZ) +#define SNP_REQ_RETRY_DELAY (2*HZ) +/* See SNP spec SNP_GUEST_REQUEST section for the structure */ enum msg_type {SNP_MSG_TYPE_INVALID =0 ,
@@ -493,6 +496,9 @@ static inline void snp_msg_cleanup(struct snp_msg_desc *mdesc) kfree(mdesc->ctx); } +int snp_send_guest_request (struct snp_msg_desc *mdesc,struct snp_guest_req *req, +struct snp_guest_request_ioctl *rio); +#else /* !CONFIG_AMD_MEM_ENCRYPT */ #define snp_vmpl 0
@@ -537,6 +543,8 @@ static inline int snp_msg_init(struct snp_msg_desc *mdesc, int vmpck_id) { returstatic inline struct snp_msg_desc *snp_msg_alloc (void ) {return NULL ; }static inline void snp_msg_cleanup (struct snp_msg_desc *mdesc) { } +static inline int snp_send_guest_request (struct snp_msg_desc *mdesc,struct snp_guest_req *req, +struct snp_guest_request_ioctl *rio) {return -ENODEV ; }#endif /* CONFIG_AMD_MEM_ENCRYPT */
arch/x86/coco/sev/core.c +284 -0
287 lines not on this page · raw message
drivers/virt/coco/sev-guest/sev-guest.c +0 -286
304 lines not on this page · raw message
arch/x86/Kconfig +1 -0
@@ -1552,6 +1552,7 @@ config AMD_MEM_ENCRYPT select ARCH_HAS_CC_PLATFORM select X86_MEM_ENCRYPT select UNACCEPTED_MEMORY + select CRYPTO_LIB_AESGCM help Say yes to enable support for the encryption of system memory. This requires an AMD processor that supports Secure Memory
drivers/virt/coco/sev-guest/Kconfig +0 -1
@@ -2,7 +2,6 @@ config SEV_GUEST tristate "AMD SEV Guest driver" default m depends on AMD_MEM_ENCRYPT - select CRYPTO_LIB_AESGCM select TSM_REPORTS help SEV-SNP firmware provides the guest a mechanism to communicate with
Signature · 1 line
2.34.1
Re: [PATCH v11 12/20] x86/sev: Relocate SNP guest messaging routines to common code
Quoted 11 lines · Nikunj A Dadhania
At present, the SEV guest driver exclusively handles SNP guest messaging. All routines for sending guest messages are embedded within the guest driver. To support Secure TSC, SEV-SNP guests must communicate with the AMD Security Processor during early boot. However, these guest messaging functions are not accessible during early boot since they are currently part of the guest driver.
Hence, relocate the core SNP guest messaging functions to SEV common code and provide an API for sending SNP guest messages.
No functional change, but just an export symbol.
That means we can drop the export symbol on snp_issue_guest_request() and make it static, right?
Quoted 2 lines
Signed-off-by Nikunj A Dadhania <[email protected]>
Quoted 7 lines
--- arch/x86/include/asm/sev.h | 8 + arch/x86/coco/sev/core.c | 284 +++++++++++++++++++++++ drivers/virt/coco/sev-guest/sev-guest.c | 286 ------------------------ arch/x86/Kconfig | 1 + drivers/virt/coco/sev-guest/Kconfig | 1 - 5 files changed, 293 insertions(+), 287 deletions(-)
Re: [PATCH v11 12/20] x86/sev: Relocate SNP guest messaging routines to common code
Quoted 8 lines · Tom Lendacky
Quoted 7 lines · Nikunj A Dadhania
At present, the SEV guest driver exclusively handles SNP guest messaging. All routines for sending guest messages are embedded within the guest driver. To support Secure TSC, SEV-SNP guests must communicate with the AMD Security Processor during early boot. However, these guest messaging functions are not accessible during early boot since they are currently part of the guest driver.
Quoted 7 lines
Quoted 4 lines
Hence, relocate the core SNP guest messaging functions to SEV common code and provide an API for sending SNP guest messages.
No functional change, but just an export symbol.
That means we can drop the export symbol on
snp_issue_guest_request()and make it static, right?
Yes, let me remove that.
Quoted 13 lines
Quoted 3 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Reviewed-by Tom Lendacky <[email protected]>Quoted 7 lines
--- arch/x86/include/asm/sev.h | 8 + arch/x86/coco/sev/core.c | 284 +++++++++++++++++++++++ drivers/virt/coco/sev-guest/sev-guest.c | 286 ------------------------ arch/x86/Kconfig | 1 + drivers/virt/coco/sev-guest/Kconfig | 1 - 5 files changed, 293 insertions(+), 287 deletions(-)
Regards
Nikunj
PATCH v11 13/20 x86/cc: Add CC_ATTR_GUEST_SECURE_TSC
In reply to Nikunj A DadhaniaAdd confidential compute platform attribute CC_ATTR_GUEST_SECURE_TSC that can be used by the guest to query whether the Secure TSC feature is active.
--- include/linux/cc_platform.h | 8 ++++++++ arch/x86/coco/core.c | 3 +++ 2 files changed, 11 insertions(+)
include/linux/cc_platform.h +8 -0
@@ -88,6 +88,14 @@ enum cc_attr {* enabled to run SEV-SNP guests. */ CC_ATTR_HOST_SEV_SNP , + +/** +* @CC_ATTR_GUEST_SECURE_TSC: Secure TSC is active. +* +* The platform/OS is running as a guest/virtual machine and actively +* using AMD SEV-SNP Secure TSC feature. +*/ + CC_ATTR_GUEST_SECURE_TSC, };#ifdef CONFIG_ARCH_HAS_CC_PLATFORM
arch/x86/coco/core.c +3 -0
@@ -100,6 +100,9 @@ static bool noinstr amd_cc_platform_has(enum cc_attr attr)case CC_ATTR_HOST_SEV_SNP :return cc_flags.host_sev_snp; +case CC_ATTR_GUEST_SECURE_TSC : +return sev_status &MSR_AMD64_SNP_SECURE_TSC ; +default :return false; }
Signature · 1 line
2.34.1
Re: [PATCH v11 13/20] x86/cc: Add CC_ATTR_GUEST_SECURE_TSC
Quoted 15 lines · Nikunj A Dadhania
Add confidential compute platform attribute
CC_ATTR_GUEST_SECURE_TSCthat can be used by the guest to query whether the Secure TSC feature is active.Signed-off-by Nikunj A Dadhania <[email protected]>--- include/linux/cc_platform.h | 8 ++++++++ arch/x86/coco/core.c | 3 +++ 2 files changed, 11 insertions(+)include/linux/cc_platform.h +0
-0@@ -88,6 +88,14 @@ enum cc_attr {* enabled to run SEV-SNP guests.
include/linux/cc_platform.h enum cc_attr { · line 98
Quoted 10 lines
include/linux/cc_platform.h +8
-0*/ CC_ATTR_HOST_SEV_SNP , + +/** +* @CC_ATTR_GUEST_SECURE_TSC: Secure TSC is active. +* +* The platform/OS is running as a guest/virtual machine and actively +* using AMD SEV-SNP Secure TSC feature. +*/ + CC_ATTR_GUEST_SECURE_TSC,
If this is specifically used for the AMD feature, as opposed to a generic "does your system have a secure TSC", then it should probably be CC_ATTR_GUEST_SNP_SECURE_TSC or CC_ATTR_GUEST_SEV_SNP_SECURE_TSC.
Thanks,
Tom
Quoted 17 lines
include/linux/cc_platform.h +0
-0};#ifdef CONFIG_ARCH_HAS_CC_PLATFORM arch/x86/coco/core.c +3
-0@@ -100,6 +100,9 @@ static bool noinstr amd_cc_platform_has(enum cc_attr attr)case CC_ATTR_HOST_SEV_SNP :return cc_flags.host_sev_snp; +case CC_ATTR_GUEST_SECURE_TSC : +return sev_status &MSR_AMD64_SNP_SECURE_TSC ; +default :return false; }
Re: [PATCH v11 13/20] x86/cc: Add CC_ATTR_GUEST_SECURE_TSC
Quoted 18 lines · Tom Lendacky
include/linux/cc_platform.h enum cc_attr { · line 98
Quoted 12 lines · Nikunj A Dadhania
include/linux/cc_platform.h +8
-0@@ -88,6 +88,14 @@ enum cc_attr {* enabled to run SEV-SNP guests. */ CC_ATTR_HOST_SEV_SNP , + +/** +* @CC_ATTR_GUEST_SECURE_TSC: Secure TSC is active. +* +* The platform/OS is running as a guest/virtual machine and actively +* using AMD SEV-SNP Secure TSC feature. +*/ + CC_ATTR_GUEST_SECURE_TSC,If this is specifically used for the AMD feature, as opposed to a generic "does your system have a secure TSC", then it should probably be
CC_ATTR_GUEST_SNP_SECURE_TSCorCC_ATTR_GUEST_SEV_SNP_SECURE_TSC.
Sure, let me rename it to CC_ATTR_GUEST_SNP_SECURE_TSC.
Regards
Nikunj
PATCH v11 14/20 x86/sev: Add Secure TSC support for SNP guests
In reply to Nikunj A DadhaniaAdd support for Secure TSC in SNP-enabled guests. Secure TSC allows guests to securely use RDTSC/RDTSCP instructions, ensuring that the parameters used cannot be altered by the hypervisor once the guest is launched.
Secure TSC-enabled guests need to query TSC information from the AMD Security Processor. This communication channel is encrypted between the AMD Security Processor and the guest, with the hypervisor acting merely as a conduit to deliver the guest messages to the AMD Security Processor. Each message is protected with AEAD (AES-256 GCM). Use a minimal AES GCM library to encrypt and decrypt SNP guest messages for communication with the PSP.
Use mem_encrypt_init() to fetch SNP TSC information from the AMD Security Processor and initialize snp_tsc_scale and snp_tsc_offset. During secondary CPU initialization, set the VMSA fields GUEST_TSC_SCALE (offset 2F0h) and GUEST_TSC_OFFSET (offset 2F8h) with snp_tsc_scale and snp_tsc_offset, respectively.
Since handle_guest_request() is common routine used by both the SEV guest driver and Secure TSC code, move it to the SEV header file.
--- arch/x86/include/asm/sev-common.h | 1 + arch/x86/include/asm/sev.h | 46 +++++++++++++ arch/x86/include/asm/svm.h | 6 +- arch/x86/coco/sev/core.c | 91 +++++++++++++++++++++++++ arch/x86/mm/mem_encrypt.c | 4 ++ drivers/virt/coco/sev-guest/sev-guest.c | 19 ------ 6 files changed, 146 insertions(+), 21 deletions(-)
arch/x86/include/asm/sev-common.h +1 -0
@@ -206,6 +206,7 @@ struct snp_psc_desc {#define GHCB_TERM_NO_SVSM 7/* SVSM is not advertised in the secrets page */ #define GHCB_TERM_SVSM_VMPL0 8/* SVSM is present but has set VMPL to 0 */ #define GHCB_TERM_SVSM_CAA 9/* SVSM is present but CAA is not page aligned */ +#define GHCB_TERM_SECURE_TSC 10/* Secure TSC initialization failed */ #define GHCB_RESP_CODE (v) ((v) & GHCB_MSR_INFO_MASK)
arch/x86/include/asm/sev.h +46 -0
70 lines not on this page · raw message
arch/x86/include/asm/svm.h +4 -2
@@ -417,7 +417,9 @@ struct sev_es_save_area {u8 reserved_0x298[80 ];u32 pkru;u32 tsc_aux; -u8 reserved_0x2f0[24 ]; +u64 tsc_scale; +u64 tsc_offset; +u8 reserved_0x300[8 ];u64 rcx;u64 rdx;u64 rbx;
@@ -549,7 +551,7 @@ static inline void __unused_size_checks(void)BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x1c0 );BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x248 );BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x298 ); -BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x2f0 ); +BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x300 );BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x320 );BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x380 );BUILD_BUG_RESERVED_OFFSET (sev_es_save_area,0x3f0 );
arch/x86/coco/sev/core.c +91 -0
106 lines not on this page · raw message
arch/x86/mm/mem_encrypt.c +4 -0
@@ -94,6 +94,10 @@ void __init mem_encrypt_init(void)/* Call into SWIOTLB to update the SWIOTLB DMA buffers */ swiotlb_update_mem_attributes (); +/* Initialize SNP Secure TSC */ +if (cc_platform_has (CC_ATTR_GUEST_SEV_SNP )) +snp_secure_tsc_prepare (); +print_mem_encrypt_feature_info (); }
drivers/virt/coco/sev-guest/sev-guest.c +0 -19
@@ -64,25 +64,6 @@ static inline struct snp_guest_dev *to_snp_dev(struct file *file) return container_of(dev, struct snp_guest_dev, misc); } -static int handle_guest_request (struct snp_msg_desc *mdesc,u64 exit_code, -struct snp_guest_request_ioctl *rio,u8 type, -void *req_buf,size_t req_sz,void *resp_buf, -u32 resp_sz) -{ -struct snp_guest_req req = { - .msg_version = rio->msg_version, - .msg_type = type, - .vmpck_id = mdesc->vmpck_id, - .req_buf = req_buf, - .req_sz = req_sz, - .resp_buf = resp_buf, - .resp_sz = resp_sz, - .exit_code = exit_code, - }; - -return snp_send_guest_request (mdesc, &req, rio); -} -struct snp_req_resp {sockptr_t req_data;sockptr_t resp_data;
Signature · 1 line
2.34.1
Re: [PATCH v11 14/20] x86/sev: Add Secure TSC support for SNP guests
Quoted 17 lines · Nikunj A Dadhania
Add support for Secure TSC in SNP-enabled guests. Secure TSC allows guests to securely use RDTSC/RDTSCP instructions, ensuring that the parameters used cannot be altered by the hypervisor once the guest is launched.
Secure TSC-enabled guests need to query TSC information from the AMD Security Processor. This communication channel is encrypted between the AMD Security Processor and the guest, with the hypervisor acting merely as a conduit to deliver the guest messages to the AMD Security Processor. Each message is protected with AEAD (AES-256 GCM). Use a minimal AES GCM library to encrypt and decrypt SNP guest messages for communication with the PSP.
Use
mem_encrypt_init()to fetch SNP TSC information from the AMD Security Processor and initializesnp_tsc_scaleandsnp_tsc_offset. During secondary CPU initialization, set the VMSA fieldsGUEST_TSC_SCALE(offset 2F0h) andGUEST_TSC_OFFSET(offset 2F8h) withsnp_tsc_scaleandsnp_tsc_offset, respectively.
Quoted 5 lines
Since
handle_guest_request()is common routine used by both the SEV guest driver and Secure TSC code, move it to the SEV header file.Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 9 lines
--- arch/x86/include/asm/sev-common.h | 1 + arch/x86/include/asm/sev.h | 46 +++++++++++++ arch/x86/include/asm/svm.h | 6 +- arch/x86/coco/sev/core.c | 91 +++++++++++++++++++++++++ arch/x86/mm/mem_encrypt.c | 4 ++ drivers/virt/coco/sev-guest/sev-guest.c | 19 ------ 6 files changed, 146 insertions(+), 21 deletions(-)
PATCH v11 15/20 x86/sev: Change TSC MSR behavior for Secure TSC enabled guests
In reply to Nikunj A DadhaniaSecure TSC enabled guests should not write to MSR_IA32_TSC(10H) register as the subsequent TSC value reads are undefined. MSR_IA32_TSC read/write accesses should not exit to the hypervisor for such guests.
Accesses to MSR_IA32_TSC needs special handling in the #VC handler for the guests with Secure TSC enabled. Writes to MSR_IA32_TSC should be ignored, and reads of MSR_IA32_TSC should return the result of the RDTSC instruction.
--- arch/x86/coco/sev/core.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
arch/x86/coco/sev/core.c +24 -0
@@ -1335,6 +1335,30 @@ static enum es_result vc_handle_msr(struct ghcb *ghcb, struct es_em_ctxt *ctxt)return ES_OK ; } +/* +* TSC related accesses should not exit to the hypervisor when a +* guest is executing with SecureTSC enabled, so special handling +* is required for accesses of MSR_IA32_TSC: +* +* Writes: Writing to MSR_IA32_TSC can cause subsequent reads +* of the TSC to return undefined values, so ignore all +* writes. +* Reads: Reads of MSR_IA32_TSC should return the current TSC +* value, use the value returned by RDTSC. +*/ +if (regs->cx ==MSR_IA32_TSC &&cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) { +u64 tsc; + +if (exit_info_1) +return ES_OK ; + + tsc =rdtsc (); + regs->ax =UINT_MAX & tsc; + regs->dx =UINT_MAX & (tsc >>32 ); + +return ES_OK ; + } +ghcb_set_rcx (ghcb, regs->cx);if (exit_info_1) {ghcb_set_rax (ghcb, regs->ax);
Signature · 1 line
2.34.1
PATCH v11 16/20 x86/sev: Prevent RDTSC/RDTSCP interception for Secure TSC enabled guests
In reply to Nikunj A DadhaniaThe hypervisor should not be intercepting RDTSC/RDTSCP when Secure TSC is enabled. A #VC exception will be generated if the RDTSC/RDTSCP instructions are being intercepted. If this should occur and Secure TSC is enabled, terminate guest execution.
--- arch/x86/coco/sev/shared.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
arch/x86/coco/sev/shared.c +10 -0
@@ -1140,6 +1140,16 @@ static enum es_result vc_handle_rdtsc(struct ghcb *ghcb,bool rdtscp = (exit_code ==SVM_EXIT_RDTSCP );enum es_result ret; +/* +* RDTSC and RDTSCP should not be intercepted when Secure TSC is +* enabled. Terminate the SNP guest when the interception is enabled. +* This file is included from kernel/sev.c and boot/compressed/sev.c, +* use sev_status here as cc_platform_has() is not available when +* compiling boot/compressed/sev.c. +*/ +if (sev_status &MSR_AMD64_SNP_SECURE_TSC ) +return ES_VMM_ERROR ; + ret =sev_es_ghcb_hv_call (ghcb, ctxt, exit_code,0 ,0 );if (ret !=ES_OK )return ret;
Signature · 1 line
2.34.1
Re: [PATCH v11 16/20] x86/sev: Prevent RDTSC/RDTSCP interception for Secure TSC enabled guests
Quoted 7 lines · Nikunj A Dadhania
The hypervisor should not be intercepting RDTSC/RDTSCP when Secure TSC is enabled. A #VC exception will be generated if the RDTSC/RDTSCP instructions are being intercepted. If this should occur and Secure TSC is enabled, terminate guest execution.
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 25 lines
--- arch/x86/coco/sev/shared.c | 10 ++++++++++ 1 file changed, 10 insertions(+)arch/x86/coco/sev/shared.c +10
-0@@ -1140,6 +1140,16 @@ static enum es_result vc_handle_rdtsc(struct ghcb *ghcb,bool rdtscp = (exit_code ==SVM_EXIT_RDTSCP );enum es_result ret; +/* +* RDTSC and RDTSCP should not be intercepted when Secure TSC is +* enabled. Terminate the SNP guest when the interception is enabled. +* This file is included from kernel/sev.c and boot/compressed/sev.c, +* use sev_status here as cc_platform_has() is not available when +* compiling boot/compressed/sev.c. +*/ +if (sev_status &MSR_AMD64_SNP_SECURE_TSC ) +return ES_VMM_ERROR ; + ret =sev_es_ghcb_hv_call (ghcb, ctxt, exit_code,0 ,0 );if (ret !=ES_OK )return ret;
PATCH v11 17/20 x86/sev: Allow Secure TSC feature for SNP guests
In reply to Nikunj A DadhaniaNow that all the required plumbing is done for enabling SNP Secure TSC feature, add Secure TSC to SNP features present list.
--- arch/x86/boot/compressed/sev.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/x86/boot/compressed/sev.c +2 -1
@@ -401,7 +401,8 @@ void do_boot_stage2_vc(struct pt_regs *regs, unsigned long exit_code)* by the guest kernel. As and when a new feature is implemented in the * guest kernel, a corresponding bit should be added to the mask. */ -#define SNP_FEATURES_PRESENT MSR_AMD64_SNP_DEBUG_SWAP +#define SNP_FEATURES_PRESENT (MSR_AMD64_SNP_DEBUG_SWAP | \ + MSR_AMD64_SNP_SECURE_TSC)u64 snp_get_unsupported_features (u64 status) {
Signature · 1 line
2.34.1
Re: [PATCH v11 17/20] x86/sev: Allow Secure TSC feature for SNP guests
Quoted 2 lines · Nikunj A Dadhania
Now that all the required plumbing is done for enabling SNP Secure TSC feature, add Secure TSC to SNP features present list.
So I think this should be the last patch in the series after the TSC is marked reliable, kvmclock is bypassed, etc. This way everything is in place when the guest is allowed to run with Secure TSC.
Quoted 3 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 18 lines
--- arch/x86/boot/compressed/sev.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)arch/x86/boot/compressed/sev.c +2
-1@@ -401,7 +401,8 @@ void do_boot_stage2_vc(struct pt_regs *regs, unsigned long exit_code)* by the guest kernel. As and when a new feature is implemented in the * guest kernel, a corresponding bit should be added to the mask. */ -#define SNP_FEATURES_PRESENT MSR_AMD64_SNP_DEBUG_SWAP +#define SNP_FEATURES_PRESENT (MSR_AMD64_SNP_DEBUG_SWAP | \ + MSR_AMD64_SNP_SECURE_TSC)u64 snp_get_unsupported_features (u64 status) {
Re: [PATCH v11 17/20] x86/sev: Allow Secure TSC feature for SNP guests
Quoted 7 lines · Tom Lendacky
Quoted 2 lines · Nikunj A Dadhania
Now that all the required plumbing is done for enabling SNP Secure TSC feature, add Secure TSC to SNP features present list.
So I think this should be the last patch in the series after the TSC is marked reliable, kvmclock is bypassed, etc. This way everything is in place when the guest is allowed to run with Secure TSC.
Sure, I can re-arrange that. I had re-arranged it in this order so the TSC related problems are visible after SecureTSC is enabled and fix them.
Quoted 6 lines
Quoted 4 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>Reviewed-by Tom Lendacky <[email protected]>
Regards
Nikunj
PATCH v11 18/20 x86/sev: Mark Secure TSC as reliable clocksource
In reply to Nikunj A DadhaniaIn SNP guest environment with Secure TSC enabled, unlike other clock sources (such as HPET, ACPI timer, APIC, etc.), the RDTSC instruction is handled without causing a VM exit, resulting in minimal overhead and jitters. Hence, mark Secure TSC as the only reliable clock source, bypassing unstable calibration.
--- arch/x86/mm/mem_encrypt_amd.c | 4 ++++ 1 file changed, 4 insertions(+)
arch/x86/mm/mem_encrypt_amd.c +4 -0
@@ -516,6 +516,10 @@ void __init sme_early_init(void)* kernel mapped. */ snp_update_svsm_ca (); + +/* Mark the TSC as reliable when Secure TSC is enabled */ +if (sev_status &MSR_AMD64_SNP_SECURE_TSC ) +setup_force_cpu_cap (X86_FEATURE_TSC_RELIABLE ); }void __init mem_encrypt_free_decrypted_mem (void )
Signature · 1 line
2.34.1
Re: [PATCH v11 18/20] x86/sev: Mark Secure TSC as reliable clocksource
Quoted 8 lines · Nikunj A Dadhania
In SNP guest environment with Secure TSC enabled, unlike other clock sources (such as HPET, ACPI timer, APIC, etc.), the RDTSC instruction is handled without causing a VM exit, resulting in minimal overhead and jitters. Hence, mark Secure TSC as the only reliable clock source, bypassing unstable calibration.
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 19 lines
--- arch/x86/mm/mem_encrypt_amd.c | 4 ++++ 1 file changed, 4 insertions(+)arch/x86/mm/mem_encrypt_amd.c +4
-0@@ -516,6 +516,10 @@ void __init sme_early_init(void)* kernel mapped. */ snp_update_svsm_ca (); + +/* Mark the TSC as reliable when Secure TSC is enabled */ +if (sev_status &MSR_AMD64_SNP_SECURE_TSC ) +setup_force_cpu_cap (X86_FEATURE_TSC_RELIABLE ); }void __init mem_encrypt_free_decrypted_mem (void )
PATCH v11 19/20 x86/kvmclock: Skip kvmclock when Secure TSC is available
In reply to Nikunj A DadhaniaFor AMD SNP guests with SecureTSC enabled, kvm-clock is being picked up momentarily instead of selecting more stable TSC clocksource.
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000001] kvm-clock: using sched offset of 1799357702246960 cycles [ 0.001493] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.006289] tsc: Detected 1996.249 MHz processor [ 0.305123] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.045759] clocksource: Switched to clocksource kvm-clock [ 1.141326] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.144634] clocksource: Switched to clocksource tsc
When Secure TSC is enabled, skip using the kvmclock. The guest kernel will fallback and use Secure TSC based clocksource.
--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kernel/kvmclock.c +1 -1
@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))return ;if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE2 )) {
Signature · 1 line
2.34.1
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 12 lines · Nikunj A Dadhania
For AMD SNP guests with SecureTSC enabled, kvm-clock is being picked up momentarily instead of selecting more stable TSC clocksource.
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000001] kvm-clock: using sched offset of 1799357702246960 cycles [ 0.001493] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.006289] tsc: Detected 1996.249 MHz processor [ 0.305123] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.045759] clocksource: Switched to clocksource kvm-clock [ 1.141326] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.144634] clocksource: Switched to clocksource tsc
Quoted 5 lines
When Secure TSC is enabled, skip using the kvmclock. The guest kernel will fallback and use Secure TSC based clocksource.
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 17 lines
--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))return ;if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE2 )) {
Sean Christopherson
maintainerRe: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
In reply to Nikunj A DadhaniaQuoted 26 lines · Nikunj A Dadhania
For AMD SNP guests with SecureTSC enabled, kvm-clock is being picked up momentarily instead of selecting more stable TSC clocksource.
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000001] kvm-clock: using sched offset of 1799357702246960 cycles [ 0.001493] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.006289] tsc: Detected 1996.249 MHz processor [ 0.305123] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.045759] clocksource: Switched to clocksource kvm-clock [ 1.141326] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.144634] clocksource: Switched to clocksource tscWhen Secure TSC is enabled, skip using the kvmclock. The guest kernel will fallback and use Secure TSC based clocksource.
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0
arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 5 lines
arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))
I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 6 lines
arch/x86/kernel/kvmclock.c +0
-0return ;if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE2 )) {Signature · 1 line
2.34.1
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 30 lines · Sean Christopherson
Quoted 29 lines · Nikunj A Dadhania
For AMD SNP guests with SecureTSC enabled, kvm-clock is being picked up momentarily instead of selecting more stable TSC clocksource.
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000001] kvm-clock: using sched offset of 1799357702246960 cycles [ 0.001493] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.006289] tsc: Detected 1996.249 MHz processor [ 0.305123] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.045759] clocksource: Switched to clocksource kvm-clock [ 1.141326] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns [ 1.144634] clocksource: Switched to clocksource tscWhen Secure TSC is enabled, skip using the kvmclock. The guest kernel will fallback and use Secure TSC based clocksource.
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags;
Quoted 10 lines
arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 2 lines
arch/x86/kernel/kvmclock.c +1
-1-if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
Regards
Nikunj
Sean Christopherson
maintainerRe: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 26 lines · Nikunj A. Dadhania
Quoted 14 lines · Sean Christopherson
Quoted 14 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags;Quoted 10 lines
arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 2 lines
arch/x86/kernel/kvmclock.c +1
-1-if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit 7539b174aef4 ("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to the kvm_sched_clock_init() code.
The other aspect of this to consider is wallclock. If I'm reading the code correctly, _completely_ disabling kvmclock will case the kernel to keep using the RTC for wallclock. Using the RTC is an amusingly bad decision for SNP and TDX (and regular VMs), as the RTC is a slooow emulation path and it's still very much controlled by the untrusted host.
Unless you have a better idea for what to do with wallclock, I think the right approach is to come up a cleaner way to prefer TSC over kvmclock for timekeeping and the scheduler, but leave wallclock as-is. And then for SNP and TDX, "assert" that the TSC is being used instead of kvmclock. Presumably, all SNP and TDX hosts provide a stable TSC, so there's probably no reason for the guest to even care if the TSC is "secure".
Note, past me missed the wallclock side of things[*], so I don't think hiding kvmclock entirely is the best solution.
[*] https://lore.kernel.org/all/ZOjF2DMBgW%[email protected]
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 27 lines · Sean Christopherson
Quoted 26 lines · Nikunj A. Dadhania
Quoted 24 lines · Sean Christopherson
Quoted 11 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 5 lines
arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.
The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
arch/x86/kernel/kvmclock.c +2 -2
@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SNP_SECURE_TSC )) +if (!kvm_para_available () || !kvmclock)return ;if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE2 )) {
@@ -342,7 +342,7 @@ void __init kvmclock_init(void)if (boot_cpu_has (X86_FEATURE_CONSTANT_TSC ) &&boot_cpu_has (X86_FEATURE_NONSTOP_TSC ) && !check_tsc_unstable ()) - kvm_clock.rating =299 ; + kvm_clock.rating =298 ;clocksource_register_hz (&kvm_clock,NSEC_PER_SEC ); pv_info.name ="KVM" ;
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00 [ 0.000001] kvm-clock: using sched offset of 6630881179920185 cycles [ 0.001266] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [ 0.005347] tsc: Detected 1996.247 MHz processor [ 0.263100] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398caa9ddcb, max_idle_ns: 881590739785 ns [ 0.980456] clocksource: Switched to clocksource tsc-early [ 1.059332] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398caa9ddcb, max_idle_ns: 881590739785 ns [ 1.062094] clocksource: Switched to clocksource tsc
Quoted 5 lines
The other aspect of this to consider is wallclock. If I'm reading the code correctly, _completely_ disabling kvmclock will case the kernel to keep using the RTC for wallclock. Using the RTC is an amusingly bad decision for SNP and TDX (and regular VMs), as the RTC is a slooow emulation path and it's still very much controlled by the untrusted host.
Right, this is not expected.
Quoted 11 lines
Unless you have a better idea for what to do with wallclock, I think the right approach is to come up a cleaner way to prefer TSC over kvmclock for timekeeping and the scheduler, but leave wallclock as-is. And then for SNP and TDX, "assert" that the TSC is being used instead of kvmclock. Presumably, all SNP and TDX hosts provide a stable TSC, so there's probably no reason for the guest to even care if the TSC is "secure".
Note, past me missed the wallclock side of things[*], so I don't think hiding kvmclock entirely is the best solution.
[*] https://lore.kernel.org/all/ZOjF2DMBgW%[email protected]
Regards
Nikunj
Sean Christopherson
maintainerRe: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 37 lines · Nikunj A. Dadhania
Quoted 27 lines · Sean Christopherson
Quoted 26 lines · Nikunj A. Dadhania
Quoted 24 lines · Sean Christopherson
Quoted 11 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 5 lines
arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.
Quoted 5 lines
The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
IMO, it's ugly, but that's a problem with the rating system inasmuch as anything.
But the kernel will still be using kvmclock for the scheduler clock, which is undesirable.
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 41 lines · Sean Christopherson
Quoted 40 lines · Nikunj A. Dadhania
Quoted 27 lines · Sean Christopherson
Quoted 26 lines · Nikunj A. Dadhania
Quoted 24 lines · Sean Christopherson
Quoted 11 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 5 lines
arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Quoted 7 lines
Quoted 2 lines
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
IMO, it's ugly, but that's a problem with the rating system inasmuch as anything.
But the kernel will still be using kvmclock for the scheduler clock, which is undesirable.
Agree, kvm_sched_clock_init() is still being called. The above hunk was to use tsc-early/tsc as the clocksource and not kvm-clock.
Regards,
Nikunj
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 45 lines · Nikunj A. Dadhania
Quoted 44 lines · Sean Christopherson
Quoted 42 lines · Nikunj A. Dadhania
Quoted 27 lines · Sean Christopherson
Quoted 26 lines · Nikunj A. Dadhania
Quoted 24 lines · Sean Christopherson
Quoted 11 lines
Signed-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/kvmclock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)arch/x86/kernel/kvmclock.c +0
-0arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 292
Quoted 5 lines
arch/x86/kernel/kvmclock.c +1
-1@@ -289,7 +289,7 @@ void __init kvmclock_init(void) {u8 flags; -if (!kvm_para_available () || !kvmclock) +if (!kvm_para_available () || !kvmclock ||cc_platform_has (CC_ATTR_GUEST_SECURE_TSC ))I would much prefer we solve the kvmclock vs. TSC fight in a generic way. Unless I've missed something, the fact that the TSC is more trusted in the SNP/TDX world is simply what's forcing the issue, but it's not actually the reason why Linux should prefer the TSC over kvmclock. The underlying reason is that platforms that support SNP/TDX are guaranteed to have a stable, always running TSC, i.e. that the TSC is a superior timesource purely from a functionality perspective. That it's more secure is icing on the cake.
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
Quoted 7 lines
Quoted 4 lines
IMO, it's ugly, but that's a problem with the rating system inasmuch as anything.
But the kernel will still be using kvmclock for the scheduler clock, which is undesirable.
Agree,
kvm_sched_clock_init()is still being called. The above hunk was to use tsc-early/tsc as the clocksource and not kvm-clock.
How about the below patch:
From: Nikunj A Dadhania <[email protected]>
Date: Tue, 28 Nov 2023 18:29:56 +0530
Subject: [RFC PATCH] x86/kvmclock: Prefer invariant TSC as the clocksource and
scheduler clock
For platforms that support stable and always running TSC, although the kvm-clock rating is dropped to 299 to prefer TSC, the guest scheduler clock still keeps on using the kvm-clock which is undesirable. Moreover, as the kvm-clock and early-tsc clocksource are both registered with 299 rating, kvm-clock is being picked up momentarily instead of selecting more stable tsc-early clocksource.
kvm-clock: Using msrs 4b564d01 and 4b564d00
kvm-clock: using sched offset of 1799357702246960 cycles
clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
tsc: Detected 1996.249 MHz processor
clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource kvm-clock
clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x398cadd9d93, max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource tsc
Drop the kvm-clock rating to 298, so that tsc-early is picked up before kvm-clock and use TSC for scheduler clock as well when the TSC is invariant and stable.
---
The issue we see here is that on bare-metal if the TSC is marked unstable, then the sched-clock will fall back to jiffies. In the virtualization case, do we want to fall back to kvm-clock when TSC is marked unstable?
--- arch/x86/kernel/kvmclock.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)
arch/x86/kernel/kvmclock.c +6 -5
@@ -317,9 +317,6 @@ void __init kvmclock_init(void)if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE_STABLE_BIT ))pvclock_set_flags (PVCLOCK_TSC_STABLE_BIT ); - flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); -kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); - x86_platform.calibrate_tsc = kvm_get_tsc_khz; x86_platform.calibrate_cpu = kvm_get_tsc_khz; x86_platform.get_wallclock = kvm_get_wallclock;
@@ -341,8 +338,12 @@ void __init kvmclock_init(void)*/ if (boot_cpu_has (X86_FEATURE_CONSTANT_TSC ) &&boot_cpu_has (X86_FEATURE_NONSTOP_TSC ) && - !check_tsc_unstable ()) - kvm_clock.rating =299 ; + !check_tsc_unstable ()) { + kvm_clock.rating =298 ; + }else { + flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); +kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); + }clocksource_register_hz (&kvm_clock,NSEC_PER_SEC ); pv_info.name ="KVM" ;
Signature · 1 line
2.34.1
Sean Christopherson
maintainerRe: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 50 lines · Nikunj A. Dadhania
Quoted 15 lines
Quoted 15 lines
Quoted 14 lines
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
Quoted 7 lines
Quoted 4 lines
IMO, it's ugly, but that's a problem with the rating system inasmuch as anything.
But the kernel will still be using kvmclock for the scheduler clock, which is undesirable.
Agree,
kvm_sched_clock_init()is still being called. The above hunk was to use tsc-early/tsc as the clocksource and not kvm-clock.How about the below patch:
From: Nikunj A Dadhania <[email protected]>
Date: Tue, 28 Nov 2023 18:29:56 +0530
Subject: [RFC PATCH] x86/kvmclock: Prefer invariant TSC as the clocksource and
scheduler clockFor platforms that support stable and always running TSC, although the kvm-clock rating is dropped to 299 to prefer TSC, the guest scheduler clock still keeps on using the kvm-clock which is undesirable. Moreover, as the kvm-clock and early-tsc clocksource are both registered with 299 rating, kvm-clock is being picked up momentarily instead of selecting more stable tsc-early clocksource.
kvm-clock: Using msrs
4b564d01and4b564d00
kvm-clock: using sched offset of 1799357702246960 cycles
clocksource: kvm-clock: mask:0xffffffffffffffffmax_cycles:0x1cd42e4dffb,max_idle_ns: 881590591483 ns
tsc: Detected 1996.249 MHz processor
clocksource: tsc-early: mask:0xffffffffffffffffmax_cycles:0x398cadd9d93,max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource kvm-clock
clocksource: tsc: mask:0xffffffffffffffffmax_cycles:0x398cadd9d93,max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource tscDrop the kvm-clock rating to 298, so that tsc-early is picked up before kvm-clock and use TSC for scheduler clock as well when the TSC is invariant and stable.
Quoted 7 lines
Signed-off-by Nikunj A Dadhania <[email protected]>---
The issue we see here is that on bare-metal if the TSC is marked unstable, then the sched-clock will fall back to jiffies. In the virtualization case, do we want to fall back to kvm-clock when TSC is marked unstable?
In the general case, yes. Though that might be a WARN-able offense if the TSC is allegedly constant+nonstop. And for SNP and TDX, it might be a "panic and do not boot" offense, since using kvmclock undermines the security of the guest.
Quoted 20 lines
--- arch/x86/kernel/kvmclock.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)arch/x86/kernel/kvmclock.c +0
-3@@ -317,9 +317,6 @@ void __init kvmclock_init(void)if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE_STABLE_BIT ))pvclock_set_flags (PVCLOCK_TSC_STABLE_BIT ); - flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); -kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); - x86_platform.calibrate_tsc = kvm_get_tsc_khz; x86_platform.calibrate_cpu = kvm_get_tsc_khz; x86_platform.get_wallclock = kvm_get_wallclock;@@ -341,8 +338,12 @@ void __init kvmclock_init(void)*/
arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 346
Quoted 10 lines
arch/x86/kernel/kvmclock.c +6
-2if (boot_cpu_has (X86_FEATURE_CONSTANT_TSC ) &&boot_cpu_has (X86_FEATURE_NONSTOP_TSC ) && - !check_tsc_unstable ()) - kvm_clock.rating =299 ; + !check_tsc_unstable ()) { + kvm_clock.rating =298 ; + }else { + flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); +kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); + }
I would really, really like to fix this in a centralized location, not by having each PV clocksource muck with their clock's rating. I'm not even sure the existing code is entirely correct, as kvmclock_init() runs _before_ tsc_early_init(). Which is desirable in the legacy case, as it allows calibrating the TSC using kvmclock,
x86_platform.calibrate_tsc = kvm_get_tsc_khz;
but on modern setups that's definitely undesirable, as it means the kernel won't use CPUID.0x15, which every explicitly tells software the frequency of the TSC.
And I don't think we want to simply point at native_calibrate_tsc(), because that thing is not at all correct for a VM, where checking x86_vendor and x86_vfm is at best sketchy. E.g. I would think it's in AMD's interest for Secure TSC to define the TSC frequency using CPUID.0x15, even if AMD CPUs don't (yet) natively support CPUID.0x15.
In other words, I think we need to overhaul the PV clock vs. TSC logic so that it makes sense for modern CPUs+VMs, not just keep hacking away at kvmclock. I don't expect the code would be all that complex in the end, the hardest part is likely just figuring out (and agreeing on) what exactly the kernel should be doing.
Quoted 5 lines
arch/x86/kernel/kvmclock.c +0
-0clocksource_register_hz (&kvm_clock,NSEC_PER_SEC ); pv_info.name ="KVM" ;Signature · 1 line
2.34.1
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 88 lines · Sean Christopherson
Quoted 50 lines · Nikunj A. Dadhania
Quoted 15 lines
Quoted 15 lines
Quoted 14 lines
Quoted 8 lines
Quoted 2 lines
Are you suggesting that whenever the guest is either SNP or TDX, kvmclock should be disabled assuming that timesource is stable and always running?
No, I'm saying that the guest should prefer the raw TSC over kvmclock if the TSC is stable, irrespective of SNP or TDX. This is effectively already done for the timekeeping base (see commit
7539b174aef4("x86: kvmguest: use TSC clocksource if invariant TSC is exposed")), but the scheduler still uses kvmclock thanks to thekvm_sched_clock_init()code.The kvm-clock and tsc-early both are having the rating of 299. As they are of same rating, kvm-clock is being picked up first.
Is it fine to drop the clock rating of kvmclock to 298 ? With this tsc-early will be picked up instead.
Quoted 7 lines
Quoted 4 lines
IMO, it's ugly, but that's a problem with the rating system inasmuch as anything.
But the kernel will still be using kvmclock for the scheduler clock, which is undesirable.
Agree,
kvm_sched_clock_init()is still being called. The above hunk was to use tsc-early/tsc as the clocksource and not kvm-clock.How about the below patch:
From: Nikunj A Dadhania <[email protected]>
Date: Tue, 28 Nov 2023 18:29:56 +0530
Subject: [RFC PATCH] x86/kvmclock: Prefer invariant TSC as the clocksource and
scheduler clockFor platforms that support stable and always running TSC, although the kvm-clock rating is dropped to 299 to prefer TSC, the guest scheduler clock still keeps on using the kvm-clock which is undesirable. Moreover, as the kvm-clock and early-tsc clocksource are both registered with 299 rating, kvm-clock is being picked up momentarily instead of selecting more stable tsc-early clocksource.
kvm-clock: Using msrs
4b564d01and4b564d00
kvm-clock: using sched offset of 1799357702246960 cycles
clocksource: kvm-clock: mask:0xffffffffffffffffmax_cycles:0x1cd42e4dffb,max_idle_ns: 881590591483 ns
tsc: Detected 1996.249 MHz processor
clocksource: tsc-early: mask:0xffffffffffffffffmax_cycles:0x398cadd9d93,max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource kvm-clock
clocksource: tsc: mask:0xffffffffffffffffmax_cycles:0x398cadd9d93,max_idle_ns: 881590552906 ns
clocksource: Switched to clocksource tscDrop the kvm-clock rating to 298, so that tsc-early is picked up before kvm-clock and use TSC for scheduler clock as well when the TSC is invariant and stable.
Quoted 7 lines
Signed-off-by Nikunj A Dadhania <[email protected]>---
The issue we see here is that on bare-metal if the TSC is marked unstable, then the sched-clock will fall back to jiffies. In the virtualization case, do we want to fall back to kvm-clock when TSC is marked unstable?
In the general case, yes. Though that might be a WARN-able offense if the TSC is allegedly constant+nonstop. And for SNP and TDX, it might be a "panic and do not boot" offense, since using kvmclock undermines the security of the guest.
Quoted 25 lines
--- arch/x86/kernel/kvmclock.c | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)arch/x86/kernel/kvmclock.c +1
-5@@ -317,9 +317,6 @@ void __init kvmclock_init(void)if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE_STABLE_BIT ))pvclock_set_flags (PVCLOCK_TSC_STABLE_BIT ); - flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); -kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); - x86_platform.calibrate_tsc = kvm_get_tsc_khz; x86_platform.calibrate_cpu = kvm_get_tsc_khz; x86_platform.get_wallclock = kvm_get_wallclock;@@ -341,8 +338,12 @@ void __init kvmclock_init(void)*/ if (boot_cpu_has (X86_FEATURE_CONSTANT_TSC ) &&boot_cpu_has (X86_FEATURE_NONSTOP_TSC ) && - !check_tsc_unstable ()) - kvm_clock.rating =299 ; + !check_tsc_unstable ()) {
Quoted 8 lines
arch/x86/kernel/kvmclock.c void __init kvmclock_init(void) · line 346
Quoted 5 lines
arch/x86/kernel/kvmclock.c +5
-0+ kvm_clock.rating =298 ; + }else { + flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); +kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); + }I would really, really like to fix this in a centralized location, not by having each PV clocksource muck with their clock's rating.
TSC Clock Rating Adjustment:
* During TSC initialization, downgrade the TSC clock rating to 200 if TSC is not constant/reliable, placing it below HPET.
* Ensure the kvm-clock rating is set to 299 by default in the struct clocksource kvm_clock.
* Avoid changing the kvm clock rating based on the availability of reliable clock sources. Let the TSC clock source determine and downgrade itself.
The above will make sure that the PV clocksource rating remain unaffected.
Clock soure selection order when the ratings match:
* Currently, clocks are registered and enqueued based on their rating.
* When clock ratings are tied, use the advertised clock frequency(freq_khz) as a secondary key to favor clocks with better frequency.
This approach improves the selection process by considering both rating and frequency. Something like below:
kernel/time/clocksource.c +6 -0
@@ -1098,6 +1098,9 @@ static void clocksource_enqueue(struct clocksource *cs)/* Keep track of the place, where to insert */ if (tmp->rating < cs->rating)break ; +if (tmp->rating == cs->rating && tmp->freq_khz < cs->freq_khz) +break ; + entry = &tmp->list; }list_add (&cs->list, entry);
@@ -1133,6 +1136,9 @@ void __clocksource_update_freq_scale(struct clocksource *cs, u32 scale, u32 freq* clocksource with mask >= 40-bit and f >= 4GHz. That maps to * ~ 0.06ppm granularity for NTP. */ + + cs->freq_khz = freq * scale /1000 ; + sec = cs->mask;do_div (sec, freq);do_div (sec, scale);
Quoted 9 lines
I'm not even sure the existing
code is entirely correct, askvmclock_init()runs _before_tsc_early_init(). Which is desirable in the legacy case, as it allows calibrating the TSC using kvmclock,x86_platform.calibrate_tsc = kvm_get_tsc_khz;but on modern setups that's definitely undesirable, as it means the kernel won't use CPUID.0x15, which every explicitly tells software the frequency of the TSC.
Quoted 7 lines
And I don't think we want to simply point at
native_calibrate_tsc(), because that thing is not at all correct for a VM, where checkingx86_vendorandx86_vfmis at best sketchy.E.g. I would think it's in AMD's interest for Secure TSC to define the TSC frequency using CPUID.0x15, even if AMD CPUs don't (yet) natively support CPUID.0x15.
For SecureTSC: GUEST_TSC_FREQ MSR (C001_0134h) provides the TSC frequency.
Quoted 4 lines
In other words, I think we need to overhaul the PV clock vs. TSC logic so that it makes sense for modern CPUs+VMs, not just keep hacking away at kvmclock. I don't expect the code would be all that complex in the end, the hardest part is likely just figuring out (and agreeing on) what exactly the kernel should be doing.
To summarise this thread with respect to TSC vs KVM clock, there three key questions:
1) When should kvmclock init be done?
2) How should the TSC frequency be discovered?
3) What should be the sched clock source and how should it be selected in a generic way?
○ Legacy CPU/VMs: VMs running on platforms without non-stop/constant TSC
+ kvm-clock should be registered before tsc-early/tsc
+ Need to calibrate TSC frequency
+ Use kvmclock wallclock
+ Use kvmclock for sched clock selected dynamicaly
(using clocksource enable()/disable() callback)
○ Modern CPU/VMs: VMs running on platforms supporting constant, non-stop and reliable TSC
+ kvm-clock should be registered before tsc-early/tsc
+ TSC Frequency:
Intel: TSC frequency using CPUID 0x15H/ 0x16H ?
For SecureTSC: GUEST_TSC_FREQ MSR (C001_0134h) provides the TSC frequency, other AMD guests need to calibrate the TSC frequency.
+ Use kvmclock wallclock
+ Use TSC for sched clock
After reviewing the code, the current init sequence looks correct for both legacy and modern VMs/CPUs. Let kvmclock go ahead and register itself as a clocksource, although registration of the sched clock can be deferred until the kvm-clock is picked up as the clock source. And restore the old sched clock when kvmclock is disabled. Something like the below patch, lightly tested:
arch/x86/kernel/kvmclock.c +31 -5
@@ -21,6 +21,7 @@#include <asm/hypervisor.h> #include <asm/x86_init.h> #include <asm/kvmclock.h> +#include <asm/timer.h> static int kvmclock__initdata =1 ;static int kvmclock_vsyscall__initdata =1 ;
@@ -148,12 +149,41 @@ bool kvm_check_and_clear_guest_paused(void)return ret; } +static u64 (*old_pv_sched_clock)(void ); + +static void enable_kvm_schedclock_work (struct work_struct *work) +{ +u8 flags; + + old_pv_sched_clock =static_call_query (pv_sched_clock); + flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); +kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); +} + +static DECLARE_DELAYED_WORK(enable_kvm_sc, enable_kvm_schedclock_work); + +static void disable_kvm_schedclock_work (struct work_struct *work) +{ +if (old_pv_sched_clock) +paravirt_set_sched_clock (old_pv_sched_clock); +} +static DECLARE_DELAYED_WORK(disable_kvm_sc, disable_kvm_schedclock_work); +static int kvm_cs_enable (struct clocksource *cs) { +u8 flags; +vclocks_set_used (VDSO_CLOCKMODE_PVCLOCK ); +schedule_delayed_work (&enable_kvm_sc,0 ); +return 0 ; } +static void kvm_cs_disable (struct clocksource *cs) +{ +schedule_delayed_work (&disable_kvm_sc,0 ); +} +static struct clocksource kvm_clock = { .name ="kvm-clock" , .read = kvm_clock_get_cycles,
@@ -162,6 +192,7 @@ static struct clocksource kvm_clock = { .flags = CLOCK_SOURCE_IS_CONTINUOUS, .id = CSID_X86_KVM_CLK, .enable = kvm_cs_enable, + .disable = kvm_cs_disable, };static void kvm_register_clock (char *txt)
@@ -287,8 +318,6 @@ static int kvmclock_setup_percpu(unsigned int cpu)void __init kvmclock_init (void ) { -u8 flags; -if (!kvm_para_available () || !kvmclock)return ;
@@ -317,9 +346,6 @@ void __init kvmclock_init(void)if (kvm_para_has_feature (KVM_FEATURE_CLOCKSOURCE_STABLE_BIT ))pvclock_set_flags (PVCLOCK_TSC_STABLE_BIT ); - flags =pvclock_read_flags (&hv_clock_boot[0 ].pvti); -kvm_sched_clock_init (flags &PVCLOCK_TSC_STABLE_BIT ); - x86_platform.calibrate_tsc = kvm_get_tsc_khz; x86_platform.calibrate_cpu = kvm_get_tsc_khz; x86_platform.get_wallclock = kvm_get_wallclock;
Regards
Nikunj
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 3 lines · Nikunj A. Dadhania
TSC Clock Rating Adjustment:
* During TSC initialization, downgrade the TSC clock rating to 200 if TSC is not constant/reliable, placing it below HPET.
Downgrading a constant TSC is a bad idea. Reliable just means that it does not need a watchdog clocksource. If it's non-constant it's downgraded anyway.
Quoted 4 lines
* Ensure the kvm-clock rating is set to 299 by default in the struct clocksource
kvm_clock.
* Avoid changing the kvm clock rating based on the availability of reliable clock sources. Let the TSC clock source determine and downgrade itself.
Why downgrade? If it's the best one you want to upgrade it so it's preferred over the others.
Quoted 10 lines
The above will make sure that the PV clocksource rating remain unaffected.
Clock soure selection order when the ratings match:
* Currently, clocks are registered and enqueued based on their rating.
* When clock ratings are tied, use the advertised clockfrequency(freq_khz)as a secondary key to favor clocks with better frequency.This approach improves the selection process by considering both rating and frequency. Something like below:
What does the frequency tell us? Not really anything. It's not necessarily the better clocksource.
Higher frequency gives you a slightly better resolution, but as all of this is usually sub-nanosecond resolution already that's not making a difference in practice.
So if you know you want TSC to be selected, then upgrade the rating of both the early and the regular TSC clocksource and be done with it.
Thanks,
tglx
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 9 lines · Thomas Gleixner
Quoted 3 lines · Nikunj A. Dadhania
TSC Clock Rating Adjustment:
* During TSC initialization, downgrade the TSC clock rating to 200 if TSC is not constant/reliable, placing it below HPET.Downgrading a constant TSC is a bad idea. Reliable just means that it does not need a watchdog clocksource. If it's non-constant it's downgraded anyway.
Quoted 7 lines
Quoted 4 lines
* Ensure the kvm-clock rating is set to 299 by default in the struct clocksource
kvm_clock.
* Avoid changing the kvm clock rating based on the availability of reliable clock sources. Let the TSC clock source determine and downgrade itself.Why downgrade? If it's the best one you want to upgrade it so it's preferred over the others.
Thanks for confirming that upgrading the TSC rating is fine.
Quoted 14 lines
The above will make sure that the PV clocksource rating remain
Quoted 9 lines
unaffected.
Clock soure selection order when the ratings match:
* Currently, clocks are registered and enqueued based on their rating.
* When clock ratings are tied, use the advertised clockfrequency(freq_khz)as a secondary key to favor clocks with better frequency.This approach improves the selection process by considering both rating and frequency. Something like below:
What does the frequency tell us? Not really anything. It's not necessarily the better clocksource.
Quoted 6 lines
Higher frequency gives you a slightly better resolution, but as all of this is usually sub-nanosecond resolution already that's not making a difference in practice.
So if you know you want TSC to be selected, then upgrade the rating of both the early and the regular TSC clocksource and be done with it.
Sure Thomas, I will modify the patch accordingly and send an RFC.
Also I realized that, for the guests, instead of rdtsc(), we should be calling rdtsc_ordered() to make sure that time moves forward even when vCPUs are migrated.
Thanks,
Nikunj
Re: [PATCH v11 19/20] x86/kvmclock: Skip kvmclock when Secure TSC is available
Quoted 3 lines · Nikunj A. Dadhania
Also I realized that, for the guests, instead of
rdtsc(), we should be callingrdtsc_ordered()to make sure that time moves forward even when vCPUs are migrated.
The above is with reference to native_sched_clock() being used for VM instead of kvm_sched_clock_read() when using TSC.
Regards
Nikunj
PATCH v11 20/20 x86/cpu/amd: Do not print FW_BUG for Secure TSC
In reply to Nikunj A DadhaniaWhen Secure TSC is enabled and TscInvariant (bit 8) in CPUID_8000_0007_edx is set, the kernel complains with the below firmware bug:
[Firmware Bug]: TSC doesn't count with P0 frequency!
Secure TSC does not need to run at P0 frequency; the TSC frequency is set by the VMM as part of the SNP_LAUNCH_START command. Skip this check when Secure TSC is enabled
--- arch/x86/kernel/cpu/amd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/amd.c +2 -1
@@ -370,7 +370,8 @@ static void bsp_determine_snp(struct cpuinfo_x86 *c)static void bsp_init_amd (struct cpuinfo_x86 *c) { -if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) {if (c->x86 >0x10 || (c->x86 ==0x10 && c->x86_model >=0x2 )) {
Signature · 1 line
2.34.1
Re: [PATCH v11 20/20] x86/cpu/amd: Do not print FW_BUG for Secure TSC
Quoted 11 lines · Nikunj A Dadhania
When Secure TSC is enabled and TscInvariant (bit 8) in
CPUID_8000_0007_edxis set, the kernel complains with the below firmware bug:[Firmware Bug]: TSC doesn't count with P0 frequency!
Secure TSC does not need to run at P0 frequency; the TSC frequency is set by the VMM as part of the
SNP_LAUNCH_STARTcommand. Skip this check when Secure TSC is enabledSigned-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>
Quoted 18 lines
--- arch/x86/kernel/cpu/amd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)arch/x86/kernel/cpu/amd.c +2
-1@@ -370,7 +370,8 @@ static void bsp_determine_snp(struct cpuinfo_x86 *c)static void bsp_init_amd (struct cpuinfo_x86 *c) { -if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) {if (c->x86 >0x10 || (c->x86 ==0x10 && c->x86_model >=0x2 )) {
Re: [PATCH v11 20/20] x86/cpu/amd: Do not print FW_BUG for Secure TSC
In reply to Nikunj A DadhaniaQuoted 21 lines · Nikunj A Dadhania
When Secure TSC is enabled and TscInvariant (bit 8) in
CPUID_8000_0007_edxis set, the kernel complains with the below firmware bug:[Firmware Bug]: TSC doesn't count with P0 frequency!
Secure TSC does not need to run at P0 frequency; the TSC frequency is set by the VMM as part of the
SNP_LAUNCH_STARTcommand. Skip this check when Secure TSC is enabledSigned-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/cpu/amd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)arch/x86/kernel/cpu/amd.c +0
-0
arch/x86/kernel/cpu/amd.c static void bsp_determine_snp(struct cpuinfo_x86 *c) · line 374
Quoted 6 lines
arch/x86/kernel/cpu/amd.c +2
-1@@ -370,7 +370,8 @@ static void bsp_determine_snp(struct cpuinfo_x86 *c)static void bsp_init_amd (struct cpuinfo_x86 *c) { -if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) {
Could we extend this to never complain in a virtual machine? i.e.
...
- if (cpu_has(c, X86_FEATURE_CONSTANT_TSC)) {
+ if (cpu_has(c, X86_FEATURE_CONSTANT_TSC) &&
+ !cpu_has(c, X86_FEATURE_HYPERVISOR)) {
...
Re: [PATCH v11 20/20] x86/cpu/amd: Do not print FW_BUG for Secure TSC
Quoted 23 lines · Jim Mattson
Quoted 22 lines · Nikunj A Dadhania
When Secure TSC is enabled and TscInvariant (bit 8) in
CPUID_8000_0007_edxis set, the kernel complains with the below firmware bug:[Firmware Bug]: TSC doesn't count with P0 frequency!
Secure TSC does not need to run at P0 frequency; the TSC frequency is set by the VMM as part of the
SNP_LAUNCH_STARTcommand. Skip this check when Secure TSC is enabledSigned-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/cpu/amd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)arch/x86/kernel/cpu/amd.c +0
-0@@ -370,7 +370,8 @@ static void bsp_determine_snp(struct cpuinfo_x86 *c)
Quoted 7 lines
arch/x86/kernel/cpu/amd.c static void bsp_determine_snp(struct cpuinfo_x86 *c) · line 374
Quoted 5 lines
arch/x86/kernel/cpu/amd.c +2
-1static void bsp_init_amd (struct cpuinfo_x86 *c) { -if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) {Could we extend this to never complain in a virtual machine? i.e.
Let me get more clarity on the below and your commit[1]
arch/x86/kernel/cpu/amd.c static void bsp_determine_snp(struct cpuinfo_x86 *c)
Quoted 5 lines
...
arch/x86/kernel/cpu/amd.c +2
-1-if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cpu_has (c,X86_FEATURE_HYPERVISOR )) {
Or do this for Family 15h and above ?
Regards
Nikunj
Re: [PATCH v11 20/20] x86/cpu/amd: Do not print FW_BUG for Secure TSC
Quoted 37 lines · Nikunj A. Dadhania
Quoted 23 lines · Jim Mattson
Quoted 22 lines · Nikunj A Dadhania
When Secure TSC is enabled and TscInvariant (bit 8) in
CPUID_8000_0007_edxis set, the kernel complains with the below firmware bug:[Firmware Bug]: TSC doesn't count with P0 frequency!
Secure TSC does not need to run at P0 frequency; the TSC frequency is set by the VMM as part of the
SNP_LAUNCH_STARTcommand. Skip this check when Secure TSC is enabledSigned-off-by Nikunj A Dadhania <[email protected]>Tested-by Peter Gonda <[email protected]>--- arch/x86/kernel/cpu/amd.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)arch/x86/kernel/cpu/amd.c +0
-0@@ -370,7 +370,8 @@ static void bsp_determine_snp(struct cpuinfo_x86 *c)Quoted 7 lines
arch/x86/kernel/cpu/amd.c static void bsp_determine_snp(struct cpuinfo_x86 *c) · line 374
Quoted 5 lines
arch/x86/kernel/cpu/amd.c +2
-1static void bsp_init_amd (struct cpuinfo_x86 *c) { -if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cc_platform_has (CC_ATTR_GUEST_SECURE_TSC )) {Could we extend this to never complain in a virtual machine? i.e.
Let me get more clarity on the below and your commit[1]
Quoted 7 lines
arch/x86/kernel/cpu/amd.c static void bsp_determine_snp(struct cpuinfo_x86 *c)
Quoted 5 lines
...
arch/x86/kernel/cpu/amd.c +2
-1-if (cpu_has (c,X86_FEATURE_CONSTANT_TSC )) { +if (cpu_has (c,X86_FEATURE_CONSTANT_TSC ) && + !cpu_has (c,X86_FEATURE_HYPERVISOR )) {Or do this for Family 15h and above ?
I don't think there exists a virtual firmware that sets this bit on older CPU families. In fact, before my referenced commit, it wasn't possible.
Quoted 4 lines
Regards
Nikunj
Something like this is necessary for existing versions of Linux. I would like to have set HW_CR.TscFreqSel[bit 24] at VCPU creation, but Sean would not let me. So, now userspace has to do it right after VCPU creation. I don't have any intention of adding the code to qemu, but maybe someone will.
Quoted 51 lines · Nikunj A Dadhania
This patchset is also available at:
https://github.com/AMDESE/linux-kvm/tree/sectsc-guest-latest
and is based on v6.11-rc1
Overview
--------Secure TSC allows guests to securely use RDTSC/RDTSCP instructions as the parameters being used cannot be changed by hypervisor once the guest is launched. More details in the AMD64 APM Vol 2, Section "Secure TSC".
In order to enable secure TSC, SEV-SNP guests need to send
TSC_INFOguest message before the APs are booted. Details from theTSC_INFOresponse will then be used to program the VMSA before the APs are brought up. See "SEV Secure Nested Paging Firmware ABI Specification" document (currently at
https://www.amd.com/system/files/TechDocs/56860.pdf) section "TSC Info"SEV-guest driver has the implementation for guest and AMD Security Processor communication. As the
TSC_INFOneeds to be initialized during early boot before APs are started, move the guest messaging code from sev-guest driver tosev/core.cand provide well defined APIs to the sev-guest driver.Patches:
01-04: sev-guest driver cleanup and enhancements
05: Use AES GCM library
06-07: SNP init error handling and cache secrets page address 08-10: Preparatory patches for code movement
11-12: Patches moving SNP guest messaging code from SEV guest driver to
SEV common code
13-20: SecureTSC enablement patches.Testing SecureTSC
-----------------SecureTSC hypervisor patches based on top of SEV-SNP Guest MEMFD series:
https://github.com/AMDESE/linux-kvm/tree/sectsc-host-latestQEMU changes:
https://github.com/nikunjad/qemu/tree/snp-securetsc-latestQEMU commandline SEV-SNP with SecureTSC:
qemu-system-x86_64 -cpu EPYC-Milan-v2 -smp 4 \ -object memory-backend-memfd,id=ram1,size=1G,share=true,prealloc=false,reserve=false \ -object sev-snp-guest,id=sev0,cbitpos=51,reduced-phys-bits=1,secure-tsc=on \ -machine q35,confidential-guest-support=sev0,memory-backend=ram1 \ ...
Quoted 14 lines
Changelog:
----------
v11:
* Rebased on top of v6.11-rc1
* Added Acked-by/Reviewed-by
* Moved SEV Guest driver cleanups in the beginning of the series
* Commit message updates
* EnforcedPAGE_SIZEconstraints forsnp_guest_msg
* After offline discussion with Boris, redesigned and exported SEV guest messaging APIs to sev-guest driver
* Dropped VMPCK rework patches
* Make sure movement of SEV core routines does not break the SEV Guest driver midway of the series.
A gentle reminder.
Regards
Nikunj