From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Rae Moar <rmoar@google.com>
Cc: linux-kselftest@vger.kernel.org, kunit-dev@googlegroups.com,
David Gow <davidgow@google.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH v2 3/6] kunit: Add macro to conditionally expose expressions to tests
Date: Tue, 27 Aug 2024 21:47:43 +0200 [thread overview]
Message-ID: <fe0b8cd7-583c-4a2d-a61d-18484c3197bf@intel.com> (raw)
In-Reply-To: <CA+GJov4dfR=Cv7uRhPqw3P3XP==rntYWzgCKJ_7O4AcfwD--qw@mail.gmail.com>
On 27.08.2024 21:04, Rae Moar wrote:
> On Mon, Aug 26, 2024 at 3:20 PM Michal Wajdeczko
> <michal.wajdeczko@intel.com> wrote:
>>
>> The ONLY_IF_KUNIT macro will add expression statement only if the
>> CONFIG_KUNIT is enabled. Otherwise if CONFIG_KUNIT is not enabled
>> it will evaluate always to 0.
>>
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> Hello!
>
> Thanks for the second version of this patch series!
>
> I definitely could see this new macro as being useful but I currently
> don't see an example of its use in the rest of the patch series. How
> do you see this macro as being used or do you have a current use case
> for this macro?
in Xe driver we have this macro defined as XE_TEST_ONLY [1]
[1] https://elixir.bootlin.com/linux/v6.11-rc5/A/ident/XE_TEST_ONLY
>
> I would be fine adding this macro without being used as long as
> examples on how and why to use it are clearly documented.
sure, I'll try to add some usage in the example patch 5/6
>
> Thanks!
> -Rae
>
>> ---
>> Cc: Rae Moar <rmoar@google.com>
>> Cc: David Gow <davidgow@google.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> ---
>> include/kunit/visibility.h | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/include/kunit/visibility.h b/include/kunit/visibility.h
>> index 1c23773f826c..69c71eacf368 100644
>> --- a/include/kunit/visibility.h
>> +++ b/include/kunit/visibility.h
>> @@ -18,6 +18,13 @@
>> * @body: identifiers to be introduced conditionally
>> */
>> #define DECLARE_IF_KUNIT(body...) body
>> + /**
>> + * ONLY_IF_KUNIT - A macro that adds expression statement only if
>> + * CONFIG_KUNIT is enabled. Otherwise if CONFIG_KUNIT is not enabled
>> + * it will evaluate always to 0.
>> + * @expr: expression to be introduced conditionally
>> + */
>> + #define ONLY_IF_KUNIT(expr...) expr
>> /**
>> * VISIBLE_IF_KUNIT - A macro that sets symbols to be static if
>> * CONFIG_KUNIT is not enabled. Otherwise if CONFIG_KUNIT is enabled
>> @@ -34,6 +41,7 @@
>> EXPORTED_FOR_KUNIT_TESTING)
>> #else
>> #define DECLARE_IF_KUNIT(body...)
>> + #define ONLY_IF_KUNIT(expr...) 0
>> #define VISIBLE_IF_KUNIT static
>> #define EXPORT_SYMBOL_IF_KUNIT(symbol)
>> #endif
>> --
>> 2.43.0
>>
next prev parent reply other threads:[~2024-08-27 19:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 22:20 [PATCH v2 0/6] kunit: Add macros to help write more complex tests Michal Wajdeczko
2024-08-26 22:20 ` [PATCH v2 1/6] kunit: Introduce kunit_is_running() Michal Wajdeczko
2024-08-26 22:20 ` [PATCH v2 2/6] kunit: Add macro to conditionally expose declarations to tests Michal Wajdeczko
2024-08-27 13:45 ` Lucas De Marchi
2024-08-27 19:56 ` Michal Wajdeczko
2024-08-26 22:20 ` [PATCH v2 3/6] kunit: Add macro to conditionally expose expressions " Michal Wajdeczko
2024-08-27 19:04 ` Rae Moar
2024-08-27 19:47 ` Michal Wajdeczko [this message]
2024-08-26 22:20 ` [PATCH v2 4/6] kunit: Allow function redirection outside of the KUnit thread Michal Wajdeczko
2024-08-27 14:46 ` Lucas De Marchi
2024-08-27 20:30 ` Michal Wajdeczko
2024-08-29 15:56 ` Michal Wajdeczko
2024-08-26 22:20 ` [PATCH v2 5/6] kunit: Add example with alternate function redirection method Michal Wajdeczko
2024-08-27 14:18 ` Lucas De Marchi
2024-08-26 22:20 ` [PATCH v2 6/6] kunit: Add some selftests for global stub redirection macros Michal Wajdeczko
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=fe0b8cd7-583c-4a2d-a61d-18484c3197bf@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=davidgow@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=rmoar@google.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