public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Oliver Neukum <oliver@neukum.org>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, greg@kroah.com, vojtech@suse.cz
Subject: Re: [RFC] Changing SysRq - show registers handling
Date: Thu, 3 Jun 2004 17:06:01 -0400	[thread overview]
Message-ID: <20040603210601.GC6709@thunk.org> (raw)
In-Reply-To: <200406030944.01615.oliver@neukum.org>

On Thu, Jun 03, 2004 at 09:44:01AM +0200, Oliver Neukum wrote:
> Am Donnerstag, 3. Juni 2004 09:27 schrieb Dmitry Torokhov:
> > I don't like the requirement of SysRq request processing being in hard
> > interrupt handler - that excludes uinput-generated events and precludes
> > moving keyboard handling to a tasklet for example.
> 
> SysRq should work even if bottom halfs don't.

Indeed; one of the times when SysRq-p is used in the field is when the
machine is completely wedged.  Sometimes it's the only way to figure
out where the machine is wedged.  It would be unfortunate if the
number of cases (when the kernel is four feet in the air and
twitching) where SysRq worked decreases as a result of the proposed
change.

						- Ted

  reply	other threads:[~2004-06-03 21:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  6:34 [RFC] Changing SysRq - show registers handling Dmitry Torokhov
2004-06-03  6:53 ` Andrew Morton
2004-06-03  7:08   ` Dmitry Torokhov
2004-06-03  7:18     ` Andrew Morton
2004-06-03  7:27       ` Dmitry Torokhov
2004-06-03  7:39         ` Andrew Morton
2004-06-03  7:44         ` Oliver Neukum
2004-06-03 21:06           ` Theodore Ts'o [this message]
2004-06-03 22:21             ` Keith Owens
     [not found] <fa.jjf8osn.670mbt@ifi.uio.no>
2004-06-03  7:03 ` Andy Lutomirski
2004-06-03  7:15   ` Dmitry Torokhov

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=20040603210601.GC6709@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@osdl.org \
    --cc=dtor_core@ameritech.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=vojtech@suse.cz \
    /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