From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Thomas Hellström" <thomas@shipmail.org>,
"Dave Airlie" <airlied@linux.ie>,
"Alex Deucher" <alexdeucher@gmail.com>,
"Andrew Lutomirski" <luto@mit.edu>,
dri-devel@lists.sf.net, "Jerome Glisse" <jglisse@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [git pull] drm: previous pull req + 1.
Date: Tue, 23 Jun 2009 11:04:39 +1000 [thread overview]
Message-ID: <1245719079.4017.25.camel@pasglop> (raw)
In-Reply-To: <alpine.LFD.2.01.0906221721450.3240@localhost.localdomain>
On Mon, 2009-06-22 at 17:24 -0700, Linus Torvalds wrote:
>
> On Tue, 23 Jun 2009, Benjamin Herrenschmidt wrote:
> >
> > As far as I can remember, all fbdev operations are done under the
> > console semaphore.
>
> Yeah, and some of them are horribly broken (ie copying data from user
> space while doing it - causing horrible things like VC switching latencies
> and invisible printk's if an oops happens during the op).
>
> Or maybe that got fixed.
Well, it does rely on userspace behaving.. ie, no accel ops are done by
the kernel in KD_GRAPHICS and userspace is -supposed- to switch to
KD_GRAPHICS before touching the fb.
In fact, nowdays, we do have the infrastructure to be smart and enforce
that. IE. Instead of using a boring remap_page_ranges() in fb_mmap() we
could use a fault handler. When in KD_TEXT, we fail them, when in
KD_GRAPHICS, we service them, and we unmap_mapping_range() when
switching. Something like that...
Dunno how that interacts with the new DRM thingy though.
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-23 1:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-20 5:23 [git pull] drm: previous pull req + 1 Dave Airlie
2009-06-21 0:04 ` Maxim Levitsky
2009-06-21 0:42 ` Linus Torvalds
2009-06-21 14:47 ` Maxim Levitsky
2009-06-21 21:24 ` Chris Wilson
2009-06-22 18:09 ` Maxim Levitsky
2009-06-29 7:57 ` Chris Wilson
2009-06-30 9:49 ` Chris Wilson
2009-07-09 23:11 ` Eric Anholt
2009-06-21 1:33 ` Dave Airlie
2009-06-21 3:41 ` Andy Lutomirski
2009-06-21 5:16 ` Dave Airlie
2009-06-21 12:06 ` Andrew Lutomirski
2009-06-21 16:46 ` Linus Torvalds
2009-06-21 17:13 ` Linus Torvalds
2009-06-21 18:50 ` Andrew Lutomirski
2009-06-21 19:47 ` Linus Torvalds
2009-06-21 21:14 ` Andrew Lutomirski
2009-06-22 0:05 ` Andrew Lutomirski
2009-06-22 19:20 ` Arnaldo Carvalho de Melo
2009-06-21 22:40 ` Dave Airlie
2009-06-22 8:18 ` Thomas Hellström
2009-06-22 8:30 ` Dave Airlie
2009-06-22 18:22 ` Linus Torvalds
2009-06-22 18:59 ` Andrew Lutomirski
2009-06-22 19:43 ` Linus Torvalds
2009-06-23 0:01 ` Benjamin Herrenschmidt
2009-06-23 0:00 ` Benjamin Herrenschmidt
2009-06-23 0:24 ` Linus Torvalds
2009-06-23 1:04 ` Benjamin Herrenschmidt [this message]
2009-06-23 1:18 ` Jesse Barnes
2009-06-23 1:58 ` Benjamin Herrenschmidt
2009-06-23 2:07 ` Jesse Barnes
2009-06-23 2:26 ` Benjamin Herrenschmidt
2009-06-23 15:40 ` Jesse Barnes
2009-06-23 7:48 ` Michel Dänzer
2009-06-23 15:39 ` Jesse Barnes
2009-06-23 16:28 ` Jesse Barnes
2009-06-22 23:57 ` Benjamin Herrenschmidt
2009-06-21 22:41 ` 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=1245719079.4017.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@mit.edu \
--cc=thomas@shipmail.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