[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240415210421.GR3039520@ls.amr.corp.intel.com>
Date: Mon, 15 Apr 2024 14:04:21 -0700
From: Isaku Yamahata <isaku.yamahata@...el.com>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
Cc: "Li, Xiaoyao" <xiaoyao.li@...el.com>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"davidskidmore@...gle.com" <davidskidmore@...gle.com>,
"seanjc@...gle.com" <seanjc@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"srutherford@...gle.com" <srutherford@...gle.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"pankaj.gupta@....com" <pankaj.gupta@....com>,
"Wang, Wei W" <wei.w.wang@...el.com>,
"isaku.yamahata@...ux.intel.com" <isaku.yamahata@...ux.intel.com>
Subject: Re: [ANNOUNCE] PUCK Notes - 2024.04.03 - TDX Upstreaming Strategy
On Fri, Apr 12, 2024 at 08:05:44PM +0000,
"Edgecombe, Rick P" <rick.p.edgecombe@...el.com> wrote:
> > We can use device attributes as discussed at
> > https://lore.kernel.org/kvm/CABgObfZzkNiP3q8p=KpvvFnh8m6qcHX4=tATaJc7cvVv2QWpJQ@mail.gmail.com/
> > https://lore.kernel.org/kvm/20240404121327.3107131-6-pbonzini@redhat.com/
> >
> > Something like
> >
> > #define KVM_X86_GRP_TDX 2
> > ioctl(fd, KVM_GET_DEVICE_ATTR, (KVM_X86_GRP_TDX, metadata_field_id))
>
> This would be instead of ATTRIBUTES and XFAM?
This is to replace KVM_TDX_CAPABILITIES.
--
Isaku Yamahata <isaku.yamahata@...el.com>
Powered by blists - more mailing lists