Linux filesystem development
 help / color / mirror / Atom feed
From: Punit Salian <psalian@google.com>
To: pankaj.gupta@amd.com
Cc: michael.roth@amd.com, thomas.lendacky@amd.com, miklos@szeredi.hu,
	 linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	 stefanha@redhat.com, vgoyal@redhat.com,
	linux-coco@lists.linux.dev,  x86@kernel.org
Subject: Re: [PATCH] fuse: mark DAX VMA page protections as decrypted
Date: Tue, 25 Aug 2026 21:14:10 +0000	[thread overview]
Message-ID: <20260825211410.2805027-1-psalian@google.com> (raw)
In-Reply-To: <a877fa95-4cb4-44b9-b123-5d9084fa4e65@amd.com>

Hi Pankaj,

Thanks for looking into this! Yes, that makes sense - virtio-fs DAX support 
(the DAX window BAR) was developed in out-of-tree QEMU development branches 
(e.g., https://github.com/rhvgoyal/qemu or https://gitlab.com/virtio-fs/qemu) 
and was never fully merged into upstream mainline QEMU.

In our case, we validated the guest kernel DAX driver on AMD SEV-SNP and Intel TDX 
hardware using our in-house lightweight VMM coupled with the standalone Rust virtiofsd 
daemon. Other public VMMs like Cloud-Hypervisor [1] and crosvm [2] also support 
the DAX shared memory window natively.

I have posted a [PATCH v2] to the list incorporating your Acked-by tag.

Thanks again for the review and assistance!

[1] https://github.com/cloud-hypervisor/cloud-hypervisor
[2] https://github.com/google/crosvm

Best regards,
Punit

  reply	other threads:[~2026-08-25 21:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 21:07 [PATCH] fuse: mark DAX VMA page protections as decrypted Punit Salian
2026-08-18 11:38 ` Miklos Szeredi
2026-08-18 13:42   ` Tom Lendacky
2026-08-18 16:00     ` Gupta, Pankaj
2026-08-19 15:03       ` Gupta, Pankaj
2026-08-19 16:48         ` Punit Salian
2026-08-19 18:16         ` Michael Roth
2026-08-20  8:21           ` Gupta, Pankaj
2026-08-24 17:58             ` Punit Salian
2026-08-25 19:25               ` Gupta, Pankaj
2026-08-25 21:14                 ` Punit Salian [this message]
2026-08-25 17:54 ` [PATCH v2] " Punit Salian
2026-08-26 10:51   ` Miklos Szeredi

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=20260825211410.2805027-1-psalian@google.com \
    --to=psalian@google.com \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=miklos@szeredi.hu \
    --cc=pankaj.gupta@amd.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