From: Tom Lendacky <thomas.lendacky@amd.com>
To: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Alison Schofield <alison.schofield@intel.com>
Subject: Re: [PATCH v3 0/2] x86/sev: Generalize sev_setup_arch()
Date: Tue, 10 Oct 2023 15:46:37 -0500 [thread overview]
Message-ID: <34c937ad-f8d8-4f03-9f0d-bf46398b31df@amd.com> (raw)
In-Reply-To: <20231010145220.3960055-1-alexander.shishkin@linux.intel.com>
On 10/10/23 09:52, Alexander Shishkin wrote:
> Hi,
>
> v3:
> * rebased
> * moved mem_encrypt_setup_arch under a common #ifdef CONFIG_X86_MEM_ENCRYPT
> per Tom's comment
>
> v2: [1]
> * added 2/2, which is a minor cleanup
>
> v1: [0]
>
> 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/
> [1] https://lore.kernel.org/all/20230609171214.31846-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 | 4 ++--
> arch/x86/kernel/setup.c | 2 +-
> arch/x86/mm/mem_encrypt.c | 34 ++++++++++++++++++++++++++++
> arch/x86/mm/mem_encrypt_amd.c | 36 ------------------------------
> 4 files changed, 37 insertions(+), 39 deletions(-)
>
For the series:
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
prev parent reply other threads:[~2023-10-10 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 14:52 Alexander Shishkin
2023-10-10 14:52 ` [PATCH v3 1/2] x86/sev: Move sev_setup_arch() to mem_encrypt.c Alexander Shishkin
2023-10-11 8:30 ` [tip: x86/mm] " tip-bot2 for Alexander Shishkin
2023-10-10 14:52 ` [PATCH v3 2/2] x86/sev: Drop unneeded include Alexander Shishkin
2023-10-11 8:30 ` [tip: x86/mm] x86/sev: Drop unneeded #include tip-bot2 for Alexander Shishkin
2023-10-10 20:46 ` Tom Lendacky [this message]
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=34c937ad-f8d8-4f03-9f0d-bf46398b31df@amd.com \
--to=thomas.lendacky@amd.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alison.schofield@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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®