mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: 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 10:46:16 +0000	[thread overview]
Message-ID: <20100219104616.377927e6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <2582583.137891266540487930.JavaMail.root@zimbra>

> If the X server eventually uses this new mode, debugging and crash
> recovery should become easier. This is because even when currently in
> the VT of a frozen X server it would still be possible to switch out
> by doing SysRq-r and then CTRL-<number of a text vt>, sshing in and
> doing chvt <number of a text vt>, or any other method of VT switching.
> The general concensus on #xorg-devel seems to be that it should be
> safe to use this with X now that we have KMS.
> 
> Signed-off-by: Ari Entlich <atrigent@ccs.neu.edu>

If KMS doesn't need to mode switch then does it need any of this stuff -
can it not just switch to a console and use it ? Otherwise please use a
different value than ACKACQ (just for clarity) and conceptually it looks
fine to me - I just question if it's really needed as KMS based X not
having to play with magic locking stuff would be cleaner still.

Alan

  reply	other threads:[~2010-02-19 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8618245.137111266537413491.JavaMail.root@zimbra>
2010-02-19  0:48 ` atrigent
2010-02-19 10:46   ` Alan Cox [this message]
     [not found] <7662526.141431266580674036.JavaMail.root@zimbra>
2010-02-19 12:00 ` Ari G. Entlich
2010-02-19 12:07   ` Alan Cox
     [not found] <16583928.142261266584767537.JavaMail.root@zimbra>
2010-02-19 13:10 ` Ari G. Entlich
2010-02-19 14:18   ` Alan Cox
     [not found] <26133453.143601266589400174.JavaMail.root@zimbra>
2010-02-19 14:24 ` Ari Entlich

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=20100219104616.377927e6@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®