Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Alexander Shishkin <alexander.shishkin@linux.intel.com>
To:     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>,
        alexander.shishkin@linux.intel.com
Subject: Re: [PATCH v2 0/2] x86/sev: Generalize sev_setup_arch()
In-Reply-To: <20230609171214.31846-1-alexander.shishkin@linux.intel.com>
References: <20230609171214.31846-1-alexander.shishkin@linux.intel.com>
Date:   Mon, 31 Jul 2023 21:01:42 +0300
Message-ID: <87tttkx8mx.fsf@ubik.fi.intel.com>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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