From: Dionna Glaze <dionnaglaze@google.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Dionna Glaze <dionnaglaze@google.com>
Subject: [PATCH v2 0/2] kvm: sev: Add SNP guest request throttling
Date: Thu, 17 Nov 2022 18:11:25 +0000 [thread overview]
Message-ID: <20221117181127.1859634-1-dionnaglaze@google.com> (raw)
This patch series is based on
[PATCH Part2 v6 00/49] Add AMD Secure Nested Paging (SEV-SNP)
and is requested to be rolled into the upcoming v7 of that patch series.
The GHCB specification recommends that SNP guest requests should be
rate limited. This 2 patch series adds such rate limiting with a 2
burst, 2 second interval per VM as the default values for two new
kvm-amd module parameters:
guest_request_throttle_s
guest_request_throttle_burst
This patch series cooperates with the guest series,
Add throttling detection to sev-guest
in order for guests to retry when throttled, rather than disable the
VMPCK and fail to complete their request.
Changes since v1:
* Added missing Ccs to patches.
Dionna Glaze (2):
kvm: sev: Add SEV-SNP guest request throttling
kvm: sev: If ccp is busy, report throttled to guest
arch/x86/include/asm/sev-common.h | 1 +
arch/x86/kvm/svm/sev.c | 46 +++++++++++++++++++++++++++++--
arch/x86/kvm/svm/svm.h | 3 ++
3 files changed, 48 insertions(+), 2 deletions(-)
--
2.38.1.584.g0f3c55d4c2-goog
next reply other threads:[~2022-11-17 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 18:11 Dionna Glaze [this message]
2022-11-17 18:11 ` [PATCH v2 1/2] kvm: sev: Add SEV-SNP guest request throttling Dionna Glaze
2022-11-17 19:10 ` Dionna Amalie Glaze
2022-11-17 18:11 ` [PATCH v2 2/2] kvm: sev: If ccp is busy, report throttled to guest Dionna Glaze
2022-11-17 19:11 ` Dionna Amalie Glaze
2022-11-17 19:07 [PATCH v2 0/2] kvm: sev: Add SNP guest request throttling Dionna Glaze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221117181127.1859634-1-dionnaglaze@google.com \
--to=dionnaglaze@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.