On 26/10/2016 09:14, Chris Wilson wrote:
On Wed, Oct 26, 2016 at 08:20:35AM +0100, Tvrtko Ursulin wrote:
On 25/10/2016 21:03, Chris Wilson wrote:
On Tue, Oct 25, 2016 at 10:05:23PM +0530, akash.g...@intel.com wrote:
From: Akash Goel
Driver accesses the ringbuffer pages, via GMADR BAR, if t
On Wed, Oct 26, 2016 at 08:20:35AM +0100, Tvrtko Ursulin wrote:
>
> On 25/10/2016 21:03, Chris Wilson wrote:
> >On Tue, Oct 25, 2016 at 10:05:23PM +0530, akash.g...@intel.com wrote:
> >>From: Akash Goel
> >>
> >>Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are
> >>pinned in m
On 25/10/2016 21:03, Chris Wilson wrote:
On Tue, Oct 25, 2016 at 10:05:23PM +0530, akash.g...@intel.com wrote:
From: Akash Goel
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are
pinned in mappable aperture portion of GGTT and for ringbuffer pages
allocated from Stolen memo
On Tue, Oct 25, 2016 at 10:05:23PM +0530, akash.g...@intel.com wrote:
> From: Akash Goel
>
> Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are
> pinned in mappable aperture portion of GGTT and for ringbuffer pages
> allocated from Stolen memory, access can only be done through
From: Akash Goel
Driver accesses the ringbuffer pages, via GMADR BAR, if the pages are
pinned in mappable aperture portion of GGTT and for ringbuffer pages
allocated from Stolen memory, access can only be done through GMADR BAR.
In case of GuC based submission, updates done in ringbuffer via GMAD
