On Fri, May 09, 2014 at 01:08:39PM +0100, oscar.mateo@xxxxxxxxx wrote: > From: Oscar Mateo <oscar.mateo@xxxxxxxxx> > > The context are going to become very important pretty soon, and > we need to be able to access them in a number of places inside > the command submission path. The idea is that, when we need to > place commands inside a ringbuffer or update the tail register, > we know which context we are working with. > > We left intel_ring_begin() as a function macro to quickly adapt > legacy code, an introduce intel_ringbuffer_begin() as the first > of a set of new functions for ringbuffer manipulation (the rest > will come in subsequent patches). > > No functional changes. > > v2: Do not set the context to NULL. In legacy code, set it to > the default ring context (even if it doesn't get used later on). Won't rings be stored within the context? So the context should be derivable from which ring the operation is being issued on. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
