mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
Cc: linux-kernel@vger.kernel.org,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
	Jiri Slaby <jslaby@suse.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, dri-devel@lists.freedesktop.org,
	kernel@collabora.com
Subject: Re: [PATCH v3 2/2] tty/sysrq: Add configurable handler to execute a compound action
Date: Fri, 2 Oct 2020 16:02:33 +0200	[thread overview]
Message-ID: <20201002140233.GB3475053@kroah.com> (raw)
In-Reply-To: <db7fe4ed-19a4-3303-a544-eb789badb8a1@collabora.com>

On Fri, Oct 02, 2020 at 03:42:52PM +0200, Andrzej Pietrasiewicz wrote:
> Hi,
> 
> W dniu 02.10.2020 o 14:54, Greg Kroah-Hartman pisze:
> > On Tue, Aug 18, 2020 at 01:28:25PM +0200, Andrzej Pietrasiewicz wrote:
> > > Userland might want to execute e.g. 'w' (show blocked tasks), followed
> > > by 's' (sync), followed by 1000 ms delay and then followed by 'c' (crash)
> > > upon a single magic SysRq. Or one might want to execute the famous "Raising
> > > Elephants Is So Utterly Boring" action. This patch adds a configurable
> > > handler, triggered with 'C', for this exact purpose. The user specifies the
> > > composition of the compound action using syntax similar to getopt, where
> > > each letter corresponds to an individual action and a colon followed by a
> > > number corresponds to a delay of that many milliseconds, e.g.:
> > > 
> > > ws:1000c
> > > 
> > > or
> > > 
> > > r:100eis:1000ub
> > 
> > A macro language for sysrq commands, who would have thought...
> > 
> > Anyway, _why_ would userland want to do something so crazy as this?
> > What is the use-case here?
> > 
> 
> A use-case is Chromebooks which do want to execute 'w', 's',
> wait 1000ms and then 'c' under one key combination. Having that supported
> upstream brings us one little step closer to those machines running
> upstream kernel.

Who is causing that to "execute"?  Some daemon/program?

> Another argument for such a "macro language" is when a machine's system
> keeps degrading over time, possibly degrading (relatively) fast.
> "Raising Elephants Is So Utterly Boring" consists of 6 actions, each
> of which requires pressing several keys. The user might be unable
> to complete all the 6 steps, while a "macro" requires user's involvement
> for carrying out just one step.

So you want to "preload" some commands ahead of time, for when you get
in trouble?

These should just be debugging / last resort types of things, how
regular are they being used in your systems?

thanks,

greg k-h

  reply	other threads:[~2020-10-02 14:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-18 11:28 [PATCH v3 0/2] " Andrzej Pietrasiewicz
2020-08-18 11:28 ` [PATCH v3 1/2] tty/sysrq: Extend the sysrq_key_table to cover capital letters Andrzej Pietrasiewicz
2020-08-18 11:28 ` [PATCH v3 2/2] tty/sysrq: Add configurable handler to execute a compound action Andrzej Pietrasiewicz
2020-10-02 12:54   ` Greg Kroah-Hartman
2020-10-02 13:42     ` Andrzej Pietrasiewicz
2020-10-02 14:02       ` Greg Kroah-Hartman [this message]
2020-10-02 15:06         ` Andrzej Pietrasiewicz
2020-10-03  8:26           ` Greg Kroah-Hartman
2020-10-02 12:31 ` [PATCH v3 0/2] " Greg Kroah-Hartman
2020-10-02 12:33   ` Andrzej Pietrasiewicz
2020-10-02 12:36     ` Andrzej Pietrasiewicz
2020-10-02 12:45       ` Daniel Vetter
2020-10-02 12:55         ` Greg Kroah-Hartman

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=20201002140233.GB3475053@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@linux.ie \
    --cc=andrzej.p@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jslaby@suse.com \
    --cc=kernel@collabora.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    /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

Powered by JetHome