On Wed, 2009-02-04 at 23:48 +0100, Thomas Hellström wrote: > Eric, > > Looking at the intel_bufmgr_gem implementation there seems to be a > number of members on a > "struct drm_intel_bo_gem" that really should be per context, like > validate_index, *reloc_* members, included_in_check_aperture etc. > > What happens if a shared texture, for example, is used by multiple > contexts from multiple threads simultaneously?
Shared textures and renderbuffers don't have relocations. validate_index is protected by the lock held across bo_exec. check_aperture needs the same locking treatment. -- Eric Anholt e...@anholt.net eric.anh...@intel.com
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
-- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
