Thu, Apr 02, 2026 at 02:02:54PM +0200, [email protected] wrote: >On Thu, Apr 02, 2026 at 10:52:34AM +0100, Brian Starkey wrote: >> I'm not clear why the heap depends on !CONFIG_HIGHMEM, but I also >> don't know anything about SEV/TDX. > >It is because the CC apis, set_memory_decrypted()/etc are slightly >mis-designed. They take in a vaddr to represent the address instead of >a phys_addr_t or a page * > >This means the user has to use page_address() and then the whole thing >is incompatible with highmem. > >Which is fine, highmem and CC are never turned on together.
Yeah, I was wondering if it is worth sanitizing it, but decided to be on the safe side, for unlikely oddities future may bring sake :)
