All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Will Deacon <will@kernel.org>
Cc: "iommu@lists.linux.dev" <iommu@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"jgg@nvidia.com" <jgg@nvidia.com>,
	"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"kevin.tian@intel.com" <kevin.tian@intel.com>,
	"nicolinc@nvidia.com" <nicolinc@nvidia.com>,
	"mshavit@google.com" <mshavit@google.com>,
	"eric.auger@redhat.com" <eric.auger@redhat.com>,
	"joao.m.martins@oracle.com" <joao.m.martins@oracle.com>,
	jiangkunkun <jiangkunkun@huawei.com>,
	zhukeqian <zhukeqian1@huawei.com>, Linuxarm <linuxarm@huawei.com>
Subject: RE: [PATCH v6 0/6] Add IOMMUFD dirty tracking support for SMMUv3
Date: Wed, 3 Jul 2024 10:20:32 +0000	[thread overview]
Message-ID: <285351de4086438e922d3698e5a86a39@huawei.com> (raw)
In-Reply-To: <20240702184551.GA5167@willie-the-truck>



> -----Original Message-----
> From: Will Deacon <will@kernel.org>
> Sent: Tuesday, July 2, 2024 7:46 PM
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: iommu@lists.linux.dev; linux-arm-kernel@lists.infradead.org;
> robin.murphy@arm.com; joro@8bytes.org; jgg@nvidia.com;
> ryan.roberts@arm.com; mark.rutland@arm.com; kevin.tian@intel.com;
> nicolinc@nvidia.com; mshavit@google.com; eric.auger@redhat.com;
> joao.m.martins@oracle.com; jiangkunkun <jiangkunkun@huawei.com>;
> zhukeqian <zhukeqian1@huawei.com>; Linuxarm <linuxarm@huawei.com>
> Subject: Re: [PATCH v6 0/6] Add IOMMUFD dirty tracking support for
> SMMUv3
> 
> Hey Shameer,
> 
> On Thu, Jun 13, 2024 at 03:41:43PM +0100, Shameer Kolothum wrote:
> > v5 --> v6
> >  -Minor updates based on Nicolin's feedback.
> >  -Picked up R-by tags by Jason, Nicolin and Kevin(Thanks!)
> >
> > Hi Will,
> >
> > Not sure you got a chance to take a look at this series yet. Hopefully
> > this will make it for 6.11
> 
> This all looks good to me, thanks.
> 
> However, it conflicts with some of Jason's stuff that I've pushed out to
> for-joerg/smmu/updates:
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git/log/?h=for-
> joerg/arm-smmu/updates
> 
> Please can you rebase, retest and repost? Hopefully it makes your life
> even easier as, for example, I don't think you need the first patch at
> all anymore thanks to "iommu/arm-smmu-v3: Make SVA allocate a normal
> arm_smmu_domain".

Done. Please see the v7 send out just now.

Thanks,
Shameer

      reply	other threads:[~2024-07-03 10:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 14:41 [PATCH v6 0/6] Add IOMMUFD dirty tracking support for SMMUv3 Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 1/6] iommu/arm-smmu-v3: Factor out a common domain alloc Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 2/6] iommu/arm-smmu-v3: Add support for domain_alloc_user fn Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 3/6] iommu/arm-smmu-v3: Add feature detection for HTTU Shameer Kolothum
2024-06-13 17:50   ` Nicolin Chen
2024-06-13 14:41 ` [PATCH v6 4/6] iommu/io-pgtable-arm: Add read_and_clear_dirty() support Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 5/6] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc Shameer Kolothum
2024-06-13 14:41 ` [PATCH v6 6/6] iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping Shameer Kolothum
2024-07-02 13:15 ` [PATCH v6 0/6] Add IOMMUFD dirty tracking support for SMMUv3 Shameerali Kolothum Thodi
2024-07-02 13:19   ` Will Deacon
2024-07-02 13:25     ` Shameerali Kolothum Thodi
2024-07-02 18:45 ` Will Deacon
2024-07-03 10:20   ` Shameerali Kolothum Thodi [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=285351de4086438e922d3698e5a86a39@huawei.com \
    --to=shameerali.kolothum.thodi@huawei.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=jiangkunkun@huawei.com \
    --cc=joao.m.martins@oracle.com \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=mark.rutland@arm.com \
    --cc=mshavit@google.com \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=ryan.roberts@arm.com \
    --cc=will@kernel.org \
    --cc=zhukeqian1@huawei.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.