From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: is magic-sysrq handling threaded in linux-RT?
Date: Wed, 3 Jul 2019 13:24:57 +0200 [thread overview]
Message-ID: <20190703112457.qxq2xtqcg564gms3@linutronix.de> (raw)
In-Reply-To: <a9dfc474-3691-64bc-7b81-7e4e6d4acb71@windriver.com>
On 2019-07-02 10:04:49 [-0600], Chris Friesen wrote:
> I'd like to clarify something though...is the serial console interrupt
> threaded? If it is, then something that prevents the scheduler from running
> could result in magic-sysrq not functioning, but if it isn't then I think
> that would point to an interrupt problem.
The interrupt is threaded, the magic-sysrq happens threaded then. Any
printk in non-preemptible region will be delayed until preemptible
region is reached (or delayed until the next print from preeptible
region).
> Thanks,
> Chris
Sebastian
prev parent reply other threads:[~2019-07-03 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 16:04 is magic-sysrq handling threaded in linux-RT? Chris Friesen
2019-07-03 11:24 ` 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=20190703112457.qxq2xtqcg564gms3@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=chris.friesen@windriver.com \
--cc=linux-rt-users@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).