From: Johan Hovold <johan@kernel.org>
To: Erwan LE RAY <erwan.leray@foss.st.com>
Cc: dillon min <dillon.minfei@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
jirislaby@kernel.org, Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@foss.st.com>,
kernel test robot <lkp@intel.com>,
linux-serial@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
Gerald Baeza <gerald.baeza@foss.st.com>
Subject: Re: [PATCH v2] serial: stm32: optimize spin lock usage
Date: Fri, 16 Apr 2021 10:51:09 +0200 [thread overview]
Message-ID: <YHlP/SryZXr/nNLM@hovoldconsulting.com> (raw)
In-Reply-To: <e17fddfb-f9b8-238f-da74-a4746f33134f@foss.st.com>
[ Please avoid top-posting. ]
On Thu, Apr 15, 2021 at 07:09:14PM +0200, Erwan LE RAY wrote:
> Hi Dillon,
>
> STM32MP151 is mono-core, but both STM32MP153 and STM32MP157 are
> dual-core (see
> https://www.st.com/content/st_com/en/products/microcontrollers-microprocessors/stm32-arm-cortex-mpus.html).
> So your point is fully relevant, thanks.
>
> ST already fixed the same issue in st-asc.c driver in the past (see
> ef49ffd8), because a systematic deadlock was detected with RT kernel.
That's not the same issue. The above mentioned commit fixed an issue on
*RT* where local_irq_save() should be avoided.
> You proposed a first implementation in your patch, and a second one in
> the discussion. It seems that your initial proposal (ie your V2 patch)
> is the most standard one (implemented in 6 drivers). The second
> implementation is implemented by only 1 company.
>
> It looks that the solution is to avoid locking in the sysrq case and
> trylock in the oops_in_progress case (see detailed analysis in
> 677fe555cbfb1).
>
> So your initial patch looks to the right proposal, but it would be safer
> if Greg could confirm it.
That would only fix the RT issue (and by making the sysrq one slightly
worse).
Using uart_unlock_and_check_sysrq() would address both issues.
Johan
next prev parent reply other threads:[~2021-04-16 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 9:31 [PATCH v2] serial: stm32: optimize spin lock usage dillon.minfei
2021-04-12 13:08 ` Johan Hovold
2021-04-12 14:04 ` dillon min
2021-04-12 23:44 ` dillon min
2021-04-15 17:09 ` Erwan LE RAY
2021-04-16 0:06 ` Hua Dillon
2021-04-16 8:51 ` Johan Hovold [this message]
2021-04-16 8:35 ` Johan Hovold
2021-04-16 8:56 ` dillon min
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=YHlP/SryZXr/nNLM@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dillon.minfei@gmail.com \
--cc=erwan.leray@foss.st.com \
--cc=gerald.baeza@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lkp@intel.com \
--cc=mcoquelin.stm32@gmail.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