From: Randy Dunlap <rdunlap@infradead.org>
To: Vipin Sharma <vipinsh@google.com>,
thomas.lendacky@amd.com, pbonzini@redhat.com,
sean.j.christopherson@intel.com, tj@kernel.org,
lizefan@huawei.com
Cc: joro@8bytes.org, corbet@lwn.net, brijesh.singh@amd.com,
jon.grimm@amd.com, eric.vantassell@amd.com, gingell@google.com,
rientjes@google.com, kvm@vger.kernel.org, x86@kernel.org,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Dionna Glaze <dionnaglaze@google.com>,
Erdem Aktas <erdemaktas@google.com>
Subject: Re: [RFC Patch 1/2] KVM: SVM: Create SEV cgroup controller.
Date: Mon, 21 Sep 2020 18:04:04 -0700 [thread overview]
Message-ID: <94c3407d-07ca-8eaf-4073-4a5e2a3fb7b8@infradead.org> (raw)
In-Reply-To: <20200922004024.3699923-2-vipinsh@google.com>
Hi,
On 9/21/20 5:40 PM, Vipin Sharma wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index d6a0b31b13dc..1a57c362b803 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1101,6 +1101,20 @@ config CGROUP_BPF
> BPF_CGROUP_INET_INGRESS will be executed on the ingress path of
> inet sockets.
>
> +config CGROUP_SEV
> + bool "SEV ASID controller"
> + depends on KVM_AMD_SEV
> + default n
> + help
> + Provides a controller for AMD SEV ASIDs. This controller limits and
> + shows the total usage of SEV ASIDs used in encrypted VMs on AMD
> + processors. Whenever a new encrypted VM is created using SEV on an
> + AMD processor, this controller will check the current limit in the
> + cgroup to which the task belongs and will deny the SEV ASID if the
> + cgroup has already reached its limit.
> +
> + Say N if unsure.
Something here (either in the bool prompt string or the help text) should
let a reader know w.t.h. SEV means.
Without having to look in other places...
thanks.
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: Randy Dunlap <rdunlap-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Vipin Sharma <vipinsh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
thomas.lendacky-5C7GfCeVMHo@public.gmane.org,
pbonzini-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
sean.j.christopherson-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Cc: joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org,
corbet-T1hC0tSOHrs@public.gmane.org,
brijesh.singh-5C7GfCeVMHo@public.gmane.org,
jon.grimm-5C7GfCeVMHo@public.gmane.org,
eric.vantassell-5C7GfCeVMHo@public.gmane.org,
gingell-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
rientjes-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-doc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Dionna Glaze
<dionnaglaze-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
Erdem Aktas <erdemaktas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [RFC Patch 1/2] KVM: SVM: Create SEV cgroup controller.
Date: Mon, 21 Sep 2020 18:04:04 -0700 [thread overview]
Message-ID: <94c3407d-07ca-8eaf-4073-4a5e2a3fb7b8@infradead.org> (raw)
In-Reply-To: <20200922004024.3699923-2-vipinsh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Hi,
On 9/21/20 5:40 PM, Vipin Sharma wrote:
> diff --git a/init/Kconfig b/init/Kconfig
> index d6a0b31b13dc..1a57c362b803 100644
> --- a/init/Kconfig
> +++ b/init/Kconfig
> @@ -1101,6 +1101,20 @@ config CGROUP_BPF
> BPF_CGROUP_INET_INGRESS will be executed on the ingress path of
> inet sockets.
>
> +config CGROUP_SEV
> + bool "SEV ASID controller"
> + depends on KVM_AMD_SEV
> + default n
> + help
> + Provides a controller for AMD SEV ASIDs. This controller limits and
> + shows the total usage of SEV ASIDs used in encrypted VMs on AMD
> + processors. Whenever a new encrypted VM is created using SEV on an
> + AMD processor, this controller will check the current limit in the
> + cgroup to which the task belongs and will deny the SEV ASID if the
> + cgroup has already reached its limit.
> +
> + Say N if unsure.
Something here (either in the bool prompt string or the help text) should
let a reader know w.t.h. SEV means.
Without having to look in other places...
thanks.
--
~Randy
next prev parent reply other threads:[~2020-09-22 1:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 0:40 [RFC Patch 0/2] KVM: SVM: Cgroup support for SVM SEV ASIDs Vipin Sharma
2020-09-22 0:40 ` [RFC Patch 1/2] KVM: SVM: Create SEV cgroup controller Vipin Sharma
2020-09-22 1:04 ` Randy Dunlap [this message]
2020-09-22 1:04 ` Randy Dunlap
2020-09-22 1:22 ` Sean Christopherson
2020-09-22 16:05 ` Vipin Sharma
2020-09-22 16:05 ` Vipin Sharma
2020-11-03 16:39 ` James Bottomley
2020-11-03 18:10 ` Sean Christopherson
2020-11-03 22:43 ` James Bottomley
2020-09-22 7:54 ` kernel test robot
2020-09-22 0:40 ` [RFC Patch 2/2] KVM: SVM: SEV cgroup controller documentation Vipin Sharma
2020-09-22 0:40 ` Vipin Sharma
2020-09-22 1:48 ` [RFC Patch 0/2] KVM: SVM: Cgroup support for SVM SEV ASIDs Sean Christopherson
2020-09-22 21:14 ` Vipin Sharma
2020-09-22 21:14 ` Vipin Sharma
[not found] ` <20200924192116.GC9649@linux.intel.com>
2020-09-24 19:55 ` Tom Lendacky
2020-09-24 19:55 ` Tom Lendacky
2020-09-25 22:22 ` Vipin Sharma
2020-10-02 20:48 ` Vipin Sharma
2020-11-03 2:06 ` Sean Christopherson
2020-11-14 0:26 ` David Rientjes
2020-11-24 19:16 ` Sean Christopherson
2020-11-24 19:49 ` Vipin Sharma
2020-11-24 19:49 ` Vipin Sharma
2020-11-24 20:18 ` David Rientjes
2020-11-24 21:08 ` Vipin Sharma
2020-11-24 21:27 ` Sean Christopherson
2020-11-24 21:27 ` Sean Christopherson
2020-11-24 22:21 ` Vipin Sharma
2020-11-24 23:18 ` Sean Christopherson
2020-11-27 18:01 ` Christian Borntraeger
2020-11-27 18:01 ` Christian Borntraeger
2020-10-01 18:08 ` Peter Gonda
2020-10-01 22:44 ` Tom Lendacky
2020-10-01 22:44 ` Tom Lendacky
2020-09-23 12:47 ` Paolo Bonzini
2020-09-23 12:47 ` Paolo Bonzini
2020-09-23 12:47 ` Paolo Bonzini
2020-09-28 9:12 ` Janosch Frank
2020-09-28 9:12 ` Janosch Frank
2020-09-28 9:21 ` Christian Borntraeger
2020-09-28 9:21 ` Christian Borntraeger
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=94c3407d-07ca-8eaf-4073-4a5e2a3fb7b8@infradead.org \
--to=rdunlap@infradead.org \
--cc=brijesh.singh@amd.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dionnaglaze@google.com \
--cc=erdemaktas@google.com \
--cc=eric.vantassell@amd.com \
--cc=gingell@google.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=sean.j.christopherson@intel.com \
--cc=thomas.lendacky@amd.com \
--cc=tj@kernel.org \
--cc=vipinsh@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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.