Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Gabriele Monaco <gmonaco@redhat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Shuah Khan <shuah@kernel.org>, Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v5 3/3] rseq/selftests: Add test for mm_cid compaction
Date: Tue, 18 Feb 2025 16:45:58 -0700	[thread overview]
Message-ID: <60671af0-204d-413e-9b65-00b526764ab9@linuxfoundation.org> (raw)
In-Reply-To: <2c2ee65283893a433ac4488f3d048b0f7454be24.camel@redhat.com>

On 2/10/25 08:25, Gabriele Monaco wrote:
> 
> 
> On Mon, 2025-02-10 at 15:53 +0100, Mathieu Desnoyers wrote:
>> On 2025-02-10 08:57, Gabriele Monaco wrote:
>>> A task in the kernel (task_mm_cid_work) runs somewhat periodically
>>> to
>>> compact the mm_cid for each process. Add a test to validate that it
>>> runs
>>> correctly and timely.
>>>
>>> The test spawns 1 thread pinned to each CPU, then each thread,
>>> including
>>> the main one, runs in short bursts for some time. During this
>>> period, the
>>> mm_cids should be spanning all numbers between 0 and nproc.
>>>
>>> At the end of this phase, a thread with high enough mm_cid (>=
>>> nproc/2)
>>> is selected to be the new leader, all other threads terminate.
>>>
>>> After some time, the only running thread should see 0 as mm_cid, if
>>> that
>>> doesn't happen, the compaction mechanism didn't work and the test
>>> fails.
>>>
>>> The test never fails if only 1 core is available, in which case, we
>>> cannot test anything as the only available mm_cid is 0.
>>>
>>> To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>
>> Reviewed-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
>>
>> tiny nit below:
>>
>>> +		usleep(RUNNER_PERIOD);
>>> +	curr_mm_cid = rseq_current_mm_cid();
>>> +	/*
>>> +	 * We select one thread with high enough mm_cid to be the
>>> new leader
>>
>> Missing punctuation here (...new leader.  All other...)
> 
> I guess I'm allergic to those ;) Thanks for finding it!
> I wonder if checkpatch should be able to catch this kind of problem,
> but that's for another day.
> 
> Do I need to send a v6 for this or just reply here with the fixed
> patch?

Please send v6 with the suggested changes. Also change the commit
summary to

"selftests/rseq"

thanks,
-- Shuah

  reply	other threads:[~2025-02-18 23:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250210075703.79125-1-gmonaco@redhat.com>
2025-02-10  7:57 ` [PATCH v5 3/3] rseq/selftests: Add test for mm_cid compaction Gabriele Monaco
2025-02-10 14:53   ` Mathieu Desnoyers
2025-02-10 15:25     ` Gabriele Monaco
2025-02-18 23:45       ` Shuah Khan [this message]
2025-02-19 10:28         ` Gabriele Monaco

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=60671af0-204d-413e-9b65-00b526764ab9@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=gmonaco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=shuah@kernel.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