From: "H. Peter Anvin" <hpa@zytor.com>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Albert Cahalan <acahalan@gmail.com>,
"Antonino A. Daplas" <adaplas@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
aeb@cwi.nl
Subject: Re: console font limits
Date: Thu, 03 May 2007 17:39:05 -0700 [thread overview]
Message-ID: <463A80A9.7030809@zytor.com> (raw)
In-Reply-To: <E0FF8D28-219F-44D5-88B4-BDE6A4D6605A@mac.com>
Kyle Moffett wrote:
>
> Actually I think the real problem was that "KD_GRAPHICS" got overloaded
> to mean "some userspace program is probably poking at the GPU in very
> direct ways possibly including /dev/mem". As such it really isn't safe
> at all for the kernel to write stuff to the screen in that situation;
> you could turn a panic()+reboot-after-30-secs into an unrecoverable hard
> PCI bus lockup. IIRC there were at least a couple chipsets which had
> that problem with X. If we can implement enough APIs for X to do all of
> its stuff from userspace without iopl() or /dev/mem then we could
> probably bring back the option for dumping oopses to screen in
> KD_GRAPHICS mode, but otherwise it'll just cause more headaches.
>
It never meant anything *BUT* that, to the best of my knowledge. That
was certainly the original meaning of KD_GRAPHICS.
-hpa
next prev parent reply other threads:[~2007-05-04 0:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 4:09 console font limits Albert Cahalan
2007-05-01 11:49 ` Geert Uytterhoeven
2007-05-01 12:11 ` Antonino A. Daplas
2007-05-01 15:05 ` H. Peter Anvin
2007-05-01 15:49 ` Albert Cahalan
2007-05-02 18:02 ` Jan Engelhardt
2007-05-03 6:17 ` Albert Cahalan
2007-05-03 7:12 ` Jan Engelhardt
2007-05-03 14:14 ` Albert Cahalan
2007-05-03 14:26 ` Jan Engelhardt
2007-05-03 15:56 ` Geert Uytterhoeven
2007-05-03 18:27 ` Jan Engelhardt
2007-05-03 20:15 ` H. Peter Anvin
2007-05-03 20:16 ` Jan Engelhardt
2007-05-04 0:17 ` Kyle Moffett
2007-05-04 0:39 ` H. Peter Anvin [this message]
2007-05-04 3:58 ` Daniel Hazelton
2007-05-04 4:59 ` Antonino A. Daplas
2007-05-04 15:34 ` Jesse Barnes
2007-05-06 23:35 ` Daniel Hazelton
2007-05-03 7:19 ` H. Peter Anvin
2007-05-03 7:45 ` Helge Hafting
2007-05-03 10:20 ` Alan Cox
2007-05-01 17:06 ` Ken Moffat
2007-05-03 17:11 ` Andries Brouwer
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=463A80A9.7030809@zytor.com \
--to=hpa@zytor.com \
--cc=acahalan@gmail.com \
--cc=adaplas@gmail.com \
--cc=aeb@cwi.nl \
--cc=geert@linux-m68k.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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