From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: James Simmons <jsimmons@edgeglobal.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Marcus Sundberg <erammsu@kieray1.p.y.ki.era.ericsson.se>,
linux-mm@kvack.org
Subject: Re: mm->mmap_sem
Date: Wed, 29 Sep 1999 20:23:00 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.990929201805.6780A-100000@kanga.kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9909292012290.31287-100000@imperial.edgeglobal.com>
On Wed, 29 Sep 1999, James Simmons wrote:
> On Thu, 30 Sep 1999, Stephen C. Tweedie wrote:
>
> > Hi,
> >
> > On Mon, 27 Sep 1999 15:31:28 -0400 (EDT), James Simmons
> > <jsimmons@edgeglobal.com> said:
> >
> > > What are all the broken cards out their? I was reading my old Matrox
> > > Millenium I docs and even that card supports similutaneous access to
> > > the accel engine and framebuffer. If the number of cards that are that
> > > broken are small then I just will not support them.
> >
> > I think that there's a large number of them. The XI and XFree86 folk
> > would probably know which ones exactly.
>
> Yikes. I think the best solution is to just put the process that owns
> the framebuffer to be put to sleep just before accel engine access. Wake
> it up once its done. Some fancy scheduling tricks should do it. I have it
> setup now that accels used internal in the kernel to speed up console
> rendering will not work when /dev/fb is mmapped. Also I have set it up so
> only one process can open /dev/fb at a time. This makes life much easier.
No, same problem. You can't put a process to sleep without
inter-processor interrupts on smp if its not running currently. You can't
allow the kernel to touch the frame buffer if the user is using the
accelerator or vice-versa. Have an ioctl to lock the kernel out from
updating, and only unlock it from user space when there's no activity for
a while.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-09-30 0:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-22 21:02 mm->mmap_sem James Simmons
1999-09-24 0:07 ` mm->mmap_sem Stephen C. Tweedie
1999-09-24 14:59 ` mm->mmap_sem James Simmons
1999-09-24 18:09 ` mm->mmap_sem Stephen C. Tweedie
1999-09-25 1:24 ` mm->mmap_sem James Simmons
1999-09-25 14:55 ` mm->mmap_sem Andrea Arcangeli
1999-09-25 16:50 ` mm->mmap_sem James Simmons
1999-09-25 17:06 ` mm->mmap_sem Andrea Arcangeli
1999-09-26 1:19 ` mm->mmap_sem James Simmons
1999-09-26 14:07 ` mm->mmap_sem Andrea Arcangeli
1999-09-27 8:55 ` mm->mmap_sem Marcus Sundberg
1999-09-27 19:31 ` mm->mmap_sem James Simmons
1999-09-29 23:00 ` mm->mmap_sem Stephen C. Tweedie
1999-09-30 0:17 ` mm->mmap_sem James Simmons
1999-09-30 0:23 ` Benjamin C.R. LaHaise [this message]
1999-09-30 14:59 ` mm->mmap_sem James Simmons
1999-09-30 15:15 ` mm->mmap_sem Benjamin C.R. LaHaise
1999-09-30 16:05 ` mm->mmap_sem James Simmons
1999-09-30 14:54 ` mm->mmap_sem Stephen C. Tweedie
1999-09-27 14:16 ` mm->mmap_sem Stephen C. Tweedie
1999-09-27 20:22 ` mm->mmap_sem James Simmons
1999-09-27 14:13 ` mm->mmap_sem Stephen C. Tweedie
1999-09-27 8:08 ` mm->mmap_sem Neil Conway
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=Pine.LNX.3.96.990929201805.6780A-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=erammsu@kieray1.p.y.ki.era.ericsson.se \
--cc=jsimmons@edgeglobal.com \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.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