From: Matthew Auld <matthew.william.auld@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/gem: Remove special casing from reloc-gtt
Date: Thu, 21 Jan 2021 17:10:00 +0000 [thread overview]
Message-ID: <CAM0jSHOHkZhivgi-X37W2rxYQHm1vbqB8uzAVYexEjuwE0LxSQ@mail.gmail.com> (raw)
In-Reply-To: <20210121124932.2143-1-chris@chris-wilson.co.uk>
On Thu, 21 Jan 2021 at 12:49, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>
> By observing that we only use reloc-gtt on objects that are device
> coherent and idle, we can avoid the set-to-domain call. Then noting that
> our preferred partial GGTT mapping path automatically copes with tiling
> (it does not use a fence) and handles all the error cases of pinning,
> that dramatically simplifies that branch.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-21 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 12:49 [Intel-gfx] [PATCH 1/2] drm/i915/gem: Remove special casing from reloc-gtt Chris Wilson
2021-01-21 12:49 ` [Intel-gfx] [PATCH 2/2] drm/i915/gvt: Acutally use the map interface Chris Wilson
2021-01-21 17:12 ` Matthew Auld
2021-01-21 17:10 ` Matthew Auld [this message]
2021-01-21 17:47 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/gem: Remove special casing from reloc-gtt Patchwork
2021-01-21 18:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-01-21 22:44 ` [Intel-gfx] ✗ 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=CAM0jSHOHkZhivgi-X37W2rxYQHm1vbqB8uzAVYexEjuwE0LxSQ@mail.gmail.com \
--to=matthew.william.auld@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).