From: Jason Gunthorpe via iommu <iommu@lists.linux-foundation.org>
To: Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
Cornelia Huck <cohuck@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Vivek Kumar Gautam <Vivek.Gautam@arm.com>,
iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] vfio: Remove VFIO_TYPE1_NESTING_IOMMU
Date: Thu, 12 May 2022 08:32:41 -0300 [thread overview]
Message-ID: <20220512113241.GQ49344@nvidia.com> (raw)
In-Reply-To: <6c6f3ecb-6339-4093-a15a-fcf95a7c61fb@linaro.org>
On Thu, May 12, 2022 at 03:07:09PM +0800, Zhangfei Gao wrote:
> > > I can't help feeling a little wary about removing this until IOMMUFD
> > > can actually offer a functional replacement - is it in the way of
> > > anything upcoming?
> > From an upstream perspective if someone has a patched kernel to
> > complete the feature, then they can patch this part in as well, we
> > should not carry dead code like this in the kernel and in the uapi.
> >
> > It is not directly in the way, but this needs to get done at some
> > point, I'd rather just get it out of the way.
>
> We are using this interface for nested mode.
How are you using it? It doesn't do anything. Do you have out of tree
patches as well?
Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2022-05-12 11:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 16:55 [PATCH] vfio: Remove VFIO_TYPE1_NESTING_IOMMU Jason Gunthorpe via iommu
2022-05-10 17:52 ` Robin Murphy
2022-05-10 18:13 ` Jason Gunthorpe via iommu
2022-05-12 7:07 ` Zhangfei Gao
2022-05-12 11:32 ` Jason Gunthorpe via iommu [this message]
2022-05-12 11:57 ` zhangfei.gao
2022-05-12 11:59 ` Jason Gunthorpe via iommu
2022-05-12 12:07 ` zhangfei.gao
2022-05-12 17:27 ` Eric Auger
2022-05-10 18:31 ` Nicolin Chen via iommu
2022-05-12 5:04 ` Tian, Kevin
2022-05-16 6:39 ` Christoph Hellwig
2022-05-17 20:26 ` Alex Williamson
2022-05-20 7:38 ` Joerg Roedel
2022-05-20 11:02 ` Robin Murphy
2022-05-20 12:00 ` Will Deacon
2022-05-20 12:28 ` Jason Gunthorpe via iommu
2022-05-20 12:18 ` Jason Gunthorpe via iommu
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=20220512113241.GQ49344@nvidia.com \
--to=iommu@lists.linux-foundation.org \
--cc=Vivek.Gautam@arm.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
--cc=zhangfei.gao@linaro.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