Linux Confidential Computing Development
 help / color / mirror / Atom feed
From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: Michael Roth <michael.roth@amd.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
	Miklos Szeredi <miklos@szeredi.hu>,
	Punit Salian <psalian@google.com>,
	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: Thu, 20 Aug 2026 10:21:45 +0200	[thread overview]
Message-ID: <51a316c1-4654-4f6f-92ff-84c310cd604d@amd.com> (raw)
In-Reply-To: <ijwjd4gc5hrowrxntq7dknbuhvotkvpuhrk3gdoorxab4kez2w@ym6mti6jmcmz>


>>
>> 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
> I'm not sure what the real solution should be for this, but does this
> hack for QEMU avoid the error?
>
>    https://github.com/AMDESE/qemu/commit/63f103e35f5f3735d10f7618584bd8bb208e2c28

Mike,

Yes, this hack avoids the error, and I was able to get virtio-fs working 
with it.

Thanks for sharing the patch!

Best regards,

Pankaj


      reply	other threads:[~2026-08-20  8:21 UTC|newest]

Thread overview: 7+ 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
2026-08-19 16:48         ` Punit Salian
2026-08-19 18:16         ` Michael Roth
2026-08-20  8:21           ` Gupta, Pankaj [this message]

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=51a316c1-4654-4f6f-92ff-84c310cd604d@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=michael.roth@amd.com \
    --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