From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Vipin Sharma <vipinsh@google.com>
Cc: thomas.lendacky@amd.com, pbonzini@redhat.com, tj@kernel.org,
lizefan@huawei.com, 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
Subject: Re: [RFC Patch 0/2] KVM: SVM: Cgroup support for SVM SEV ASIDs
Date: Mon, 2 Nov 2020 18:06:24 -0800 [thread overview]
Message-ID: <20201103020623.GJ21563@linux.intel.com> (raw)
In-Reply-To: <20201002204810.GA3179405@google.com>
On Fri, Oct 02, 2020 at 01:48:10PM -0700, Vipin Sharma wrote:
> On Fri, Sep 25, 2020 at 03:22:20PM -0700, Vipin Sharma wrote:
> > I agree with you that the abstract name is better than the concrete
> > name, I also feel that we must provide HW extensions. Here is one
> > approach:
> >
> > Cgroup name: cpu_encryption, encryption_slots, or memcrypt (open to
> > suggestions)
> >
> > Control files: slots.{max, current, events}
I don't particularly like the "slots" name, mostly because it could be confused
with KVM's memslots. Maybe encryption_ids.ids.{max, current, events}? I don't
love those names either, but "encryption" and "IDs" are the two obvious
commonalities betwee TDX's encryption key IDs and SEV's encryption address
space IDs.
next prev parent reply other threads:[~2020-11-03 2:06 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
[not found] ` <20200922004024.3699923-2-vipinsh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2020-09-22 1:04 ` Randy Dunlap
2020-09-22 1:04 ` Randy Dunlap
2020-09-22 1:22 ` Sean Christopherson
[not found] ` <20200922012227.GA26483-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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
[not found] ` <20200922004024.3699923-1-vipinsh-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
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
[not found] ` <20200922014836.GA26507-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2020-09-22 21:14 ` Vipin Sharma
2020-09-22 21:14 ` Vipin Sharma
[not found] ` <20200924192116.GC9649@linux.intel.com>
[not found] ` <20200924192116.GC9649-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
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 [this message]
2020-11-14 0:26 ` David Rientjes
2020-11-24 19:16 ` Sean Christopherson
[not found] ` <20201124191629.GB235281-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
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
[not found] ` <20201124210817.GA65542-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
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
[not found] ` <CAMkAt6oX+18cZy_t3hm0zo-sLmTGeGs5H9YAWvj7WBU7_uwU5Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
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=20201103020623.GJ21563@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=brijesh.singh@amd.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--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=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.