RFC Fix SEV user-space mapping of unencrypted coherent memory
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 25 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | x86: Don't let pgprot_modify() change the page encryption bitarch/ | +7 | 22 replies | |
| 2/2 | dma-mapping: Fix dma_pgprot() for unencrypted coherent pageskernel/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/2] Fix SEV user-space mapping of unencrypted coherent memory
With SEV and sometimes with SME encryption, The dma api coherent memory is typically unencrypted, meaning the linear kernel map has the encryption bit cleared. However, default page protection returned from vm_get_page_prot() has the encryption bit set. So to compute the correct page protection we need to clear the encryption bit.
Also, in order for the encryption bit setting to survive across do_mmap() and mprotect_fixup(), We need to make pgprot_modify() aware of it and not touch it.
(Note that the encryption status is not logically encoded in the pfn but in the page protection even if an address line in the physical address is used).
The patchset has seen some sanity testing by exporting dma_pgprot() and using it in the vmwgfx mmap handler with SEV enabled.