All of lore.kernel.org
 help / color / mirror / Atom feed
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, 21 Sep 2020 18:48:38 -0700	[thread overview]
Message-ID: <20200922014836.GA26507@linux.intel.com> (raw)
In-Reply-To: <20200922004024.3699923-1-vipinsh@google.com>

On Mon, Sep 21, 2020 at 05:40:22PM -0700, Vipin Sharma wrote:
> Hello,
> 
> This patch series adds a new SEV controller for tracking and limiting
> the usage of SEV ASIDs on the AMD SVM platform.
> 
> SEV ASIDs are used in creating encrypted VM and lightweight sandboxes
> but this resource is in very limited quantity on a host.
> 
> This limited quantity creates issues like SEV ASID starvation and
> unoptimized scheduling in the cloud infrastructure.
> 
> SEV controller provides SEV ASID tracking and resource control
> mechanisms.

This should be genericized to not be SEV specific.  TDX has a similar
scarcity issue in the form of key IDs, which IIUC are analogous to SEV ASIDs
(gave myself a quick crash course on SEV ASIDs).  Functionally, I doubt it
would change anything, I think it'd just be a bunch of renaming.  The hardest
part would probably be figuring out a name :-).

Another idea would be to go even more generic and implement a KVM cgroup
that accounts the number of VMs of a particular type, e.g. legacy, SEV,
SEV-ES?, and TDX.  That has potential future problems though as it falls
apart if hardware every supports 1:MANY VMs:KEYS, or if there is a need to
account keys outside of KVM, e.g. if MKTME for non-KVM cases ever sees the
light of day.

  parent reply	other threads:[~2020-09-22  1:48 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 ` Sean Christopherson [this message]
     [not found]   ` <20200922014836.GA26507-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2020-09-22 21:14     ` [RFC Patch 0/2] KVM: SVM: Cgroup support for SVM SEV ASIDs 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
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=20200922014836.GA26507@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.