From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Ari G. Entlich" <atrigent@ccs.neu.edu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call
Date: Fri, 19 Feb 2010 12:07:30 +0000 [thread overview]
Message-ID: <20100219120730.4793ce0d@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <28568671.141471266580824918.JavaMail.root@zimbra>
> 1. VT_AUTO doesn't send signals to anything when a VT switch happens, precisely
> because VT_AUTO is supposed to be used in the case where there's nothing to
> send signals TO (i.e. the VT is managed by the kernel). The X server still
> needs to know about VT switches to turn input devices off and such.
Ok..
> VT_ACKACQ, it wouldn't really make sense for there to be a new VT_ACKACQ value,
> because VT_ACKACQ is something which gets passed to a VT_RELDISP, and VT_RELDISP
> isn't needed at all in this new mode.
I don't want to change the existing values as they are somewhat visible
to user space.
> I hope that clarifies things.
Yes. You could use the VT_EVENT facility for the switch monitoring but
the asynchronous nature of the reporting probably isn't what is needed
for input device switching etc.
Looks fine to me - just bump the value and resubmit
next prev parent reply other threads:[~2010-02-19 12:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7662526.141431266580674036.JavaMail.root@zimbra>
2010-02-19 12:00 ` Ari G. Entlich
2010-02-19 12:07 ` Alan Cox [this message]
[not found] <26133453.143601266589400174.JavaMail.root@zimbra>
2010-02-19 14:24 ` Ari Entlich
[not found] <16583928.142261266584767537.JavaMail.root@zimbra>
2010-02-19 13:10 ` Ari G. Entlich
2010-02-19 14:18 ` Alan Cox
[not found] <8618245.137111266537413491.JavaMail.root@zimbra>
2010-02-19 0:48 ` atrigent
2010-02-19 10:46 ` Alan Cox
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=20100219120730.4793ce0d@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=atrigent@ccs.neu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®