Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v2 4/9] drm/i915/gt: Add an insert_entry for gen8_ppgtt
Date: Wed, 9 Jun 2021 08:44:02 +0100	[thread overview]
Message-ID: <e75712c3-af00-e0be-6ee1-3203e7242065@intel.com> (raw)
In-Reply-To: <20210609063436.284332-5-thomas.hellstrom@linux.intel.com>

On 09/06/2021 07:34, Thomas Hellström wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
> 
> In the next patch, we will want to write a PTE for an explicit
> dma address, outside of the usual vma.
> 
> 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

  reply	other threads:[~2021-06-09  7:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09  6:34 [Intel-gfx] [PATCH v2 0/9] Prereqs for TTM accelerated migration Thomas Hellström
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 1/9] drm/i915: Reference objects on the ww object list Thomas Hellström
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 2/9] drm/i915: Break out dma_resv ww locking utilities to separate files Thomas Hellström
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 3/9] drm/i915: Introduce a ww transaction helper Thomas Hellström
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 4/9] drm/i915/gt: Add an insert_entry for gen8_ppgtt Thomas Hellström
2021-06-09  7:44   ` Matthew Auld [this message]
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 5/9] drm/i915/gt: Add a routine to iterate over the pagetables of a GTT Thomas Hellström
2021-06-09  7:48   ` Matthew Auld
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 6/9] drm/i915/gt: Export the pinned context constructor and destructor Thomas Hellström
2021-06-09  8:00   ` Matthew Auld
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 7/9] drm/i915/gt: Pipelined page migration Thomas Hellström
2021-06-09 12:14   ` Matthew Auld
2021-06-09 12:48   ` Matthew Auld
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 8/9] drm/i915/gt: Pipelined clear Thomas Hellström
2021-06-09 13:42   ` Matthew Auld
2021-06-09  6:34 ` [Intel-gfx] [PATCH v2 9/9] drm/i915/gt: Setup a default migration context on the GT Thomas Hellström
2021-06-09 14:17   ` Matthew Auld
2021-06-09  7:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prereqs for TTM accelerated migration (rev2) Patchwork
2021-06-09  8:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-09  8:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2021-06-09  9:56 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2021-06-09 11:48 ` [Intel-gfx] [PATCH v2 0/9] Prereqs for TTM accelerated migration Daniel Vetter
2021-06-09 12:16   ` Thomas Hellström
2021-06-09 12:20     ` Matthew Auld
2021-06-09 13:08       ` Thomas Hellström
2021-06-09 14:35         ` Thomas Hellström
2021-06-09 14:54           ` Daniel Vetter

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=e75712c3-af00-e0be-6ee1-3203e7242065@intel.com \
    --to=matthew.auld@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=thomas.hellstrom@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox