From: Yury Norov <yury.norov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
John Stultz <jstultz@google.com>, Stephen Boyd <sboyd@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 0/3] bitmap: introduce find_random_bit() and use in clocksource
Date: Sat, 21 Jun 2025 10:21:12 -0400 [thread overview]
Message-ID: <aFa_2D584do5p8ne@yury> (raw)
In-Reply-To: <87frfup01o.ffs@tglx>
On Fri, Jun 20, 2025 at 11:37:07PM +0200, Thomas Gleixner wrote:
> On Thu, Jun 19 2025 at 14:26, Yury Norov wrote:
> > nodemasks implement node_random(), which may also be useful for other
> > subsystems. Generalize the function, and propagate to cpumask API.
> >
> > v1: https://lore.kernel.org/all/20250604212125.25656-1-yury.norov@gmail.com/
> > v2: https://lore.kernel.org/all/20250608194536.28130-1-yury.norov@gmail.com/
> > v3: https://lore.kernel.org/all/20250617200854.60753-1-yury.norov@gmail.com/
> > v4: return NUMA_NO_NODES instead of MAX_NUMNODES in node_random() (Andrew)
> >
> > Yury Norov [NVIDIA] (3):
> > bitmap: generalize node_random()
> > cpumask: introduce cpumask_random()
> > clocksource: Improve randomness in clocksource_verify_choose_cpus()
>
> Assuming this goes through the bitmap tree, for the clocksource change:
>
> Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Thanks, applying in bitmap-for-next for testing.
prev parent reply other threads:[~2025-06-21 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 18:26 [PATCH v4 0/3] bitmap: introduce find_random_bit() and use in clocksource Yury Norov
2025-06-19 18:26 ` [PATCH v4 1/3] bitmap: generalize node_random() Yury Norov
2025-06-19 18:26 ` [PATCH v4 2/3] cpumask: introduce cpumask_random() Yury Norov
2025-06-19 18:26 ` [PATCH v4 3/3] clocksource: Improve randomness in clocksource_verify_choose_cpus() Yury Norov
2025-06-20 21:37 ` [PATCH v4 0/3] bitmap: introduce find_random_bit() and use in clocksource Thomas Gleixner
2025-06-21 14:21 ` Yury Norov [this message]
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=aFa_2D584do5p8ne@yury \
--to=yury.norov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
/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