From: Gabriele Monaco <gmonaco@redhat.com>
To: Shuah Khan <skhan@linuxfoundation.org>,
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
Subject: Re: [PATCH v5 3/3] rseq/selftests: Add test for mm_cid compaction
Date: Wed, 19 Feb 2025 11:28:57 +0100 [thread overview]
Message-ID: <e74f656e58c1c0a113de87b745a13aeae7370f6f.camel@redhat.com> (raw)
In-Reply-To: <60671af0-204d-413e-9b65-00b526764ab9@linuxfoundation.org>
On Tue, 2025-02-18 at 16:45 -0700, Shuah Khan wrote:
>
> Please send v6 with the suggested changes. Also change the commit
> summary to
>
> "selftests/rseq"
Sure, will do. There was actually a V6 already, so I'm sending a V7.
In the meanwhile there was a discussion about the approach. I'm going
to send as V7 what is closer to the approach in V6.
I opened another series for the other approach (scan in batches), which
we may continue depending on the review of V7.
The test should be mostly independent on the approach though.
Thanks,
Gabriele
next prev parent reply other threads:[~2025-02-19 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250210075703.79125-1-gmonaco@redhat.com>
2025-02-10 7:57 ` [PATCH v5 1/3] sched: Compact RSEQ concurrency IDs with reduced threads and affinity Gabriele Monaco
2025-02-10 7:57 ` [PATCH v5 2/3] sched: Move task_mm_cid_work to mm delayed work Gabriele Monaco
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
2025-02-19 10:28 ` Gabriele Monaco [this message]
2025-02-10 14:56 ` [PATCH v5 0/3] sched: Restructure task_mm_cid_work for predictability Mathieu Desnoyers
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=e74f656e58c1c0a113de87b745a13aeae7370f6f.camel@redhat.com \
--to=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 \
--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
all inboxes | Powered by JetHome®