linux-kernel - Re: [PATCH v9 1/6] x86/tdx: Add TDX Guest attestation interface driver

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: <be080a46-e6c2-995b-9064-a8506c38bef8@intel.com>
Date:   Mon, 22 Aug 2022 14:44:19 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Kuppuswamy Sathyanarayanan 
        <sathyanarayanan.kuppuswamy@...ux.intel.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H . Peter Anvin" <hpa@...or.com>,
        "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
        Tony Luck <tony.luck@...el.com>,
        Andi Kleen <ak@...ux.intel.com>,
        Kai Huang <kai.huang@...el.com>,
        Wander Lairson Costa <wander@...hat.com>,
        Isaku Yamahata <isaku.yamahata@...il.com>,
        marcelo.cerri@...onical.com, tim.gardner@...onical.com,
        khalid.elmously@...onical.com, philip.cox@...onical.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v9 1/6] x86/tdx: Add TDX Guest attestation interface
 driver

On 8/22/22 14:36, Borislav Petkov wrote:
> Which makes my initial suggestion of calling this whole guest
> functionality a "tdx" driver not such a bad idea... Depends on
> whether there will be a split at all or it'll continue gaining more
> functionality.

Yep, let's get the crystal ball out.

TDX folks:

What other ioctl()s are in the pipeline for the guest side?

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?

We want to avoid both:

 1. A driver called /dev/tdx (or "tdx-guest) which is only and will only
    ever do TDX guest attestation.
 2. A driver called /dev/tdx-guest-attest which shares a ton of
    functionality with some future TDX guest feature like
    /dev/tdx-guest-snazzy-feature-foo.  Then, a new driver every time
    a new snazzy TDX feature shows up.