linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/3] ida: Add kunit based tests for new IDA functions
Date: Thu, 2 Nov 2023 21:01:14 +0000	[thread overview]
Message-ID: <ZUQOGl/IQ3MHOkCr@casper.infradead.org> (raw)
In-Reply-To: <f6cd1d42-b901-40a9-9da6-004aaebfc4b9@intel.com>

On Thu, Nov 02, 2023 at 09:58:07PM +0100, Michal Wajdeczko wrote:
> > Why would using kunit be superior to the existing test suite?
> 
> As said above IMO it's just a nice tool, that seems to be already used
> around.  If you look for examples where kunit could win over existing
> ida test suite, then maybe that kunit allows to run only specific test
> cases or parametrize test cases or provide ready to use nicer diagnostic
> messages on missed expectations.  It should also be easy (and can be
> done in unified way) to replace some external functions to trigger
> desired faults (like altering kzalloc() or xas_store() to force
> different code paths during our alloc).
> 
> But since I'm a guest here, knowing that there could be different
> opinions on competing test suites, we can either drop this patch or
> convert new test cases with 'group' variants to the old test_ida suite
> (if that's really desired).

AFAIK, kunit can't be used to extract the in-kernel IDA code and run it
in userspace like the current testsuite does (the current testsuite also
runs in-kernel, except for the multithreaded tests).  So unless it has
that functionality, it seems like a regression to convert the existing
test-suite to kunit.

  reply	other threads:[~2023-11-02 21:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 15:34 [PATCH 0/3] ida: Allow allocations of contiguous IDs Michal Wajdeczko
2023-11-02 15:34 ` [PATCH 1/3] ida: Introduce ida_weight() Michal Wajdeczko
2023-11-02 17:46   ` Matthew Wilcox
2023-11-02 19:05     ` Michal Wajdeczko
2024-01-09 20:52     ` Michal Wajdeczko
2023-11-02 15:34 ` [PATCH 2/3] ida: Introduce ida_alloc_group_range() Michal Wajdeczko
2024-01-09 20:58   ` Michal Wajdeczko
2023-11-02 15:34 ` [PATCH 3/3] ida: Add kunit based tests for new IDA functions Michal Wajdeczko
2023-11-02 17:43   ` Matthew Wilcox
2023-11-02 18:58     ` Michal Wajdeczko
2023-11-02 19:12       ` Matthew Wilcox
2023-11-02 20:58         ` Michal Wajdeczko
2023-11-02 21:01           ` Matthew Wilcox [this message]
2023-11-02 21:33             ` 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=ZUQOGl/IQ3MHOkCr@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=michal.wajdeczko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).