linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolin Chen <nicolinc@nvidia.com>
To: <joro@8bytes.org>, Alex Williamson <alex.williamson@redhat.com>
Cc: <will@kernel.org>, <marcan@marcan.st>, <sven@svenpeter.dev>,
	<robin.murphy@arm.com>, <robdclark@gmail.com>,
	<baolu.lu@linux.intel.com>, <orsonzhai@gmail.com>,
	<baolin.wang7@gmail.com>, <zhang.lyra@gmail.com>,
	<jean-philippe@linaro.org>, <jgg@nvidia.com>,
	<kevin.tian@intel.com>, <suravee.suthikulpanit@amd.com>,
	<alyssa@rosenzweig.io>, <dwmw2@infradead.org>,
	<mjrosato@linux.ibm.com>, <gerald.schaefer@linux.ibm.com>,
	<thierry.reding@gmail.com>, <vdumpa@nvidia.com>,
	<jonathanh@nvidia.com>, <cohuck@redhat.com>,
	<thunder.leizhen@huawei.com>, <christophe.jaillet@wanadoo.fr>,
	<chenxiang66@hisilicon.com>, <john.garry@huawei.com>,
	<yangyingliang@huawei.com>, <iommu@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-arm-msm@vger.kernel.org>, <linux-s390@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>,
	<kvm@vger.kernel.org>
Subject: Re: [PATCH v5 0/5] cover-letter: Simplify vfio_iommu_type1 attach/detach routine
Date: Tue, 26 Jul 2022 11:32:43 -0700	[thread overview]
Message-ID: <YuAzS1LatwGEvk7S@Asurada-Nvidia> (raw)
In-Reply-To: <Ys9b7GSImp/sHair@Asurada-Nvidia>

On Wed, Jul 13, 2022 at 04:57:36PM -0700, Nicolin Chen wrote:

> > > > > This is on github:
> > > > > https://github.com/nicolinc/iommufd/commits/vfio_iommu_attach
> > > >
> > > > How do you foresee this going in, I'm imagining Joerg would merge the
> > > > first patch via the IOMMU tree and provide a topic branch that I'd
> > > > merge into the vfio tree along with the remaining patches.  Sound
> > > > right?  Thanks,
> > >
> > > We don't have any build dependency between the IOMMU change and
> > > VFIO changes, yet, without the IOMMU one, any iommu_attach_group()
> > > failure now would be a hard failure without a chance falling back
> > > to a new_domain, which is slightly different from the current flow.
> > >
> > > For a potential existing use case that relies on reusing existing
> > > domain, I think it'd be safer to have Joerg acking the first change
> > > so you merge them all? Thank!
> > 
> > Works for me, I'll look for buy-in + ack from Joerg.  Thanks,
> > 
> > Alex
> 
> Joerg, would it be possible for you to ack at the IOMMU patch?

Joerg, sorry for pinning again. Would it be possible for you
to give an ack at the IOMMU patch so that this series might
catch the last train of this cycle? Thanks!

      reply	other threads:[~2022-07-26 18:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01 21:44 [PATCH v5 0/5] cover-letter: Simplify vfio_iommu_type1 attach/detach routine Nicolin Chen
2022-07-01 21:44 ` [PATCH v5 1/5] iommu: Return -EMEDIUMTYPE for incompatible domain and device/group Nicolin Chen
2022-07-29 17:30   ` Jason Gunthorpe
2022-07-01 21:44 ` [PATCH v5 2/5] vfio/iommu_type1: Prefer to reuse domains vs match enforced cache coherency Nicolin Chen
2022-07-01 21:44 ` [PATCH v5 3/5] vfio/iommu_type1: Remove the domain->ops comparison Nicolin Chen
2022-07-29 17:33   ` Jason Gunthorpe
2022-07-01 21:44 ` [PATCH v5 4/5] vfio/iommu_type1: Clean up update_dirty_scope in detach_group() Nicolin Chen
2022-07-29 17:34   ` Jason Gunthorpe
2022-07-01 21:44 ` [PATCH v5 5/5] vfio/iommu_type1: Simplify group attachment Nicolin Chen
2022-07-06 17:42 ` [PATCH v5 0/5] cover-letter: Simplify vfio_iommu_type1 attach/detach routine Alex Williamson
2022-07-06 17:53   ` Nicolin Chen
2022-07-06 18:03     ` Alex Williamson
2022-07-13 23:57       ` Nicolin Chen
2022-07-26 18:32         ` Nicolin Chen [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=YuAzS1LatwGEvk7S@Asurada-Nvidia \
    --to=nicolinc@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=alyssa@rosenzweig.io \
    --cc=baolin.wang7@gmail.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chenxiang66@hisilicon.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=cohuck@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=jgg@nvidia.com \
    --cc=john.garry@huawei.com \
    --cc=jonathanh@nvidia.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=mjrosato@linux.ibm.com \
    --cc=orsonzhai@gmail.com \
    --cc=robdclark@gmail.com \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=sven@svenpeter.dev \
    --cc=thierry.reding@gmail.com \
    --cc=thunder.leizhen@huawei.com \
    --cc=vdumpa@nvidia.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will@kernel.org \
    --cc=yangyingliang@huawei.com \
    --cc=zhang.lyra@gmail.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).