From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
Miklos Szeredi <miklos@szeredi.hu>,
Punit Salian <psalian@google.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>,
linux-coco@lists.linux.dev, x86@kernel.org
Subject: Re: [PATCH] fuse: mark DAX VMA page protections as decrypted
Date: Wed, 19 Aug 2026 17:03:10 +0200 [thread overview]
Message-ID: <b965c127-08d2-4e57-9396-a2c3f5cf253a@amd.com> (raw)
In-Reply-To: <004afd12-762d-45d6-ab75-037d58e7a359@amd.com>
Hi Punit,
>>>> In confidential computing guest environments (such as AMD SEV-SNP or
>>>> Intel TDX), direct memory access (DAX) mappings between the guest
>>>> kernel
>>>> and host-backed FUSE/virtiofs shared memory regions must be accessed
>>>> using shared (decrypted) page protections.
>>>>
>>>> Modify fuse_dax_mmap() to apply pgprot_decrypted() to
>>>> vma->vm_page_prot
>>>> when establishing FUSE DAX memory mappings. This ensures guest page
>>>> table entries for shared DAX buffers are explicitly marked as
>>>> decrypted,
>>>> preventing memory encryption faults when accessing host-shared DAX
>>>> memory.
I started testing this on my AMD system with QEMU and am still working
through the configuration details.
Did you happen to test this with QEMU under SEV or SEV-SNP as well? If
so, would you mind sharing your setup steps or
the QEMU/virtio-fs configuration you used?
The error I am facing is: device 'vhost-user-fs-pci' does not support
ACCESS_PLATFORM when it is enabled.
But under SEV-SNP ACCESS_PLATFORM(iommu_platform) is globally enabled
and when I manually disable it, guest says:
[ 8.788217] virtiofs virtio0: device must provide
VIRTIO_F_ACCESS_PLATFORM
Did you observe something similar or there are additional virtiofsd
settings i need to use?
Thanks,
Pankaj
next prev parent reply other threads:[~2026-08-19 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260727210718.125872-1-psalian@google.com>
2026-08-18 11:38 ` [PATCH] fuse: mark DAX VMA page protections as decrypted Miklos Szeredi
2026-08-18 13:42 ` Tom Lendacky
2026-08-18 16:00 ` Gupta, Pankaj
2026-08-19 15:03 ` Gupta, Pankaj [this message]
2026-08-19 16:48 ` Punit Salian
2026-08-19 18:16 ` Michael Roth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b965c127-08d2-4e57-9396-a2c3f5cf253a@amd.com \
--to=pankaj.gupta@amd.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=psalian@google.com \
--cc=stefanha@redhat.com \
--cc=thomas.lendacky@amd.com \
--cc=vgoyal@redhat.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox