Add 'tsm-next' to linux-next

Add 'tsm-next' to linux-next

[Dan Williams]

Hi Stephen,

Please add 'tsm-next' to linux-next:

  git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux tsm-next

This branch contains work to unify the "attestation report" flow of
confidential computing (for both AMD and Intel platforms with hopefully
more in the future) behind a common ABI.

As this is a new proposal for confidential computing infrastructure
(outside of arch/x86/), there is not an established owner for
drivers/virt/coco/ common code. So, Stephen please add this branch for
now, and folks on Cc please holler if you would prefer to take the
patches through another tree.

This merges cleanly with current tip/master as of this morning, and the
arch/x86 touches are limited to supporting the tdx-guest driver.

---

The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:

  Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux tsm-next

for you to fetch changes up to f4738f56d1dc62aaba69b33702a5ab098f1b8c63:

  virt: tdx-guest: Add Quote generation support using TSM_REPORTS (2023-10-19 18:12:00 -0700)

----------------------------------------------------------------
Dan Williams (6):
      virt: sevguest: Fix passing a stack buffer as a scatterlist target
      virt: coco: Add a coco/Makefile and coco/Kconfig
      configfs-tsm: Introduce a shared ABI for attestation reports
      virt: sevguest: Prep for kernel internal get_ext_report()
      mm/slab: Add __free() support for kvfree
      virt: sevguest: Add TSM_REPORTS support for SNP_GET_EXT_REPORT

Kuppuswamy Sathyanarayanan (1):
      virt: tdx-guest: Add Quote generation support using TSM_REPORTS

 Documentation/ABI/testing/configfs-tsm  |  82 ++++++
 MAINTAINERS                             |   8 +
 arch/x86/coco/tdx/tdx.c                 |  21 ++
 arch/x86/include/asm/shared/tdx.h       |   1 +
 arch/x86/include/asm/tdx.h              |   2 +
 drivers/virt/Kconfig                    |   6 +-
 drivers/virt/Makefile                   |   4 +-
 drivers/virt/coco/Kconfig               |  14 ++
 drivers/virt/coco/Makefile              |   8 +
 drivers/virt/coco/sev-guest/Kconfig     |   1 +
 drivers/virt/coco/sev-guest/sev-guest.c | 214 ++++++++++++++--
 drivers/virt/coco/tdx-guest/Kconfig     |   1 +
 drivers/virt/coco/tdx-guest/tdx-guest.c | 229 ++++++++++++++++-
 drivers/virt/coco/tsm.c                 | 425 ++++++++++++++++++++++++++++++++
 include/linux/slab.h                    |   2 +
 include/linux/tsm.h                     |  69 ++++++
 include/uapi/linux/psp-sev.h            |   1 +
 include/uapi/linux/sev-guest.h          |   4 +-
 18 files changed, 1055 insertions(+), 37 deletions(-)
 create mode 100644 Documentation/ABI/testing/configfs-tsm
 create mode 100644 drivers/virt/coco/Kconfig
 create mode 100644 drivers/virt/coco/Makefile
 create mode 100644 drivers/virt/coco/tsm.c
 create mode 100644 include/linux/tsm.h

Re: Add 'tsm-next' to linux-next

[Dave Hansen]

On 10/24/23 12:33, Dan Williams wrote:
> This merges cleanly with current tip/master as of this morning, and the
> arch/x86 touches are limited to supporting the tdx-guest driver.

Yeah, these look quite simple.  If they do conflict with any other
arch/x86 work they should be trivial to resolve.

Re: Add 'tsm-next' to linux-next

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1756 bytes --]

Hi Dan,

On Tue, 24 Oct 2023 12:33:29 -0700 Dan Williams <dan.j.williams@intel.com> wrote:
>
> Please add 'tsm-next' to linux-next:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/djbw/linux tsm-next
> 
> This branch contains work to unify the "attestation report" flow of
> confidential computing (for both AMD and Intel platforms with hopefully
> more in the future) behind a common ABI.
> 
> As this is a new proposal for confidential computing infrastructure
> (outside of arch/x86/), there is not an established owner for
> drivers/virt/coco/ common code. So, Stephen please add this branch for
> now, and folks on Cc please holler if you would prefer to take the
> patches through another tree.
> 
> This merges cleanly with current tip/master as of this morning, and the
> arch/x86 touches are limited to supporting the tdx-guest driver.

Added from today.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
     * submitted under GPL v2 (or later) and include the Contributor's
        Signed-off-by,
     * posted to the relevant mailing list,
     * reviewed by you (or another maintainer of your subsystem tree),
     * successfully unit tested, and 
     * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]