[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87jyye35qb.fsf@redhat.com>
Date: Mon, 22 Dec 2025 16:18:20 +0100
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: "Jason A. Donenfeld" <Jason@...c4.com>
Cc: Theodore Ts'o <tytso@....edu>, Ingo Molnar <mingo@...nel.org>, Kiryl
Shutsemau <kas@...nel.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Pradipta Banerjee <prbanerj@...hat.com>, Frank Liang
<xiliang@...hat.com>, Alexander Graf <graf@...zon.com>
Subject: Re: [PATCH] vmgenid: Remap memory as decrypted
"Jason A. Donenfeld" <Jason@...c4.com> writes:
> Hi Vitaly,
>
> On Mon, Dec 22, 2025 at 3:46 PM Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
>> - virt_addr = devm_memremap(&device->dev, phys_addr, VMGENID_SIZE, MEMREMAP_WB);
>> + virt_addr = devm_memremap(&device->dev, phys_addr, VMGENID_SIZE,
>> + MEMREMAP_WB | MEMREMAP_DEC);
>
> Thanks for this patch. I still need to do a bit of my own testing with
> it, but I've preliminarily applied it to the random.git tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/crng/random.git/commit/?id=9476583268980ce64ed75f124768fe3bff6fff4c
>
> Should this patch CC stable@, by the way?
>
I'm not sure how common the configuration (SEV-SNP/(TDX?) + vmgenid) is
but I guess AWS SEV-SNP config is significant enough to justify stable@
as all kernels 6.15+ don't boot there at all.
--
Vitaly
Powered by blists - more mailing lists