On 9/10/2024 3:00 PM, Gupta, Pankaj wrote:
On 8/26/2024 11:35 PM, Kevin Loughlin wrote:
How can I test this? Can I test it with virtio-pmem device?
Correct. Assuming the CoCo guest accesses some virtio-pmem device in
devdax mode, mmapping() this virtio-pmem device's memory region
results in th
On 8/26/2024 11:35 PM, Kevin Loughlin wrote:
How can I test this? Can I test it with virtio-pmem device?
Correct. Assuming the CoCo guest accesses some virtio-pmem device in
devdax mode, mmapping() this virtio-pmem device's memory region
results in the guest and host reading the same (plaintext
> How can I test this? Can I test it with virtio-pmem device?
Correct. Assuming the CoCo guest accesses some virtio-pmem device in
devdax mode, mmapping() this virtio-pmem device's memory region
results in the guest and host reading the same (plaintext) values from
the region.
>
> Thanks,
> Pan
Confidential Computing (CoCo) guests encrypt private memory by default.
DAX memory regions allow a guest to bypass its own (private) page cache
and instead use host memory, which is not private to the guest.
Commit 867400af90f1 ("mm/memremap.c: map FS_DAX device memory as
decrypted") only ensures
Confidential Computing (CoCo) guests encrypt private memory by default.
DAX memory regions allow a guest to bypass its own (private) page cache
and instead use host memory, which is not private to the guest.
Commit 867400af90f1 ("mm/memremap.c: map FS_DAX device memory as
decrypted") only ensures
5 matches
Mail list logo
