From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kms in defconfig
Date: Tue, 28 Apr 2009 22:36:24 -0700 [thread overview]
Message-ID: <20090428223624.61e7b255.akpm@linux-foundation.org> (raw)
In-Reply-To: <21d7e9970904270156v54a6483fs20d5b31c97a1d482@mail.gmail.com>
On Mon, 27 Apr 2009 18:56:27 +1000 Dave Airlie <airlied@gmail.com> wrote:
> > KMS is the sane design for graphics and i'd go as far as to consider
> > user-space mode setting an outright _bug_. It look a long time to
> > fix but now lets look forward and fix all the bugs in KMS, ASAP ...
>
> Its mainly for things like Andrews Vaio, people will not expect a new kernel
> to take out any current userspace, its a pain, but we assume distros + people
> who compile their own kernels will know what userspace exists on their
> machines and other will get the least surprise.
My Vaio thanks you.
What is the expected user-visible failure mode when someone enables KMS
on naive userspace? iow, how can bug report screeners recognise when this has
happened?
next prev parent reply other threads:[~2009-04-29 5:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 8:21 kms in defconfig Dave Airlie
2009-04-27 8:39 ` Ingo Molnar
2009-04-27 8:56 ` Dave Airlie
2009-04-28 1:45 ` Tejun Heo
2009-04-28 1:59 ` Linus Torvalds
2009-04-28 6:29 ` Ingo Molnar
2009-04-28 16:54 ` david
2009-04-28 17:13 ` Linus Torvalds
2009-04-28 17:22 ` Ingo Molnar
2009-04-28 17:36 ` Steven Rostedt
2009-04-28 19:18 ` Ingo Molnar
2009-04-28 21:23 ` Steven Rostedt
2009-04-28 17:23 ` david
2009-04-28 17:50 ` Linus Torvalds
2009-04-28 21:43 ` Florian Mickler
2009-04-28 21:50 ` david
2009-04-28 23:10 ` Florian Mickler
2009-04-28 23:29 ` david
2009-04-29 6:55 ` Giacomo Catenazzi
2009-04-29 5:36 ` Andrew Morton [this message]
2009-04-29 5:59 ` Dave Airlie
2009-04-27 15:40 ` Peter Zijlstra
2009-04-28 1:54 ` Dave Airlie
2009-04-28 7:32 ` Peter Zijlstra
2009-04-28 17:04 ` Jesse Barnes
2009-04-28 23:42 ` Dave Airlie
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=20090428223624.61e7b255.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.