From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Sergey Organov <sorganov@gmail.com>
Cc: Jiri Slaby <jslaby@suse.cz>,
linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: Serial console and interrupts latency.
Date: Tue, 14 Apr 2020 10:56:44 +0100 [thread overview]
Message-ID: <20200414095644.GU25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <CANp_pu1caHaGJbBR8sEoOER2SfMDO3eJKOVQz3K8jKKZACh7=w@mail.gmail.com>
On Tue, Apr 14, 2020 at 12:50:49PM +0300, Sergey Organov wrote:
> Russell King - ARM Linux admin <linux@armlinux.org.uk>:
> > Correct, and what I said back then still applies - and more.
>
> What bothers me is "we have no real option..." part of this, as it's rarely
> happens to be the case.
I don't see you coming forward with a solution beyond "let's revert
the commit" or "let's comment out the lock" - neither of which are
an option for mainline kernels.
Until *you* do, since you obviously have better ideas, "we have no
real option".
But, as I've said, one of the *important* characteristics of serial
console is that it is synchronous with the kernel, so it can be
relied upon to get complete messages out if the kernel crashes after
a printk() has been executed, and that must not be lost.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up
next prev parent reply other threads:[~2020-04-14 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 9:04 Serial console and interrupts latency Sergey Organov
2020-03-27 13:13 ` Jiri Slaby
2020-03-27 13:38 ` Russell King - ARM Linux admin
2020-03-27 14:03 ` Sergey Organov
2020-03-27 13:58 ` Sergey Organov
2020-03-27 23:24 ` Russell King - ARM Linux admin
2020-04-14 9:50 ` Sergey Organov
2020-04-14 9:56 ` Russell King - ARM Linux admin [this message]
2020-04-14 12:14 ` Sergey Organov
-- strict thread matches above, loose matches on Subject: below --
2020-03-20 15:15 Sergey Organov
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=20200414095644.GU25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-serial@vger.kernel.org \
--cc=sorganov@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;
as well as URLs for NNTP newsgroup(s).