From: Thomas Gleixner <tglx@linutronix.de>
To: Costa Shulyupin <costa.shul@redhat.com>, linux-kernel@vger.kernel.org
Cc: Costa Shulyupin <costa.shul@redhat.com>,
Waiman Long <longman@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v3] hrtimer: select housekeeping CPU during migration
Date: Mon, 19 Feb 2024 17:27:24 +0100 [thread overview]
Message-ID: <875xykju6r.ffs@tglx> (raw)
In-Reply-To: <20240219143301.4174966-1-costa.shul@redhat.com>
Costa!
On Mon, Feb 19 2024 at 16:33, Costa Shulyupin wrote:
> During CPU-down hotplug, hrtimers may migrate to isolated CPUs,
> compromising CPU isolation. This commit addresses this issue by
> masking valid CPUs for hrtimers using housekeeping_cpumask(HK_TYPE_TIMER).
Review feedback is meant to be addressed. I fixed it up for you in V2
and told you what needs to be changed and you got the fixed up version
in your inbox. Feel free to ignore me, but don't expect me to mop up
your stuff.
Thanks,
tglx
next prev parent reply other threads:[~2024-02-19 16:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 13:52 [PATCH] hrtimer: select housekeeping CPU during migration Costa Shulyupin
2024-02-11 16:37 ` Waiman Long
2024-02-12 15:23 ` Frederic Weisbecker
2024-02-13 12:36 ` Thomas Gleixner
2024-02-13 16:46 ` [PATCH v2] " Costa Shulyupin
2024-02-13 19:41 ` Thomas Gleixner
2024-02-13 19:49 ` [tip: timers/core] hrtimer: Select " tip-bot2 for Costa Shulyupin
2024-02-14 9:01 ` [PATCH v2] hrtimer: select " Borislav Petkov
2024-02-14 9:10 ` Thomas Gleixner
2024-02-19 14:33 ` [PATCH v3] " Costa Shulyupin
2024-02-19 16:27 ` Thomas Gleixner [this message]
2024-02-22 20:08 ` [PATCH v4] " Costa Shulyupin
2024-02-22 21:24 ` [tip: timers/core] hrtimer: Select " tip-bot2 for Costa Shulyupin
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=875xykju6r.ffs@tglx \
--to=tglx@linutronix.de \
--cc=costa.shul@redhat.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.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