From: Rob Herring <robh@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Maxime Ripard <maxime@cerno.tech>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Brendan Higgins <brendan.higgins@linux.dev>,
Rae Moar <rmoar@google.com>,
linux-kselftest@vger.kernel.org, David Gow <davidgow@google.com>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-kernel@vger.kernel.org,
"Rafael J . Wysocki" <rafael@kernel.org>,
kunit-dev@googlegroups.com, patches@lists.linux.dev,
linux-clk@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Saravana Kannan <saravanak@google.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Daniel Latypov <dlatypov@google.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 01/10] of: Add test managed wrappers for of_overlay_apply()/of_node_put()
Date: Tue, 23 Apr 2024 10:05:30 -0500 [thread overview]
Message-ID: <171388470076.215446.15104256542666415343.robh@kernel.org> (raw)
In-Reply-To: <20240422232404.213174-2-sboyd@kernel.org>
On Mon, 22 Apr 2024 16:23:54 -0700, Stephen Boyd wrote:
> Add test managed wrappers for of_overlay_apply() that automatically
> removes the overlay when the test is finished. This API is intended for
> use by KUnit tests that test code which relies on 'struct device_node's
> and of_*() APIs.
>
> KUnit tests will call of_overlay_apply_kunit() to load an overlay that's
> been built into the kernel image. When the test is complete, the overlay
> will be removed.
>
> This has a few benefits:
>
> 1) It keeps the tests hermetic because the overlay is removed when the
> test is complete. Tests won't even be aware that an overlay was
> loaded in another test.
>
> 2) The overlay code can live right next to the unit test that loads it.
> The overlay and the unit test can be compiled into one kernel module
> if desired.
>
> 3) We can test different device tree configurations by loading
> different overlays. The overlays can be written for a specific test,
> and there can be many of them loaded per-test without needing to jam
> all possible combinations into one DTB.
>
> 4) It also allows KUnit to test device tree dependent code on any
> architecture, not just UML. This allows KUnit tests to test
> architecture specific device tree code.
>
> There are some potential pitfalls though. Test authors need to be
> careful to not overwrite properties in the live tree. The easiest way to
> do this is to add and remove nodes with a 'kunit-' prefix, almost
> guaranteeing that the same node won't be present in the tree loaded at
> boot.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Cc: Saravana Kannan <saravanak@google.com>
> Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> ---
> Documentation/dev-tools/kunit/api/index.rst | 11 +++
> Documentation/dev-tools/kunit/api/of.rst | 13 +++
> drivers/of/Makefile | 1 +
> drivers/of/of_kunit.c | 99 +++++++++++++++++++++
> include/kunit/of.h | 94 +++++++++++++++++++
> 5 files changed, 218 insertions(+)
> create mode 100644 Documentation/dev-tools/kunit/api/of.rst
> create mode 100644 drivers/of/of_kunit.c
> create mode 100644 include/kunit/of.h
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2024-04-23 15:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 23:23 [PATCH v4 00/10] clk: Add kunit tests for fixed rate and parent data Stephen Boyd
2024-04-22 23:23 ` [PATCH v4 01/10] of: Add test managed wrappers for of_overlay_apply()/of_node_put() Stephen Boyd
2024-04-23 15:05 ` Rob Herring [this message]
2024-05-01 7:55 ` David Gow
2024-05-03 0:36 ` Stephen Boyd
2024-05-04 8:30 ` David Gow
2024-04-22 23:23 ` [PATCH v4 02/10] dt-bindings: vendor-prefixes: Add "test" vendor for KUnit and friends Stephen Boyd
2024-05-01 7:55 ` David Gow
2024-04-22 23:23 ` [PATCH v4 03/10] dt-bindings: test: Add KUnit empty node binding Stephen Boyd
2024-05-01 7:55 ` David Gow
2024-05-02 21:23 ` Brendan Higgins
2024-04-22 23:23 ` [PATCH v4 04/10] of: Add a KUnit test for overlays and test managed APIs Stephen Boyd
2024-04-23 15:07 ` Rob Herring
2024-04-22 23:23 ` [PATCH v4 05/10] platform: Add test managed platform_device/driver APIs Stephen Boyd
2024-04-24 18:11 ` Stephen Boyd
2024-04-30 21:32 ` Stephen Boyd
2024-05-01 7:55 ` David Gow
2024-05-03 1:03 ` Stephen Boyd
2024-05-04 8:30 ` David Gow
2024-05-10 20:12 ` Stephen Boyd
2024-05-14 3:35 ` Stephen Boyd
2024-04-22 23:23 ` [PATCH v4 06/10] dt-bindings: kunit: Add fixed rate clk consumer test Stephen Boyd
2024-06-03 22:02 ` Stephen Boyd
2024-04-22 23:24 ` [PATCH v4 07/10] clk: Add test managed clk provider/consumer APIs Stephen Boyd
2024-04-22 23:24 ` [PATCH v4 08/10] clk: Add KUnit tests for clk fixed rate basic type Stephen Boyd
2024-04-22 23:24 ` [PATCH v4 09/10] dt-bindings: clk: Add KUnit clk_parent_data test Stephen Boyd
2024-04-22 23:24 ` [PATCH v4 10/10] clk: Add KUnit tests for clks registered with struct clk_parent_data Stephen Boyd
2024-05-01 8:08 ` [PATCH v4 00/10] clk: Add kunit tests for fixed rate and parent data David Gow
2024-05-03 1:27 ` Stephen Boyd
2024-05-14 21:29 ` Stephen Boyd
2024-05-15 13:06 ` Rob Herring
2024-05-15 21:15 ` Stephen Boyd
2024-05-15 22:08 ` Rob Herring
2024-05-17 0:33 ` Stephen Boyd
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=171388470076.215446.15104256542666415343.robh@kernel.org \
--to=robh@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=brendan.higgins@linux.dev \
--cc=conor+dt@kernel.org \
--cc=davidgow@google.com \
--cc=devicetree@vger.kernel.org \
--cc=dlatypov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rmoar@google.com \
--cc=saravanak@google.com \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®