All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxing Hu <huhuvmb88@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Will Deacon" <will@kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Joerg Roedel" <joro@8bytes.org>,
	iommu@lists.linux.dev, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/rockchip: implement .flush_iotlb_all
Date: Sat, 11 Jul 2026 09:23:04 +1200	[thread overview]
Message-ID: <20260710212304.11958-1-huhuvmb88@gmail.com> (raw)
In-Reply-To: <20260710060513.863714-1-huhuvmb88@gmail.com>

On Sat, 11 Jul 2026, Robin Murphy wrote:
> there's no harm in drivers implementing it *if* they also implement the
> relevant optimisations to avoid synchronous flushing in unmap_pages to
> make CAP_DEFERRED_FLUSH worthwhile.

Understood, thanks. I will drop the standalone patch. If I come back to
rk_iommu it will be the full version: move invalidation out of unmap_pages
into an iotlb_sync/gather path and advertise CAP_DEFERRED_FLUSH with
numbers, rather than flush_iotlb_all on its own.

Thanks,
Jiaxing

WARNING: multiple messages have this Message-ID (diff)
From: Jiaxing Hu <huhuvmb88@gmail.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: "Will Deacon" <will@kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Joerg Roedel" <joro@8bytes.org>,
	iommu@lists.linux.dev, linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/rockchip: implement .flush_iotlb_all
Date: Sat, 11 Jul 2026 09:23:04 +1200	[thread overview]
Message-ID: <20260710212304.11958-1-huhuvmb88@gmail.com> (raw)
In-Reply-To: <20260710060513.863714-1-huhuvmb88@gmail.com>

On Sat, 11 Jul 2026, Robin Murphy wrote:
> there's no harm in drivers implementing it *if* they also implement the
> relevant optimisations to avoid synchronous flushing in unmap_pages to
> make CAP_DEFERRED_FLUSH worthwhile.

Understood, thanks. I will drop the standalone patch. If I come back to
rk_iommu it will be the full version: move invalidation out of unmap_pages
into an iotlb_sync/gather path and advertise CAP_DEFERRED_FLUSH with
numbers, rather than flush_iotlb_all on its own.

Thanks,
Jiaxing

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2026-07-10 21:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-10  6:05 [PATCH] iommu/rockchip: implement .flush_iotlb_all Jiaxing Hu
2026-07-10  6:05 ` Jiaxing Hu
2026-07-10 10:59 ` Will Deacon
2026-07-10 10:59   ` Will Deacon
2026-07-10 12:11   ` Robin Murphy
2026-07-10 12:11     ` Robin Murphy
2026-07-10 11:15 ` Jiaxing Hu
2026-07-10 11:15   ` Jiaxing Hu
2026-07-10 13:42   ` Heiko Stübner
2026-07-10 13:42     ` Heiko Stübner
2026-07-10 21:11   ` Jiaxing Hu
2026-07-10 21:11     ` Jiaxing Hu
2026-07-10 21:23 ` Jiaxing Hu [this message]
2026-07-10 21:23   ` Jiaxing Hu

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=20260710212304.11958-1-huhuvmb88@gmail.com \
    --to=huhuvmb88@gmail.com \
    --cc=heiko@sntech.de \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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 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.