[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c6c9edcecfed16577a93a591b54d0d39a99c5a27.camel@intel.com>
Date: Tue, 30 Aug 2022 02:25:19 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "Hansen, Dave" <dave.hansen@...el.com>,
"Wang, Wei W" <wei.w.wang@...el.com>, "bp@...en8.de" <bp@...en8.de>
CC: "khalid.elmously@...onical.com" <khalid.elmously@...onical.com>,
"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
"Luck, Tony" <tony.luck@...el.com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Cox, Philip" <philip.cox@...onical.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"wander@...hat.com" <wander@...hat.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
"hpa@...or.com" <hpa@...or.com>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"sathyanarayanan.kuppuswamy@...ux.intel.com"
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH v9 1/6] x86/tdx: Add TDX Guest attestation interface
driver
On Mon, 2022-08-29 at 08:05 +0000, Wang, Wei W wrote:
> On Monday, August 29, 2022 11:15 AM, Huang, Kai wrote:
> > On Mon, 2022-08-22 at 14:44 -0700, Dave Hansen wrote:
> > > What ioctl()s are in the pipeline for the host side? Are they all
> > > part of /dev/kvm, or are there any TDX-specific "drivers" for the host?
> >
> > Sorry for late reply. Was on vacation last week.
> >
> > AFAICT no ioctl() is in the pipeline for the host side, except those belong to
> > /dev/kvm.
> >
> > I am not 100% sure about TDX live migration support (TDX 1.5), though.
> > Supposedly even there are they should belong to /dev/kvm too. + Wang, wei
> > to confirm.
>
> Not /dev/kvm.
> TDX migration uses kvm device fd and implements a tdx-mig specific driver on it.
OK anyway so the "tdx-mig specific driver" will still be on top of KVM, and we
don't need a new device node at host for it.
--
Thanks,
-Kai
Powered by blists - more mailing lists