From: Dionna Glaze <dionnaglaze@google.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Dionna Glaze <dionnaglaze@google.com>
Subject: [PATCH v3 0/2] kvm: sev: Add SNP guest request throttling
Date: Thu, 19 Jan 2023 21:34:23 +0000 [thread overview]
Message-ID: <20230119213426.379312-1-dionnaglaze@google.com> (raw)
This patch series is based on
[RFC,v7,00/64] Add AMD Secure Nested Paging (SEV-SNP) Hypervisor Support
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 v2:
* Rebased on v7, changed "we" wording to passive voice.
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 | 47 +++++++++++++++++++++++++++++--
arch/x86/kvm/svm/svm.h | 3 ++
include/uapi/linux/in.h | 1 +
4 files changed, 50 insertions(+), 2 deletions(-)
--
2.39.0.246.g2a6d74b583-goog
next reply other threads:[~2023-01-19 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 21:34 Dionna Glaze [this message]
2023-01-19 21:34 ` [PATCH v3 1/2] kvm: sev: Add SEV-SNP " Dionna Glaze
2023-01-20 16:40 ` Sean Christopherson
2023-01-19 21:34 ` [PATCH v3 2/2] kvm: sev: If ccp is busy, report throttled to guest Dionna Glaze
2023-01-20 17:15 ` Tom Lendacky
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=20230119213426.379312-1-dionnaglaze@google.com \
--to=dionnaglaze@google.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®