From: luferry <luferry@163.com>
To: "Thomas Gleixner" <tglx@linutronix.de>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
"Rik van Riel" <riel@surriel.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Josh Poimboeuf" <jpoimboe@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re:Re: [PATCH v2] smp: avoid generic_exec_single cause system lockup
Date: Thu, 18 Jul 2019 16:50:52 +0800 (CST) [thread overview]
Message-ID: <5f5fbd7.1073c.16c0446ea63.Coremail.luferry@163.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1907181007340.1778@nanos.tec.linutronix.de>
At 2019-07-18 16:07:58, "Thomas Gleixner" <tglx@linutronix.de> wrote:
>On Thu, 18 Jul 2019, luferry@163.com wrote:
>
>> From: luferry <luferry@163.com>
>>
>> The race can reproduced by sending wait enabled IPI in softirq/irq env
>
>Which code path is doing that?
>
>Thanks,
>
> tglx
Thanks for your kindly reply.
I checked kernel and found no code path can run into this.
Actually , i encounter with this problem by my own code.
I need to do some specific urgent work periodicity and these
work may run for quite a while. So i can't disable irq during these work
which stops me from using hrtimer to do this. So i did add an extra
sofitrq action which may invoke smp_call.
next prev parent reply other threads:[~2019-07-18 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 8:03 luferry
2019-07-18 8:07 ` Thomas Gleixner
2019-07-18 8:50 ` luferry [this message]
2019-07-18 9:58 ` Thomas Gleixner
2019-07-18 16:06 ` Peter Zijlstra
2019-07-18 18:17 ` Thomas Gleixner
2019-07-20 9:31 ` [tip:smp/urgent] smp: Warn on function calls from softirq context tip-bot for Peter Zijlstra
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=5f5fbd7.1073c.16c0446ea63.Coremail.luferry@163.com \
--to=luferry@163.com \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--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
Powered by JetHome