--- Keith Whitwell <[EMAIL PROTECTED]> wrote:
> Additionally, by making this step root-only, the X server is
> effectively
> required to perform this task, meaning that the client must be
> 'blessed' by
> the X server's security mechanisms, whatever they might be.
I would like to change this from root+authorized to just authorized in
the DRM drivers. In the mesa-solo model context's don't need to pass
through the root priv server.
> Jon Smirl wrote:
> > Context creation in DRM is marked as needing root access. Is this
> to
> > prevent a process from doing a DOS attack by creating too many
> > contexts? Couldn't I do the same DOS attack simply by creating lots
> of
> > processes each with their own context?
> >
> > Is there a hardware limit on contexts? It looks to me like contexts
> are
> > allocated in normal memory and then swapped in as needed. But I
> don't
> > understand everything going on with context creation yet.
>
> You're not alone. I think the thinking relates to hardware schemes
> where
> contexts are hardware resources - these aren't uncommon at all, but
> we don't
> tend to make use of that facility in the existing drivers.
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
