From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 5/6] drm/i915: Cache LRCA in the context
Date: Thu, 7 Jan 2016 17:18:47 +0000 [thread overview]
Message-ID: <568E9DF7.7050401@linux.intel.com> (raw)
In-Reply-To: <20160107164624.GP652@nuc-i3427.alporthouse.com>
On 07/01/16 16:46, Chris Wilson wrote:
> On Thu, Jan 07, 2016 at 04:36:20PM +0000, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> LRCA lifetime is well defined so cache it so it can be looked up
>> cheaply from the interrupt context and at command submission
>> time.
>
> Or track the actual vma.
This looked easier and good enough.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-07 17:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 16:36 [PATCH 0/6] Misc cleanups Tvrtko Ursulin
2016-01-07 16:36 ` [PATCH 1/6] drm/i915/bdw+: Replace list_del+list_add_tail with list_move_tail Tvrtko Ursulin
2016-01-07 16:45 ` Chris Wilson
2016-01-07 17:18 ` Tvrtko Ursulin
2016-01-07 16:36 ` [PATCH 2/6] drm/i915: Don't need a timer to wake us up Tvrtko Ursulin
2016-01-07 16:36 ` [PATCH 3/6] drm/i915: Avoid invariant conditionals in lrc interrupt handler Tvrtko Ursulin
2016-01-07 16:42 ` Chris Wilson
2016-01-07 17:16 ` Tvrtko Ursulin
2016-01-07 16:36 ` [PATCH 4/6] drm/i915: Fail engine initialization if LRCA is incorrectly aligned Tvrtko Ursulin
2016-01-07 16:44 ` Chris Wilson
2016-01-07 16:36 ` [PATCH 5/6] drm/i915: Cache LRCA in the context Tvrtko Ursulin
2016-01-07 16:46 ` Chris Wilson
2016-01-07 17:18 ` Tvrtko Ursulin [this message]
2016-01-07 16:36 ` [PATCH 6/6] drm/i915: Only grab timestamps when needed Tvrtko Ursulin
2016-01-07 16:47 ` Chris Wilson
2016-01-07 17:20 ` Tvrtko Ursulin
2016-01-11 9:27 ` ✓ success: Fi.CI.BAT Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568E9DF7.7050401@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.