[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230626205445.GD3436214@ls.amr.corp.intel.com>
Date: Mon, 26 Jun 2023 13:54:45 -0700
From: Isaku Yamahata <isaku.yamahata@...il.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: isaku.yamahata@...el.com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, isaku.yamahata@...il.com,
Paolo Bonzini <pbonzini@...hat.com>, erdemaktas@...gle.com,
Sagi Shahar <sagis@...gle.com>,
David Matlack <dmatlack@...gle.com>,
Kai Huang <kai.huang@...el.com>,
Zhi Wang <zhi.wang.linux@...il.com>, chen.bo@...el.com,
linux-coco@...ts.linux.dev,
Chao Peng <chao.p.peng@...ux.intel.com>,
Ackerley Tng <ackerleytng@...gle.com>,
Vishal Annapurve <vannapurve@...gle.com>,
Michael Roth <michael.roth@....com>
Subject: Re: [RFC PATCH 0/6] KVM: guest memory: Misc enhacnement
On Fri, Jun 23, 2023 at 05:09:26PM -0700,
Sean Christopherson <seanjc@...gle.com> wrote:
> On Thu, Jun 15, 2023, isaku.yamahata@...el.com wrote:
> > * VM type: Now we have KVM_X86_PROTECTED_VM. How do we proceed?
> > - Keep KVM_X86_PROTECTED_VM for its use. Introduce KVM_X86_TDX_VM
> > - Use KVM_X86_PROTECTED_VM for TDX. (If necessary, introduce another type in
> > the future)
>
> How would KVM differentiate between software-protected VMs and TDX VMs if we go
> with this option?
Let's introduce new two VM type. I'm fine with two new VM types. I had KVM
capability in mind if SEV implementation doesn't like new VM types.
--
Isaku Yamahata <isaku.yamahata@...il.com>
Powered by blists - more mailing lists