From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH 3/5] drm/i915/gtt: Don't track dirty in gen6_alloc_va_range
Date: Mon, 07 May 2018 20:37:03 +0100 [thread overview]
Message-ID: <152572182334.9723.2701733849349005427@mail.alporthouse.com> (raw)
In-Reply-To: <20180507165222.17009-3-mika.kuoppala@linux.intel.com>
Quoting Mika Kuoppala (2018-05-07 17:52:20)
> gen6_alloc_va_range is only used to init the aliasing ppgtt, so
> we can be certain that it will be dirty every time. No need
> to track it.
Nah, we want it for full-ppgtt...
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-05-07 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 16:52 [PATCH 1/5] drm/i915/gtt: Move wmb inside ggtt_invalidate Mika Kuoppala
2018-05-07 16:52 ` [PATCH 2/5] drm/i915/gtt: Combine marking engines dirty with wmb Mika Kuoppala
2018-05-07 19:36 ` Chris Wilson
2018-05-07 16:52 ` [PATCH 3/5] drm/i915/gtt: Don't track dirty in gen6_alloc_va_range Mika Kuoppala
2018-05-07 19:37 ` Chris Wilson [this message]
2018-05-07 16:52 ` [PATCH 4/5] drm/i915/gtt: Flush write combining buffer on insert entries Mika Kuoppala
2018-05-07 19:38 ` Chris Wilson
2018-05-07 16:52 ` [PATCH 5/5] drm/i915/gtt: Trust the uncached store to flush wcb Mika Kuoppala
2018-05-07 17:01 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915/gtt: Move wmb inside ggtt_invalidate Patchwork
2018-05-07 17:02 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-05-07 17:19 ` ✓ Fi.CI.BAT: success " Patchwork
2018-05-07 18:59 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-07 21:59 ` [PATCH 1/5] " Chris Wilson
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=152572182334.9723.2701733849349005427@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=mika.kuoppala@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.