On 9/11/19 7:59 AM, Ingo Molnar wrote:
* Thomas Hellström (VMware) wrote:
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
* Thomas Hellström (VMware) wrote:
> 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
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
On 9/10/19 8:11 AM, Christoph Hellwig wrote:
On Thu, Sep 05, 2019 at 04:23:11AM -0700, Christoph Hellwig wrote:
This looks fine from the DMA POV. I'll let the x86 guys comment on the
rest.
Do we want to pick this series up for 5.4? Should I queue it up in
the dma-mapping tree?
Hi,
On Thu, Sep 05, 2019 at 04:23:11AM -0700, Christoph Hellwig wrote:
> This looks fine from the DMA POV. I'll let the x86 guys comment on the
> rest.
Do we want to pick this series up for 5.4? Should I queue it up in
the dma-mapping tree?
This looks fine from the DMA POV. I'll let the x86 guys comment on the
rest.
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
7 matches
Mail list logo
