From: Jason Gunthorpe <jgg@nvidia.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
kvm@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH V1 1/8] vfio: delete interfaces to update vaddr
Date: Wed, 17 May 2023 13:12:01 -0300 [thread overview]
Message-ID: <ZGT80dRx6D8e4IlW@nvidia.com> (raw)
In-Reply-To: <7614cc78-610a-f661-f564-b5cd6c624f42@oracle.com>
On Wed, Dec 07, 2022 at 09:26:33AM -0500, Steven Sistare wrote:
> > This flag should probably be marked reserved.
> >
> > Should we consider this separately for v6.2?
>
> Ideally I would like all kernels to support either the old or new vaddr interface.
> If iommufd + vfio compat does not make 6.2, then I prefer not to delete the old
> interface separately.
>
> > For the remainder, the long term plan is to move to iommufd, so any new
> > feature of type1 would need equivalent support in iommufd. Thanks,
>
> Sure. I will study iommufd and make a proposal.
>
> Will you review these patches as is to give feedback on the approach?
>
> If I show that iommufd and the vfio compat layer can support these interfaces,
> are you open to accepting these in v6.2 if iommufd is still a ways off? I see
> iommufd in qemu-next, but not the compat layer.
What happened to this? I still haven't seen iommufd support for this?
Jason
next prev parent reply other threads:[~2023-05-17 16:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 21:55 [PATCH V1 0/8] vfio virtual address update redo Steve Sistare
2022-12-06 21:55 ` [PATCH V1 1/8] vfio: delete interfaces to update vaddr Steve Sistare
2022-12-06 23:52 ` Alex Williamson
2022-12-07 14:26 ` Steven Sistare
2022-12-07 15:14 ` Alex Williamson
2023-05-17 16:12 ` Jason Gunthorpe [this message]
2023-05-17 17:35 ` Steven Sistare
2022-12-07 15:19 ` Jason Gunthorpe
2022-12-08 19:09 ` Steven Sistare
2022-12-08 19:44 ` Alex Williamson
2022-12-07 23:20 ` Jason Gunthorpe
2022-12-08 22:18 ` Alex Williamson
2022-12-06 21:55 ` [PATCH V1 2/8] vfio/type1: dma owner permission Steve Sistare
2022-12-07 15:28 ` Jason Gunthorpe
2022-12-08 20:13 ` Steven Sistare
2022-12-06 21:55 ` [PATCH V1 3/8] vfio: close dma owner Steve Sistare
2022-12-06 21:55 ` [PATCH V1 4/8] vfio/type1: " Steve Sistare
2022-12-06 21:55 ` [PATCH V1 5/8] vfio/type1: track locked_vm per dma Steve Sistare
2022-12-06 21:55 ` [PATCH V1 6/8] vfio/type1: update vaddr Steve Sistare
2022-12-06 21:55 ` [PATCH V1 7/8] vfio: change dma owner Steve Sistare
2022-12-07 16:58 ` Jason Gunthorpe
2022-12-08 16:48 ` Steven Sistare
2022-12-08 17:15 ` Jason Gunthorpe
2022-12-08 17:39 ` Steven Sistare
2022-12-08 17:46 ` Jason Gunthorpe
2022-12-06 21:55 ` [PATCH V1 8/8] vfio/type1: " Steve Sistare
2022-12-07 17:00 ` Jason Gunthorpe
2022-12-08 7:22 ` Dan Carpenter
2022-12-07 15:23 ` [PATCH V1 0/8] vfio virtual address update redo Jason Gunthorpe
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=ZGT80dRx6D8e4IlW@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=steven.sistare@oracle.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