linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
Cc: iommu@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
	robin.murphy@arm.com, will@kernel.org, joro@8bytes.org,
	ryan.roberts@arm.com, kevin.tian@intel.com, nicolinc@nvidia.com,
	mshavit@google.com, eric.auger@redhat.com,
	joao.m.martins@oracle.com, jiangkunkun@huawei.com,
	zhukeqian1@huawei.com, linuxarm@huawei.com
Subject: Re: [PATCH v3 0/4] iommu/smmuv3: Add IOMMUFD dirty tracking support for SMMUv3
Date: Sun, 12 May 2024 09:58:48 -0300	[thread overview]
Message-ID: <ZkC9CK2bLPpqpSaP@nvidia.com> (raw)
In-Reply-To: <20240430134308.1604-1-shameerali.kolothum.thodi@huawei.com>

On Tue, Apr 30, 2024 at 02:43:04PM +0100, Shameer Kolothum wrote:
> This is revisiting the earlier attempts [1, 2] to use SMMUv3 HTTU feature
> for dirty page tracking. The Intel/AMD support is already mainline.
> 
> Basic sanity tests are done using an emulation setup and on a test
> hardware setup. Block page split/merge(BBML) is not part of this
> series. I am planning to send it separately.

This looks good to me, lets have it go after the merge window. As I
mentioned please post a version rebased on top of v6.10-rc1. (ie
based on the patches only in Joerg's current tree) in two weeks.

Thanks,
Jason

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-05-12 12:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-30 13:43 [PATCH v3 0/4] iommu/smmuv3: Add IOMMUFD dirty tracking support for SMMUv3 Shameer Kolothum
2024-04-30 13:43 ` [PATCH v3 1/4] iommu/arm-smmu-v3: Add feature detection for HTTU Shameer Kolothum
2024-05-22  7:02   ` Tian, Kevin
2024-04-30 13:43 ` [PATCH v3 2/4] iommu/io-pgtable-arm: Add read_and_clear_dirty() support Shameer Kolothum
2024-04-30 14:51   ` Ryan Roberts
2024-05-12 12:51   ` Jason Gunthorpe
2024-05-22  7:12   ` Tian, Kevin
2024-05-22 12:37     ` Jason Gunthorpe
2024-05-22 14:03     ` Shameerali Kolothum Thodi
2024-05-22 14:37       ` Joao Martins
2024-05-22 16:56         ` Jason Gunthorpe
2024-05-22 17:10           ` Joao Martins
2024-05-22 17:50             ` Jason Gunthorpe
2024-05-22 18:15               ` Joao Martins
2024-05-22 18:39                 ` Joao Martins
2024-05-23  3:30               ` Tian, Kevin
2024-05-24 11:30                 ` Joao Martins
2024-05-24 14:07                   ` Jason Gunthorpe
2024-05-27  1:21                     ` Tian, Kevin
2024-05-27  9:50                       ` Joao Martins
2024-06-01 18:55                       ` Jason Gunthorpe
2024-06-03 18:50                         ` Joao Martins
2024-04-30 13:43 ` [PATCH v3 3/4] iommu/arm-smmu-v3: Add support for dirty tracking in domain alloc Shameer Kolothum
2024-04-30 15:05   ` Ryan Roberts
2024-05-12 12:57   ` Jason Gunthorpe
2024-05-22  7:16   ` Tian, Kevin
2024-05-22 12:38     ` Jason Gunthorpe
2024-05-22 14:30     ` Shameerali Kolothum Thodi
2024-05-22 23:49       ` Tian, Kevin
2024-04-30 13:43 ` [PATCH v3 4/4] iommu/arm-smmu-v3: Enable HTTU for stage1 with io-pgtable mapping Shameer Kolothum
2024-05-12 12:08   ` Jason Gunthorpe
2024-05-22  7:19     ` Tian, Kevin
2024-05-22 12:39       ` Jason Gunthorpe
2024-05-22 23:52         ` Tian, Kevin
2024-05-22 13:26     ` Shameerali Kolothum Thodi
2024-05-22 13:41       ` Jason Gunthorpe
2024-05-12 12:58 ` Jason Gunthorpe [this message]
2024-05-22 13:28   ` [PATCH v3 0/4] iommu/smmuv3: Add IOMMUFD dirty tracking support for SMMUv3 Shameerali Kolothum Thodi

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=ZkC9CK2bLPpqpSaP@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --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=mshavit@google.com \
    --cc=nicolinc@nvidia.com \
    --cc=robin.murphy@arm.com \
    --cc=ryan.roberts@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.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 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).