From: Thomas Gleixner <tglx@linutronix.de>
To: Vincent Guittot <vincent.guittot@linaro.org>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: vschneid@redhat.com, Phil Auld <pauld@redhat.com>,
vdonnefort@google.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Wei Li <liwei391@huawei.com>, "liaoyu (E)" <liaoyu15@huawei.com>,
zhangqiao22@huawei.com, Peter Zijlstra <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [Question] report a race condition between CPU hotplug state machine and hrtimer 'sched_cfs_period_timer' for cfs bandwidth throttling
Date: Wed, 28 Jun 2023 23:09:56 +0200 [thread overview]
Message-ID: <87zg4j2t0b.ffs@tglx> (raw)
In-Reply-To: <CAKfTPtDZN1gVgr0AqgtVe3arVWEtA35PA3PL99hT_WAR1D9S9g@mail.gmail.com>
On Wed, Jun 28 2023 at 15:30, Vincent Guittot wrote:
> On Tue, 27 Jun 2023 at 18:46, Vincent Guittot
>> > > + struct hrtimer_clock_base *clock_base = cfs_b->period_timer.base;
>> > > + int cpu = clock_base->cpu_base->cpu;
>> > > + if (!cpu_active(cpu) && cpu != smp_processor_id())
>> > > + hrtimer_start_expires(&cfs_b->period_timer,
>> > > HRTIMER_MODE_ABS_PINNED);
>> > > return;
>> > > + }
Can you please trim your replies?
>> I have been able to reproduce your problem and run your fix on top. I
>> still wonder if there is a
>
> Looks like I have been preempted and never finished the sentence. The
> full sentence is:
> I still wonder if there is a race condition where the hang can still
> happen but i haven't been able to find one so far
As I explained before. Assume the timer fires on the outgoing CPU and
the other CPU tries to rearm it concurrently. It will stay on the
outgoing CPU and not move over.
Thanks,
tglx
next prev parent reply other threads:[~2023-06-28 21:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:24 [Question] report a race condition between CPU hotplug state machine and hrtimer 'sched_cfs_period_timer' for cfs bandwidth throttling Xiongfeng Wang
2023-06-09 14:55 ` Thomas Gleixner
2023-06-12 12:49 ` Xiongfeng Wang
2023-06-26 8:23 ` Xiongfeng Wang
2023-06-27 16:46 ` Vincent Guittot
2023-06-28 12:03 ` Thomas Gleixner
2023-06-28 12:35 ` Vincent Guittot
2023-06-28 22:01 ` Thomas Gleixner
2023-06-29 1:41 ` Xiongfeng Wang
2023-06-29 8:30 ` Vincent Guittot
2023-08-22 8:58 ` Xiongfeng Wang
2023-08-23 10:14 ` Thomas Gleixner
2023-08-24 7:25 ` Yu Liao
2023-08-29 7:18 ` Vincent Guittot
2023-06-28 13:30 ` Vincent Guittot
2023-06-28 21:09 ` Thomas Gleixner [this message]
2023-06-29 1:26 ` Xiongfeng Wang
2023-06-29 8:33 ` Vincent Guittot
2023-08-30 10:29 ` [tip: smp/urgent] cpu/hotplug: Prevent self deadlock on CPU hot-unplug tip-bot2 for Thomas Gleixner
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=87zg4j2t0b.ffs@tglx \
--to=tglx@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=liaoyu15@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=mingo@kernel.org \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=vdonnefort@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wangxiongfeng2@huawei.com \
--cc=zhangqiao22@huawei.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