[PATCH v2 0/2] x86/sev: Generalize sev_setup_arch()

Alexander Shishkin posted 2 patches 2 years, 8 months ago
There is a newer version of this series
arch/x86/include/asm/mem_encrypt.h | 11 +++++++--
arch/x86/kernel/setup.c            |  2 +-
arch/x86/mm/mem_encrypt.c          | 34 ++++++++++++++++++++++++++++
arch/x86/mm/mem_encrypt_amd.c      | 36 ------------------------------
4 files changed, 44 insertions(+), 39 deletions(-)
[PATCH v2 0/2] x86/sev: Generalize sev_setup_arch()
Posted by Alexander Shishkin 2 years, 8 months ago
Hi,

Since previous version [0], I added 2/2, which is a minor cleanup.

The main intention of this is to move sev_setup_arch() to mem_encrypt.c
to reflect the fact that it's not SEV-specific, but covers TDX as well,
although unintentionally.

While looking at it, I also noticed that mem_encrypt_amd.c still
includes virtio_config.h, which was needed for the code that since got
moved to a different place (and even there doesn't require the include
any more).

[0] https://lore.kernel.org/all/20230530121728.28854-1-alexander.shishkin@linux.intel.com/

Alexander Shishkin (2):
  x86/sev: Move sev_setup_arch() to mem_encrypt.c
  x86/sev: Drop unneeded include

 arch/x86/include/asm/mem_encrypt.h | 11 +++++++--
 arch/x86/kernel/setup.c            |  2 +-
 arch/x86/mm/mem_encrypt.c          | 34 ++++++++++++++++++++++++++++
 arch/x86/mm/mem_encrypt_amd.c      | 36 ------------------------------
 4 files changed, 44 insertions(+), 39 deletions(-)

-- 
2.39.2
Re: [PATCH v2 0/2] x86/sev: Generalize sev_setup_arch()
Posted by Alexander Shishkin 2 years, 6 months ago
Alexander Shishkin <alexander.shishkin@linux.intel.com> writes:

> Hi,
>
> Since previous version [0], I added 2/2, which is a minor cleanup.
>
> The main intention of this is to move sev_setup_arch() to mem_encrypt.c
> to reflect the fact that it's not SEV-specific, but covers TDX as well,
> although unintentionally.
>
> While looking at it, I also noticed that mem_encrypt_amd.c still
> includes virtio_config.h, which was needed for the code that since got
> moved to a different place (and even there doesn't require the include
> any more).

Gentle ping.

Regards,
--
Alex