From: Benjamin Berg <benjamin@sipsolutions.net>
To: David Gow <davidgow@google.com>,
Matti Vaittinen <mazziesaccount@gmail.com>,
Maxime Ripard <maxime@cerno.tech>,
Brendan Higgins <brendan.higgins@linux.dev>,
Stephen Boyd <sboyd@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Daniel Latypov <dlatypov@google.com>, Rae Moar <rmoar@google.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Jonathan Cameron <jic23@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
kunit-dev@googlegroups.com
Subject: Re: [PATCH v1 0/3] kunit: Deferred action helpers
Date: Mon, 24 Apr 2023 14:32:16 +0200 [thread overview]
Message-ID: <54b49d4ddf371d0581f3b795f50f7f6673557a96.camel@sipsolutions.net> (raw)
In-Reply-To: <20230421084226.2278282-1-davidgow@google.com>
On Fri, 2023-04-21 at 16:42 +0800, 'David Gow' via KUnit Development wrote:
> This is v1 of the KUnit deferred actions API, which implements an
> equivalent of devm_add_action[1] on top of KUnit managed resources. This
> provides a simple way of scheduling a function to run when the test
> terminates (whether successfully, or with an error). It's therefore very
> useful for freeing resources, or otherwise cleaning up.
>
> The notable changes since RFCv2[2] are:
> - Got rid of the 'cancellation token' concept. It was overcomplicated,
> and we can add it back if we need to.
> - kunit_add_action() therefore now returns 0 on success, and an error
> otherwise (like devm_add_action()). Though you may wish to use:
> - Added kunit_add_action_or_reset(), which will call the deferred
> function if an error occurs. (See devm_add_action_or_reset()). This
> also returns an error on failure, which can be asserted safely.
> - Got rid of the function pointer typedef. Personally, I liked it, but
> it's more typedef-y than most kernel code.
> - Got rid of the 'internal_gfp' argument: all internal state is now
> allocated with GFP_KERNEL. The main KUnit resource API can be used
> instead if this doesn't work for your use-case.
>
> I'd love to hear any further thoughts!
I am happy with it as-is.
Reviewed-By: Benjamin Berg <benjamin.berg@intel.com>
>
> Cheers,
> -- David
>
> [1]: https://docs.kernel.org/driver-api/basics.html#c.devm_add_action
> [2]: https://patchwork.kernel.org/project/linux-kselftest/list/?series=735720
>
>
> David Gow (3):
> kunit: Add kunit_add_action() to defer a call until test exit
> kunit: executor_test: Use kunit_add_action()
> kunit: kmalloc_array: Use kunit_add_action()
>
> include/kunit/resource.h | 76 +++++++++++++++++++++++++++++++
> include/kunit/test.h | 10 ++++-
> lib/kunit/executor_test.c | 11 ++---
> lib/kunit/kunit-test.c | 88 +++++++++++++++++++++++++++++++++++-
> lib/kunit/resource.c | 95 +++++++++++++++++++++++++++++++++++++++
> lib/kunit/test.c | 48 ++++----------------
> 6 files changed, 279 insertions(+), 49 deletions(-)
>
> --
> 2.40.0.634.g4ca3ef3211-goog
>
next prev parent reply other threads:[~2023-04-24 12:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 8:42 David Gow
2023-04-21 8:42 ` [PATCH v1 1/3] kunit: Add kunit_add_action() to defer a call until test exit David Gow
2023-04-26 2:12 ` Daniel Latypov
2023-04-26 6:59 ` David Gow
2023-04-21 8:42 ` [PATCH v1 2/3] kunit: executor_test: Use kunit_add_action() David Gow
2023-04-21 8:42 ` [PATCH v1 3/3] kunit: kmalloc_array: " David Gow
2023-04-24 12:32 ` Benjamin Berg [this message]
2023-04-24 14:02 ` [PATCH v1 0/3] kunit: Deferred action helpers Benjamin Berg
2023-04-26 6:51 ` David Gow
2023-04-25 15:23 ` Maxime Ripard
2023-04-26 6:51 ` David Gow
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=54b49d4ddf371d0581f3b795f50f7f6673557a96.camel@sipsolutions.net \
--to=benjamin@sipsolutions.net \
--cc=brendan.higgins@linux.dev \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jic23@kernel.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maxime@cerno.tech \
--cc=mazziesaccount@gmail.com \
--cc=rafael@kernel.org \
--cc=rmoar@google.com \
--cc=sboyd@kernel.org \
--cc=skhan@linuxfoundation.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®