From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Ville Syrjala <ville.syrjala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 1/6] drm/i915: Add a new "remapped" gtt_view
Date: Tue, 15 Jan 2019 11:11:19 +0000 [thread overview]
Message-ID: <08826cdb-c785-4ee6-5d19-bf1a869d4099@linux.intel.com> (raw)
In-Reply-To: <154754988770.30063.17748893490510932379@skylake-alporthouse-com>
On 15/01/2019 10:58, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-01-14 09:55:10)
>>
>> On 11/01/2019 19:46, Ville Syrjala wrote:
>>> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>>>
>>> To overcome display engine stride limits we'll want to remap the
>>> pages in the GTT. To that end we need a new gtt_view type which
>>> is just like the "rotated" type except not rotated.
>>
>> I think I asked this before, so sorry if you also answered it - what
>> about rotated setups which go over display engine stride limits?
>
> There's always a task for tomorrow. For such a remapping, I guess we
> want to allow an arbitrary remapping table.
> struct intel_arb_ggtt_view {
> unsigned long *indices;
> };
True, nothing here would make that impossible it seems, which was my
concern when I asked this question.
Btw.. would this make calling this one "tiled" view more future proof?
Then we would be able to call the arbitrarily remapped view just remapped.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-01-15 11:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 19:46 [PATCH v2 0/6] drm/i915: GTT remapping for display Ville Syrjala
2019-01-11 19:46 ` [PATCH v2 1/6] drm/i915: Add a new "remapped" gtt_view Ville Syrjala
2019-01-14 9:55 ` Tvrtko Ursulin
2019-01-15 10:58 ` Chris Wilson
2019-01-15 11:11 ` Tvrtko Ursulin [this message]
2019-01-15 13:43 ` Ville Syrjälä
2019-01-15 14:18 ` Chris Wilson
2019-01-24 23:24 ` Chris Wilson
2019-01-11 19:47 ` [PATCH v2 2/6] drm/i915/selftests: Add mock selftest for remapped vmas Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 3/6] drm/i915/selftests: Add live vma selftest Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 4/6] drm/i915: Overcome display engine stride limits via GTT remapping Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 5/6] drm/i915: Bump gen4+ fb stride limit to 256KiB Ville Syrjala
2019-01-11 19:47 ` [PATCH v2 6/6] drm/i915: Bump gen7+ fb size limits to 16kx16k Ville Syrjala
2019-01-11 20:00 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GTT remapping for display Patchwork
2019-01-11 20:02 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-01-11 20:18 ` ✓ Fi.CI.BAT: success " Patchwork
2019-01-12 2:57 ` ✗ Fi.CI.IGT: failure " 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=08826cdb-c785-4ee6-5d19-bf1a869d4099@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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.