linux-kernel - RE: [PATCH v2 03/21] x86/virt/tdx: Implement the SEAMCALL base function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BN9PR11MB5276D7C515C1F28300B0B3018C1D9@BN9PR11MB5276.namprd11.prod.outlook.com>
Date:   Mon, 28 Mar 2022 08:16:03 +0000
From:   "Tian, Kevin" <kevin.tian@...el.com>
To:     "Huang, Kai" <kai.huang@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "kvm@...r.kernel.org" <kvm@...r.kernel.org>
CC:     "Hansen, Dave" <dave.hansen@...el.com>,
        "Christopherson,, Sean" <seanjc@...gle.com>,
        "pbonzini@...hat.com" <pbonzini@...hat.com>,
        "kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
        "sathyanarayanan.kuppuswamy@...ux.intel.com" 
        <sathyanarayanan.kuppuswamy@...ux.intel.com>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "Luck, Tony" <tony.luck@...el.com>,
        "ak@...ux.intel.com" <ak@...ux.intel.com>,
        "Williams, Dan J" <dan.j.williams@...el.com>,
        "Yamahata, Isaku" <isaku.yamahata@...el.com>
Subject: RE: [PATCH v2 03/21] x86/virt/tdx: Implement the SEAMCALL base
 function

> From: Huang, Kai <kai.huang@...el.com>
> Sent: Monday, March 28, 2022 9:42 AM
> 
> 
> >
> > >
> > > A CPU-attested software module (called the 'TDX module') runs in SEAM
> > > VMX root to manage the crypto protected VMs running in SEAM VMX
> non-
> > > root.
> > > SEAM VMX root is also used to host another CPU-attested software
> module
> > > (called the 'P-SEAMLDR') to load and update the TDX module.
> > >
> > > Host kernel transits to either the P-SEAMLDR or the TDX module via the
> > > new SEAMCALL instruction.  SEAMCALLs are host-side interface functions
> > > defined by the P-SEAMLDR and the TDX module around the new
> SEAMCALL
> > > instruction.  They are similar to a hypercall, except they are made by
> >
> > "SEAMCALLs are ... functions ... around the new SEAMCALL instruction"
> >
> > This is confusing. Probably just:
> 
> May I ask why is it confusing?

SEAMCALL is an instruction. One of its arguments carries the function
number.