From: Thomas Gleixner <tglx@linutronix.de>
To: Hillf Danton <hdanton@sina.com>
Cc: Thomas Pfaff <tpfaff@pcs.com>,
linux-kernel@vger.kernel.org, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v3] irq/core: synchronize irq_thread startup
Date: Tue, 03 May 2022 09:38:01 +0200 [thread overview]
Message-ID: <87pmkvkqw6.ffs@tglx> (raw)
In-Reply-To: <20220503004209.4670-1-hdanton@sina.com>
Hillf,
On Tue, May 03 2022 at 08:42, Hillf Danton wrote:
> On Mon, 02 May 2022 21:24:45 +0200 Thomas Gleixner wrote:
>> On Tue, May 03 2022 at 00:01, Hillf Danton wrote:
>> > + if (!waked)
>> > + wake_threads_waitq(desc);
>>
>> That's a guarantee to make desc->threads_active go negative in the case
>> that the thread was never woken by a hard interrupt handler. IOW, you
>> created a new problem which did not exist before.
>
> The count of active threads would not drop below zero with the change,
> given the comment in __irq_wake_thread(). It is incremented before
> wakeup.
There is no guarantee that the wake-up happens via __irq_wake_thread().
kthread_stop() does a wake-up too, but that obviously _cannot_ increment
the active counter because it does not know about it at all.
create_thread()
thread_fn()
woken = false;
wait_for_wakeup_or_stop() <- Stop is set, no interrupt happened
<- ergo woken == false
if (!woken)
wake_threads_waitq(desc)
atomic_dec_and_test(..) <- underflow
>> The problem discussed here is not a problem in irq_thread(), it's a
>> problem of not reaching this function in the first place. See the on
>> point analysis in Thomas Pfaffs patch.
>
> Well why is the count above zero without wakeup? IOW why is there imbalance
> in count if the irq thread never gets a CPU to run?
Look at kthread() and the condition under which threadfn() is invoked.
Thanks,
tglx
next prev parent reply other threads:[~2022-05-03 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 11:28 [PATCH v3] irq/core: synchronize irq_thread startup Thomas Pfaff
2022-05-02 11:48 ` Marc Zyngier
2022-05-02 14:28 ` Thomas Gleixner
2022-05-02 15:34 ` Thomas Pfaff
2022-05-02 19:00 ` Thomas Gleixner
2022-05-10 8:43 ` Thomas Pfaff
2022-05-10 11:34 ` Thomas Gleixner
2022-05-10 11:37 ` Thomas Gleixner
2022-05-10 12:58 ` Thomas Pfaff
2022-05-02 19:21 ` [tip: irq/urgent] genirq: Synchronize interrupt thread startup tip-bot2 for Thomas Pfaff
[not found] ` <20220502160106.4587-1-hdanton@sina.com>
2022-05-02 19:24 ` [PATCH v3] irq/core: synchronize irq_thread startup Thomas Gleixner
[not found] ` <20220503004209.4670-1-hdanton@sina.com>
2022-05-03 7:38 ` Thomas Gleixner [this message]
2022-05-05 10:01 ` [tip: irq/urgent] genirq: Synchronize interrupt thread startup tip-bot2 for Thomas Pfaff
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=87pmkvkqw6.ffs@tglx \
--to=tglx@linutronix.de \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=tpfaff@pcs.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