linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linaro-kernel@lists.linaro.org,
	Build bot for Mark Brown <broonie@kernel.org>,
	kernel-build-reports@lists.linaro.org,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v4.4.12-rt20 build: 0 failures 5 warnings (v4.4.12-rt20)
Date: Fri, 29 Jul 2016 17:23:58 +0200	[thread overview]
Message-ID: <20160729152358.GC21715@linutronix.de> (raw)
In-Reply-To: <77528485.4aTSS092zh@wuerfel>

* Arnd Bergmann | 2016-07-15 21:48:55 [+0200]:

>I also notice that your "tty: serial: 8250: don't take the trylock
>during oops" patch would apply on the pl011 driver as well.

That one. That is something I am not really sure about in the long run. On
-RT we can't try_lock() with IRQs off and that is why I removed it.
You could do the same with pl011 but you are screwed anyway because
clk_enable() will take a sleeping lock and that is a no no.

So you could stay with the try_lock because it does not solve anything.
In the long run I though about a console flag which denotes the console
as RT-IRQ save which is the case for 8250 but not for pl011 (due to
clk_enable()) so should not get on -RT into this case where it matters.

On the other hand if you oops on !RT+UP in your uart driver while
holding the lock then the try_lock will fail resulting in a lockdep
splat (because try_lock should not fail on UP). So might want take it as
a procation in that case :)

>Sure, that always works, it's just a bit ugly since the flags word
>should never be zero when it gets written back to the hardware irq
>state, at least in portable code.

yes :)

>Maybe something like the version below?

sure.

Sebastian

      reply	other threads:[~2016-07-29 15:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1bNugf-00064t-KA@optimist>
2016-07-15  7:07 ` v4.4.12-rt20 build: 0 failures 5 warnings (v4.4.12-rt20) Arnd Bergmann
2016-07-15 12:05   ` Sebastian Andrzej Siewior
2016-07-15 12:29     ` Arnd Bergmann
2016-07-15 13:23       ` Sebastian Andrzej Siewior
2016-07-15 19:48         ` Arnd Bergmann
2016-07-29 15:23           ` Sebastian Andrzej Siewior [this message]

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=20160729152358.GC21715@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).