Re: Kernel / user interface for new memory manager

[Ville <sy...@sc...>]

On Tue, Aug 23, 2005 at 11:04:22AM -0700, Ian Romanick wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Stephane Marchesin wrote:
>=20
> > Also, with the current log design for the memory manager, it is possi=
ble
> > for a rogue process to make the log wrap and not call the
> > force_log_update ioctl, thus being able to create some kind of race
> > condition where the drm believes it still owns the memory but another
> > process has allocated it.
>=20
> The log design presents numerous opportunities for rogue processes to d=
o
> bad things.  At some level, that's inherent in the nature of direct
> rendering.  If you don't trust the processes, don't enable direct rende=
ring.

Considering one of the major uses for direct rendering is games I don't=20
think that idea will work.

--=20
Ville Syrj=E4l=E4
sy...@sc...
http://www.sci.fi/~syrjala/