From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Latypov <dlatypov@google.com>,
brendanhiggins@google.com, davidgow@google.com
Cc: linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, skhan@linuxfoundation.org,
Daniel Latypov <dlatypov@google.com>
Subject: Re: [PATCH] lib/atomic64_test.c: convert to use KUnit
Date: Fri, 13 May 2022 13:05:31 +1000 [thread overview]
Message-ID: <87ilqa6sjo.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20220502192327.81153-1-dlatypov@google.com>
Daniel Latypov <dlatypov@google.com> writes:
> The test currently is a bunch of checks (implemented using BUG_ON())
> that can be built into the kernel or as a module.
>
> Convert it to a KUnit test, which can also run in both modes.
> From a user's perspective, this change adds a CONFIG_KUNIT=y dep and
> changes the output format of the test [1]. The test itself is the same.
...
I don't know why I got Cc'ed on this :), but I gave it a quick test anyway.
Seems to work fine on a Power9.
I also flipped some of the conditionals to make sure failure is detected
correctly.
Tested-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
> Meta:
> 1. this patch applies on top of the kunit branch,
> https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git/?h=kunit
>
> 2. checkpatch complains about aligning with parens, but it wants me to
> indent the `#ifdef CONFIG_X86_64` which seems inappropriate in context.
>
> 3. this file doesn't seem to have a clear maintainer, so I assume this
> conversion is fine to go through the kunit branch.
I think you want to at least Cc the atomic folks:
ATOMIC INFRASTRUCTURE
M: Will Deacon <will@kernel.org>
M: Peter Zijlstra <peterz@infradead.org>
R: Boqun Feng <boqun.feng@gmail.com>
R: Mark Rutland <mark.rutland@arm.com>
L: linux-kernel@vger.kernel.org
S: Maintained
cheers
next prev parent reply other threads:[~2022-05-13 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 19:23 [PATCH] lib/atomic64_test.c: convert to use KUnit Daniel Latypov
2022-05-03 6:13 ` David Gow
2022-05-12 18:52 ` Brendan Higgins
2022-05-13 3:05 ` Michael Ellerman [this message]
2022-05-13 16:25 ` Daniel Latypov
-- strict thread matches above, loose matches on Subject: below --
2022-06-16 18:04 Daniel Latypov
2022-06-17 8:02 ` David Gow
2022-06-18 8:16 ` kernel test robot
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=87ilqa6sjo.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=dlatypov@google.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.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