From: David Rientjes <rientjes@google.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>, joro@8bytes.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
alim.akhtar@samsung.com, alyssa@rosenzweig.io,
asahi@lists.linux.dev, baolu.lu@linux.intel.com,
bhelgaas@google.com, cgroups@vger.kernel.org, corbet@lwn.net,
david@redhat.com, dwmw2@infradead.org, hannes@cmpxchg.org,
heiko@sntech.de, iommu@lists.linux.dev,
jernej.skrabec@gmail.com, jonathanh@nvidia.com,
krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-tegra@vger.kernel.org, lizefan.x@bytedance.com,
marcan@marcan.st, mhiramat@kernel.org, m.szyprowski@samsung.com,
paulmck@kernel.org, rdunlap@infradead.org, robin.murphy@arm.com,
samuel@sholland.org, suravee.suthikulpanit@amd.com,
sven@svenpeter.dev, thierry.reding@gmail.com, tj@kernel.org,
tomas.mudrunka@gmail.com, vdumpa@nvidia.com, wens@csie.org,
will@kernel.org, yu-cheng.yu@intel.com, bagasdotme@gmail.com,
mkoutny@suse.com
Subject: Re: [PATCH v5 00/11] IOMMU memory observability
Date: Fri, 15 Mar 2024 14:33:53 -0700 (PDT) [thread overview]
Message-ID: <00555af4-8786-b772-7897-aef1e912b368@google.com> (raw)
In-Reply-To: <20240222173942.1481394-1-pasha.tatashin@soleen.com>
On Thu, 22 Feb 2024, Pasha Tatashin wrote:
> Pasha Tatashin (11):
> iommu/vt-d: add wrapper functions for page allocations
> iommu/dma: use iommu_put_pages_list() to releae freelist
> iommu/amd: use page allocation function provided by iommu-pages.h
> iommu/io-pgtable-arm: use page allocation function provided by
> iommu-pages.h
> iommu/io-pgtable-dart: use page allocation function provided by
> iommu-pages.h
> iommu/exynos: use page allocation function provided by iommu-pages.h
> iommu/rockchip: use page allocation function provided by iommu-pages.h
> iommu/sun50i: use page allocation function provided by iommu-pages.h
> iommu/tegra-smmu: use page allocation function provided by
> iommu-pages.h
> iommu: observability of the IOMMU allocations
> iommu: account IOMMU allocated memory
>
> Documentation/admin-guide/cgroup-v2.rst | 2 +-
> Documentation/filesystems/proc.rst | 4 +-
> drivers/iommu/amd/amd_iommu.h | 8 -
> drivers/iommu/amd/init.c | 91 ++++++------
> drivers/iommu/amd/io_pgtable.c | 13 +-
> drivers/iommu/amd/io_pgtable_v2.c | 20 +--
> drivers/iommu/amd/iommu.c | 13 +-
> drivers/iommu/dma-iommu.c | 7 +-
> drivers/iommu/exynos-iommu.c | 14 +-
> drivers/iommu/intel/dmar.c | 16 +-
> drivers/iommu/intel/iommu.c | 47 ++----
> drivers/iommu/intel/iommu.h | 2 -
> drivers/iommu/intel/irq_remapping.c | 16 +-
> drivers/iommu/intel/pasid.c | 18 +--
> drivers/iommu/intel/svm.c | 11 +-
> drivers/iommu/io-pgtable-arm.c | 15 +-
> drivers/iommu/io-pgtable-dart.c | 37 ++---
> drivers/iommu/iommu-pages.h | 186 ++++++++++++++++++++++++
> drivers/iommu/rockchip-iommu.c | 14 +-
> drivers/iommu/sun50i-iommu.c | 7 +-
> drivers/iommu/tegra-smmu.c | 18 ++-
> include/linux/mmzone.h | 5 +-
> mm/vmstat.c | 3 +
> 23 files changed, 361 insertions(+), 206 deletions(-)
> create mode 100644 drivers/iommu/iommu-pages.h
>
Joerg, is this series anticipated to be queued up in the core branch of
git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git so it gets into
linux-next?
This observability seems particularly useful so that we can monitor and
alert on any unexpected increases (unbounded memory growth from this
subsystem has in the past caused us issues before the memory is otherwise
not observable by host software).
Or are we still waiting on code reviews from some folks that we should
ping?
Thanks!
WARNING: multiple messages have this Message-ID (diff)
From: David Rientjes <rientjes@google.com>
To: Pasha Tatashin <pasha.tatashin@soleen.com>, joro@8bytes.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
alim.akhtar@samsung.com, alyssa@rosenzweig.io,
asahi@lists.linux.dev, baolu.lu@linux.intel.com,
bhelgaas@google.com, cgroups@vger.kernel.org, corbet@lwn.net,
david@redhat.com, dwmw2@infradead.org, hannes@cmpxchg.org,
heiko@sntech.de, iommu@lists.linux.dev,
jernej.skrabec@gmail.com, jonathanh@nvidia.com,
krzysztof.kozlowski@linaro.org, linux-doc@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-sunxi@lists.linux.dev,
linux-tegra@vger.kernel.org, lizefan.x@bytedance.com,
marcan@marcan.st, mhiramat@kernel.org, m.szyprowski@samsung.com,
paulmck@kernel.org, rdunlap@infradead.org, robin.murphy@arm.com,
samuel@sholland.org, suravee.suthikulpanit@amd.com,
sven@svenpeter.dev, thierry.reding@gmail.com, tj@kernel.org,
tomas.mudrunka@gmail.com, vdumpa@nvidia.com, wens@csie.org,
will@kernel.org, yu-cheng.yu@intel.com, bagasdotme@gmail.com,
mkoutny@suse.com
Subject: Re: [PATCH v5 00/11] IOMMU memory observability
Date: Fri, 15 Mar 2024 14:33:53 -0700 (PDT) [thread overview]
Message-ID: <00555af4-8786-b772-7897-aef1e912b368@google.com> (raw)
In-Reply-To: <20240222173942.1481394-1-pasha.tatashin@soleen.com>
On Thu, 22 Feb 2024, Pasha Tatashin wrote:
> Pasha Tatashin (11):
> iommu/vt-d: add wrapper functions for page allocations
> iommu/dma: use iommu_put_pages_list() to releae freelist
> iommu/amd: use page allocation function provided by iommu-pages.h
> iommu/io-pgtable-arm: use page allocation function provided by
> iommu-pages.h
> iommu/io-pgtable-dart: use page allocation function provided by
> iommu-pages.h
> iommu/exynos: use page allocation function provided by iommu-pages.h
> iommu/rockchip: use page allocation function provided by iommu-pages.h
> iommu/sun50i: use page allocation function provided by iommu-pages.h
> iommu/tegra-smmu: use page allocation function provided by
> iommu-pages.h
> iommu: observability of the IOMMU allocations
> iommu: account IOMMU allocated memory
>
> Documentation/admin-guide/cgroup-v2.rst | 2 +-
> Documentation/filesystems/proc.rst | 4 +-
> drivers/iommu/amd/amd_iommu.h | 8 -
> drivers/iommu/amd/init.c | 91 ++++++------
> drivers/iommu/amd/io_pgtable.c | 13 +-
> drivers/iommu/amd/io_pgtable_v2.c | 20 +--
> drivers/iommu/amd/iommu.c | 13 +-
> drivers/iommu/dma-iommu.c | 7 +-
> drivers/iommu/exynos-iommu.c | 14 +-
> drivers/iommu/intel/dmar.c | 16 +-
> drivers/iommu/intel/iommu.c | 47 ++----
> drivers/iommu/intel/iommu.h | 2 -
> drivers/iommu/intel/irq_remapping.c | 16 +-
> drivers/iommu/intel/pasid.c | 18 +--
> drivers/iommu/intel/svm.c | 11 +-
> drivers/iommu/io-pgtable-arm.c | 15 +-
> drivers/iommu/io-pgtable-dart.c | 37 ++---
> drivers/iommu/iommu-pages.h | 186 ++++++++++++++++++++++++
> drivers/iommu/rockchip-iommu.c | 14 +-
> drivers/iommu/sun50i-iommu.c | 7 +-
> drivers/iommu/tegra-smmu.c | 18 ++-
> include/linux/mmzone.h | 5 +-
> mm/vmstat.c | 3 +
> 23 files changed, 361 insertions(+), 206 deletions(-)
> create mode 100644 drivers/iommu/iommu-pages.h
>
Joerg, is this series anticipated to be queued up in the core branch of
git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git so it gets into
linux-next?
This observability seems particularly useful so that we can monitor and
alert on any unexpected increases (unbounded memory growth from this
subsystem has in the past caused us issues before the memory is otherwise
not observable by host software).
Or are we still waiting on code reviews from some folks that we should
ping?
Thanks!
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-03-15 21:33 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:39 [PATCH v5 00/11] IOMMU memory observability Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 01/11] iommu/vt-d: add wrapper functions for page allocations Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-04-04 12:16 ` Linu Cherian
2024-04-04 12:16 ` Linu Cherian
2024-04-04 13:56 ` Pasha Tatashin
2024-04-04 13:56 ` Pasha Tatashin
2024-04-08 2:17 ` Linu Cherian
2024-04-08 2:17 ` Linu Cherian
2024-02-22 17:39 ` [PATCH v5 02/11] iommu/dma: use iommu_put_pages_list() to releae freelist Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-03-15 21:28 ` David Rientjes
2024-03-15 21:28 ` David Rientjes
2024-02-22 17:39 ` [PATCH v5 03/11] iommu/amd: use page allocation function provided by iommu-pages.h Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 04/11] iommu/io-pgtable-arm: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 05/11] iommu/io-pgtable-dart: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 06/11] iommu/exynos: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 07/11] iommu/rockchip: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 08/11] iommu/sun50i: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 09/11] iommu/tegra-smmu: " Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 10/11] iommu: observability of the IOMMU allocations Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-02-22 17:39 ` [PATCH v5 11/11] iommu: account IOMMU allocated memory Pasha Tatashin
2024-02-22 17:39 ` Pasha Tatashin
2024-03-15 21:33 ` David Rientjes [this message]
2024-03-15 21:33 ` [PATCH v5 00/11] IOMMU memory observability David Rientjes
2024-03-15 21:53 ` Joerg Roedel
2024-03-15 21:53 ` Joerg Roedel
2024-04-03 13:18 ` Pasha Tatashin
2024-04-03 13:18 ` Pasha Tatashin
2024-04-04 0:58 ` Linu Cherian
2024-04-04 0:58 ` Linu Cherian
2024-04-04 13:50 ` Pasha Tatashin
2024-04-04 13:50 ` Pasha Tatashin
2024-04-12 10:10 ` Joerg Roedel
2024-04-12 10:10 ` Joerg Roedel
2024-04-12 17:06 ` Pasha Tatashin
2024-04-12 17:06 ` Pasha Tatashin
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=00555af4-8786-b772-7897-aef1e912b368@google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=alim.akhtar@samsung.com \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=bagasdotme@gmail.com \
--cc=baolu.lu@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw2@infradead.org \
--cc=hannes@cmpxchg.org \
--cc=heiko@sntech.de \
--cc=iommu@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux-tegra@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=m.szyprowski@samsung.com \
--cc=marcan@marcan.st \
--cc=mhiramat@kernel.org \
--cc=mkoutny@suse.com \
--cc=pasha.tatashin@soleen.com \
--cc=paulmck@kernel.org \
--cc=rdunlap@infradead.org \
--cc=robin.murphy@arm.com \
--cc=samuel@sholland.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=sven@svenpeter.dev \
--cc=thierry.reding@gmail.com \
--cc=tj@kernel.org \
--cc=tomas.mudrunka@gmail.com \
--cc=vdumpa@nvidia.com \
--cc=wens@csie.org \
--cc=will@kernel.org \
--cc=yu-cheng.yu@intel.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.