From: "Ari G. Entlich" <atrigent@ccs.neu.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
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 08:10:49 -0500 (EST) [thread overview]
Message-ID: <9700049.142281266585049621.JavaMail.root@zimbra> (raw)
In-Reply-To: <16583928.142261266584767537.JavaMail.root@zimbra>
----- "Alan Cox" <alan@lxorguk.ukuu.org.uk> wrote:
> I don't want to change the existing values as they are somewhat visible
> to user space.
Sorry if I was unclear - I wasn't talking about changing the value, I was
just saying that VT_ACKACQ and VT_PROCESS_AUTO are used in different
contexts, so it shouldn't matter that they have the same value. One thing
that probably would be nice though would be to move the VT_ACKACQ define
to a different place in vt.h (probably after the VT_RELDISP define).
> 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.
Yeah, it looks like the X server would have to be constantly blocking
inside a VT_WAITEVENT ioctl in order to use that, and then it wouldn't
be getting anything else done. :-/
Ari
next parent reply other threads:[~2010-02-19 13:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16583928.142261266584767537.JavaMail.root@zimbra>
2010-02-19 13:10 ` Ari G. Entlich [this message]
2010-02-19 14:18 ` [PATCH] Add a new VT mode which is like VT_PROCESS but doesn't require a VT_RELDISP ioctl call Alan Cox
[not found] <26133453.143601266589400174.JavaMail.root@zimbra>
2010-02-19 14:24 ` Ari Entlich
[not found] <7662526.141431266580674036.JavaMail.root@zimbra>
2010-02-19 12:00 ` Ari G. Entlich
2010-02-19 12:07 ` 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=9700049.142281266585049621.JavaMail.root@zimbra \
--to=atrigent@ccs.neu.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.