From: SeongJae Park <sj@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: SeongJae Park <sj@kernel.org>, damon@lists.linux.dev
Subject: Re: Problems running DAMON kunit tests with spinlock debugging enabled
Date: Thu, 5 Sep 2024 09:30:56 -0700 [thread overview]
Message-ID: <20240905163056.74132-1-sj@kernel.org> (raw)
In-Reply-To: <c62934de-001d-4f41-bc00-17244cd04d89@roeck-us.net>
On Wed, 4 Sep 2024 12:06:29 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
> On 9/4/24 10:53, SeongJae Park wrote:
> > On Tue, 3 Sep 2024 19:46:44 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
> >> On 9/3/24 19:24, Guenter Roeck wrote:
> >>> On 9/3/24 18:00, SeongJae Park wrote:
> >>>> Hi Guenter,
> >>>>
> >>>> On Tue, 3 Sep 2024 12:23:50 -0700 Guenter Roeck <linux@roeck-us.net> wrote:
[...]
> >>> Some more problems. I tried your patch on various architectures.
> >>> Unfortunately, that didn't turn out well. See below for some of the failures.
> >
> > Nice finding, thank you for reporting this! Just to be clear, seems this is
> > independent from the originally reported issue or the fix for it. Please let
> > me know if not.
> >
>
> It is a different problem.
Thank you for confirming :)
[...]
> > I think doing the skip if the resulting
> > aggr_interval is zero would make more sense. Having more comments would also
> > be nice.
> >
>
> Sure; the above was not intended to be a final (or even acceptable) fix,
> just a workaround to let me run tests with damon kunit tests enabled
> on 32-bit systems.
Thank you for kindly agreeing and clarifying. I just posted the fix:
https://lore.kernel.org/20240905162423.74053-1-sj@kernel.org
Hopefully the patch explains more details and my opinions.
Thanks,
SJ
>
> Thanks,
> Guenter
next prev parent reply other threads:[~2024-09-05 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 19:23 Problems running DAMON kunit tests with spinlock debugging enabled Guenter Roeck
2024-09-04 1:00 ` SeongJae Park
2024-09-04 2:24 ` Guenter Roeck
2024-09-04 2:46 ` Guenter Roeck
2024-09-04 17:53 ` SeongJae Park
2024-09-04 19:06 ` Guenter Roeck
2024-09-05 16:30 ` SeongJae Park [this message]
2024-09-04 21:04 ` Guenter Roeck
2024-09-05 17:35 ` SeongJae Park
2024-09-05 18:04 ` Guenter Roeck
2024-09-05 18:08 ` SeongJae Park
2024-09-05 6:14 ` SeongJae Park
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=20240905163056.74132-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=linux@roeck-us.net \
/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