mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jörg Rödel" <joro@8bytes.org>, x86-ml <x86@kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/sev for v5.17
Date: Mon, 10 Jan 2022 11:30:46 +0100	[thread overview]
Message-ID: <YdwK1rME5ufAJdHG@zn.tnic> (raw)

Hi Linus,

please pull the accumulated pile of x86/sev generalizations and cleanups,
for 5.17.

Thx.

---

The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:

  Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_sev_for_v5.17_rc1

for you to fetch changes up to 20f07a044a76aebaaa0603038857229b5c460d69:

  x86/sev: Move common memory encryption code to mem_encrypt.c (2021-12-08 16:49:53 +0100)

----------------------------------------------------------------
- Share the SEV string unrolling logic with TDX as TDX guests need it too

- Cleanups and generalzation of code shared by SEV and TDX

----------------------------------------------------------------
Borislav Petkov (3):
      x86/sev: Get rid of excessive use of defines
      x86/head64: Carve out the guest encryption postprocessing into a helper
      x86/sev: Remove do_early_exception() forward declarations

Brijesh Singh (1):
      x86/sev: Shorten GHCB terminate macro names

Kirill A. Shutemov (1):
      x86/sev: Move common memory encryption code to mem_encrypt.c

Kuppuswamy Sathyanarayanan (2):
      x86/sev: Use CC_ATTR attribute to generalize string I/O unroll
      x86/sev: Rename mem_encrypt.c to mem_encrypt_amd.c

 arch/x86/Kconfig                  |  10 +-
 arch/x86/boot/compressed/sev.c    |   6 +-
 arch/x86/include/asm/io.h         |  20 +-
 arch/x86/include/asm/sev-common.h |  55 ++---
 arch/x86/kernel/cc_platform.c     |   8 +
 arch/x86/kernel/head64.c          |  60 +++---
 arch/x86/kernel/sev-shared.c      |   2 +-
 arch/x86/kernel/sev.c             |  11 +-
 arch/x86/mm/Makefile              |   7 +-
 arch/x86/mm/mem_encrypt.c         | 441 +-------------------------------------
 arch/x86/mm/mem_encrypt_amd.c     | 438 +++++++++++++++++++++++++++++++++++++
 include/linux/cc_platform.h       |  11 +
 12 files changed, 545 insertions(+), 524 deletions(-)
 create mode 100644 arch/x86/mm/mem_encrypt_amd.c

-- 
Regards/Gruss,
    Boris.

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

             reply	other threads:[~2022-01-10 10:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 10:30 Borislav Petkov [this message]
2022-01-10 18:27 ` 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=YdwK1rME5ufAJdHG@zn.tnic \
    --to=bp@suse.de \
    --cc=joro@8bytes.org \
    --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

all inboxes | Powered by JetHome®