From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 30 Aug 1999 10:31:27 -0400 (EDT) From: James Simmons Subject: Re: accel handling In-Reply-To: <37CA73D8.E41F4F5@switchboard.ericsson.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Marcus Sundberg Cc: "Stephen C. Tweedie" , linux-mm@kvack.org List-ID: > What I believe James is talking about here is allowing non-priviledged > processes to access graphics hardware where the graphics card, or even > the whole system, may enter an unrecoverable state if you try to access > the frame buffer while the accel engine is active. (Yes there really > exist such hardware...) > > To achieve this you really must physicly prevent the process to access > the framebuffer while the accel engine is active. The question is what > the best way to do this is (and if that way is good enough to bother > doing it...) ? Marcus you are on this list too. Actually I have though about what he said. I never though of it this way but you can think of the accel engine as another "process" trying to use the framebuffer. Their still is the question. How do you know when a mmap of the framebuffer is being accessed? So I can lock the accel engine when needed. -- 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/