Have TTM support SEV encryption with coherent memory
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest4 patches 37 repliesIn review
Changes in v2 from the cover letter
- Use force_dma_unencrypted() rather than sev_active() to catch also the special SME encryption cases.
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | x86/mm: Export force_dma_unencryptedarch/ | +1 | 11 replies | |
| 2/4 | s390/mm: Export force_dma_unencryptedarch/ | +1 | 1 reply | |
| 3/4 | drm/ttm, drm/vmwgfx: Correctly support support AMD memory encryptiondrivers/ drivers/ drivers/ +3 more | +37 | 23 replies | |
| 4/4 | drm/ttm: Cache dma pool decrypted pages when AMD SEV is activedrivers/ | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/4] Have TTM support SEV encryption with coherent memory
With SEV memory encryption and in some cases also with SME memory encryption, coherent memory is unencrypted. In those cases, TTM doesn't set up the correct page protection. Fix this by having the TTM coherent page allocator call into the platform code to determine whether coherent memory is encrypted or not, and modify the page protection if it is not.
v2:
- Use force_dma_unencrypted() rather than sev_active() to catch also the special SME encryption cases.