Fuad Tabba <[email protected]> writes: > Hi Jason, Aneesh, > > On Mon, 16 Nov 2026 14:02:59 +0000, Jason Gunthorpe <[email protected]> wrote: > [...] >> Just like you are wrapping set_memory_decrypted() in an allocator API >> the user that wants to have the no-change sharing needs its own >> special API too. > > That works. A separate API can cover no-change sharing when a user > needs it, so I'm fine with set_memory_decrypted() zeroing. > > Aneesh, the pKVM hunk does need cache maintenance after the memset(), > which I have in the Cc: stable patch I posted earlier today [1]. >
I will add that, along with the relevant comments. Thanks, -aneesh
