linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jörg Rödel" <jroedel@suse.de>, x86-ml <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/cc for 5.18
Date: Mon, 21 Mar 2022 16:03:07 +0100	[thread overview]
Message-ID: <YjiTq6esjAKwvvZt@zn.tnic> (raw)

Hi Linus,

please pull some common confidential computing preparatory glue which
will be shared by SEV/SNP and TDX in the future.

Thx.

---

The following changes since commit cfb92440ee71adcc2105b0890bb01ac3cddb8507:

  Linux 5.17-rc5 (2022-02-20 13:07:20 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cc_for_v5.18_rc1

for you to fetch changes up to 1e8c5971c249893ac33ca983c32bafcf5d50c727:

  x86/mm/cpa: Generalize __set_memory_enc_pgtable() (2022-02-23 19:14:29 +0100)

----------------------------------------------------------------
- Add shared confidential computing code which will be used by both
vendors instead of proliferating home-grown solutions for technologies
which are pretty similar

----------------------------------------------------------------
Brijesh Singh (1):
      x86/mm/cpa: Generalize __set_memory_enc_pgtable()

Kirill A. Shutemov (3):
      x86/cc: Move arch/x86/{kernel/cc_platform.c => coco/core.c}
      x86/coco: Explicitly declare type of confidential computing platform
      x86/coco: Add API to handle encryption mask

 arch/x86/Kbuild                                |  2 +
 arch/x86/coco/Makefile                         |  6 +++
 arch/x86/{kernel/cc_platform.c => coco/core.c} | 56 +++++++++++++++-----
 arch/x86/include/asm/coco.h                    | 32 ++++++++++++
 arch/x86/include/asm/pgtable.h                 | 13 ++---
 arch/x86/include/asm/set_memory.h              |  1 -
 arch/x86/include/asm/x86_init.h                | 16 ++++++
 arch/x86/kernel/Makefile                       |  5 --
 arch/x86/kernel/cpu/mshyperv.c                 |  6 +++
 arch/x86/kernel/x86_init.c                     | 16 +++++-
 arch/x86/mm/mem_encrypt_amd.c                  | 72 ++++++++++++++++++--------
 arch/x86/mm/mem_encrypt_identity.c             | 12 +++--
 arch/x86/mm/pat/set_memory.c                   | 25 +++++----
 13 files changed, 199 insertions(+), 63 deletions(-)
 create mode 100644 arch/x86/coco/Makefile
 rename arch/x86/{kernel/cc_platform.c => coco/core.c} (73%)
 create mode 100644 arch/x86/include/asm/coco.h


-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Ivo Totev, HRB 36809, AG Nürnberg

             reply	other threads:[~2022-03-21 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 15:03 Borislav Petkov [this message]
2022-03-21 19:18 ` [GIT PULL] x86/cc for 5.18 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YjiTq6esjAKwvvZt@zn.tnic \
    --to=bp@suse.de \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).