From: Alex Williamson <alex.williamson@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Jason Gunthorpe <jgg@nvidia.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: Mon, 30 Nov 2020 08:34:33 -0700 [thread overview]
Message-ID: <20201130083433.3b80ef13@w520.home> (raw)
In-Reply-To: <f7de6a25-8ace-3d51-d954-149752f9cf26@amd.com>
On Mon, 30 Nov 2020 08:34:51 -0600
Tom Lendacky <thomas.lendacky@amd.com> wrote:
> On 11/26/20 2:13 PM, Jason Gunthorpe wrote:
> > On Tue, Nov 17, 2020 at 01:17:54PM -0500, Peter Xu wrote:
> >
> >> Logically this patch should fix that, just like the dpdk scenario where mmio
> >> regions were accessed from userspace (qemu). From that pov, I think this patch
> >> should help.
> >>
> >> Acked-by: Peter Xu <peterx@redhat.com>
> >
> > Thanks Peter
> >
> > Is there more to do here?
>
> I just did a quick, limited passthrough test of a NIC device (non SRIOV)
> for a legacy and an SEV guest and it all appears to work.
>
> I don't have anything more (i.e. SRIOV, GPUs, etc.) with which to test
> device passthrough.
Thanks, I'll include this for v5.11.
Alex
prev parent reply other threads:[~2020-11-30 15:36 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
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 [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=20201130083433.3b80ef13@w520.home \
--to=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jgg@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).