From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Max Staudt <mstaudt@suse.de>, "Theodore Ts'o" <tytso@mit.edu>,
Greg KH <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 8250: option 'force_polling' for buggy IRQs
Date: Fri, 29 Jul 2016 10:23:35 +0100 [thread overview]
Message-ID: <20160729102335.2dbe3cad@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <87mvl1hahu.fsf@x220.int.ebiederm.org>
> Serial consoles are already polled for output. So nothing should
> care until userspace starts, and the full serial driver initializes.
At which point it hangs
> So I suspect either "irqfixup" or "irqpoll" would handle this for you.
> If not I am certain a small tweak to some of that code would work.
irqfixup won't usually help but irqpoll with HZ=1000 ought to, although
it has its own set of problems because not all devices with non shared
IRQ lines take kindly to irqpoll.
Alan
next prev parent reply other threads:[~2016-07-29 9:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:36 [PATCH] 8250: option 'force_polling' for buggy IRQs Max Staudt
2016-07-25 17:47 ` Greg KH
2016-07-26 11:42 ` Max Staudt
2016-07-26 15:08 ` Greg KH
2016-07-26 16:18 ` Max Staudt
2016-07-27 12:09 ` One Thousand Gnomes
2016-07-27 12:14 ` Max Staudt
2016-07-27 13:33 ` Theodore Ts'o
2016-07-27 20:01 ` One Thousand Gnomes
2016-07-28 9:59 ` Max Staudt
2016-07-28 14:47 ` Greg KH
2016-07-28 16:01 ` Theodore Ts'o
2016-07-28 18:40 ` Eric W. Biederman
2016-07-29 9:23 ` One Thousand Gnomes [this message]
2016-07-29 9:58 ` Max Staudt
2016-07-29 17:38 ` Eric W. Biederman
2016-08-01 15:27 ` One Thousand Gnomes
2016-07-25 18:19 ` kbuild test robot
2016-07-26 11:47 ` [PATCHv2] " Max Staudt
2016-07-26 11:54 ` [PATCHv3] " Max Staudt
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=20160729102335.2dbe3cad@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mstaudt@suse.de \
--cc=tytso@mit.edu \
/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).