From: Jason Gunthorpe <jgg@nvidia.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Peter Xu <peterx@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
<kvm@vger.kernel.org>
Subject: Re: [PATCH] vfio-pci: Use io_remap_pfn_range() for PCI IO memory
Date: Tue, 17 Nov 2020 13:07:41 -0400 [thread overview]
Message-ID: <20201117170741.GU917484@nvidia.com> (raw)
In-Reply-To: <b6bd90c5-69e0-4e73-4f1a-8bc000aab941@amd.com>
On Tue, Nov 17, 2020 at 10:37:18AM -0600, Tom Lendacky wrote:
> > Ideally it won't, but trapping through QEMU is a common debugging
> > technique and required if we implement virtualization quirks for a
> > device in QEMU. So I believe what you're saying is that device
> > assignment on SEV probably works only when we're using direct mapping
> > of the mmap into the VM and tracing or quirks would currently see
> > encrypted data. Has anyone had the opportunity to check that we don't
> > break device assignment to VMs with this patch? Thanks,
>
> I have not been able to test device assignment with this patch, yet. Jason?
I don't have SME systems, we have a customer that reported RDMA didn't
work and confirmed the similar RDMA patch worked.
I know VFIO is basically identical, so it should be applicable here
too.
Jasnon
next prev parent reply other threads:[~2020-11-17 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:34 [PATCH] vfio-pci: Use io_remap_pfn_range() for PCI IO memory Jason Gunthorpe
2020-11-05 23:39 ` Peter Xu
2020-11-16 15:53 ` Jason Gunthorpe
2020-11-16 21:43 ` Tom Lendacky
2020-11-16 23:20 ` Jason Gunthorpe
2020-11-17 15:33 ` Tom Lendacky
2020-11-17 15:54 ` Alex Williamson
2020-11-17 16:37 ` Tom Lendacky
2020-11-17 17:07 ` Jason Gunthorpe [this message]
2020-11-17 17:10 ` Tom Lendacky
2020-11-17 15:57 ` Peter Xu
2020-11-17 16:34 ` Tom Lendacky
2020-11-17 18:17 ` Peter Xu
2020-11-26 20:13 ` Jason Gunthorpe
2020-11-30 14:34 ` Tom Lendacky
2020-11-30 15:34 ` Alex Williamson
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=20201117170741.GU917484@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=thomas.lendacky@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.