From: Michael Ellerman <mpe@ellerman.id.au>
To: Sam Mendoza-Jonas <sam@mendozajonas.com>, linuxppc-dev@ozlabs.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
"# 4 . 1 . x-" <stable@vger.kernel.org>,
Alistair Popple <alistair@popple.id.au>,
Samuel Mendoza-Jonas <sam@mendozajonas.com>
Subject: Re: [1/2] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles
Date: Tue, 5 Jul 2016 15:34:42 +1000 (AEST) [thread overview]
Message-ID: <3rkCJ22Wwpz9sBl@ozlabs.org> (raw)
In-Reply-To: <20160628031139.12500-1-sam@mendozajonas.com>
On Tue, 2016-28-06 at 03:11:38 UTC, Sam Mendoza-Jonas wrote:
> Commit 2def86a7200c
> ("hvc: Convert to using interrupts instead of opal events")
> enabled the use of interrupts in the hvc_driver for OPAL platforms.
> However on machines with more than one hvc console, any console after
> the first will fail to register an interrupt handler in
> notifier_add_irq() since all consoles share the same IRQ number but do
> not set the IRQF_SHARED flag:
>
> [ 51.179907] genirq: Flags mismatch irq 31. 00000000 (hvc_console) vs.
> 00000000 (hvc_console)
> [ 51.180010] hvc_open: request_irq failed with rc -16.
>
> This error propagates up to hvc_open() and the console is closed, but
> OPAL will still generate interrupts that are not handled, leading to
> rcu_sched stall warnings.
>
> Set IRQF_SHARED when calling request_irq, allowing additional consoles
> to start properly. This is only set for consoles handled by
> hvc_opal_probe(), leaving other types unaffected.
>
> Signed-off-by: Samuel Mendoza-Jonas <sam@mendozajonas.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au>
Greg I'm assuming you'll take this unless you tell me otherwise.
cheers
prev parent reply other threads:[~2016-07-05 5:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 3:11 [PATCH 1/2] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles Samuel Mendoza-Jonas
2016-06-28 3:11 ` [PATCH 2/2] tty/hvc: Use opal irqchip interface if available Samuel Mendoza-Jonas
2016-06-28 3:34 ` Benjamin Herrenschmidt
2016-06-28 3:35 ` Benjamin Herrenschmidt
2016-07-05 5:31 ` [2/2] " Michael Ellerman
2016-07-05 6:07 ` Samuel Mendoza-Jonas
2016-07-06 9:51 ` Michael Ellerman
2016-07-05 5:34 ` Michael Ellerman [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=3rkCJ22Wwpz9sBl@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=alistair@popple.id.au \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=sam@mendozajonas.com \
--cc=stable@vger.kernel.org \
/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).