From: Andrew Morton <akpm@linux-foundation.org>
To: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-alpha@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Richard Henderson <rth@twiddle.net>,
Matt Turner <mattst88@gmail.com>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: [PATCH REPOST] alpha: Replace bogus in_interrupt()
Date: Sat, 14 Nov 2020 10:39:35 -0800 [thread overview]
Message-ID: <20201114103935.6b7d0f55e2cd6dce536d304f@linux-foundation.org> (raw)
In-Reply-To: <87o8k0icsr.fsf@depni.sinp.msu.ru>
On Sat, 14 Nov 2020 11:05:08 +0300 Serge Belyshev <belyshev@depni.sinp.msu.ru> wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
> > On Fri, 13 Nov 2020 14:58:32 +0100 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> >
> >> From: Thomas Gleixner <tglx@linutronix.de>
> >>
> >> in_interrupt() is true for a variety of things including bottom half
> >> disabled regions. Deducing hard interrupt context from it is dubious at
> >> best.
> >>
> >> Use in_irq() which is true if called in hard interrupt context. Otherwise
> >> calling irq_exit() would do more harm than good.
> >>
> >
> > Gee, how to test it. Does anyone run current kernels on alpha?
>
> Hold my beer:
>
> --- a/arch/alpha/kernel/process.c
> +++ b/arch/alpha/kernel/process.c
> @@ -134,8 +134,10 @@ common_shutdown_1(void *generic_ptr)
> #ifdef CONFIG_DUMMY_CONSOLE
> /* If we've gotten here after SysRq-b, leave interrupt
> context before taking over the console. */
> - if (in_irq())
> + if (in_irq()) {
> + printk ("in_irq(): true\n");
> irq_exit();
> + }
> /* This has the effect of resetting the VGA video origin. */
> console_lock();
> do_take_over_console(&dummy_con, 0, MAX_NR_CONSOLES-1, 1);
>
>
> and then sysrq-b over serial console:
>
> [ 56.531250] sysrq: Resetting
> [ 56.531250] in_irq(): true
> [ 56.531250] Console: switching to colour dummy device 80x25
>
> halted CPU 0
>
> halt code = 5
> HALT instruction executed
> PC = fffffc0000310040
> Resetting I/O buses...
> >>>
>
> Tested-by: Serge Belyshev <belyshev@depni.sinp.msu.ru>
Thanks ;)
Here, have that beer back - I kept some for you.
prev parent reply other threads:[~2020-11-14 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 13:58 [PATCH REPOST] alpha: Replace bogus in_interrupt() Sebastian Andrzej Siewior
2020-11-14 0:25 ` Andrew Morton
2020-11-14 8:05 ` Serge Belyshev
2020-11-14 18:39 ` Andrew Morton [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=20201114103935.6b7d0f55e2cd6dce536d304f@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=belyshev@depni.sinp.msu.ru \
--cc=bigeasy@linutronix.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=rth@twiddle.net \
--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