From: Chris Wilson <chris@chris-wilson.co.uk>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 3/3] drm/i915: treat stolen as a region
Date: Fri, 18 Oct 2019 10:56:53 +0100 [thread overview]
Message-ID: <157139261395.10597.5640146663288332929@skylake-alporthouse-com> (raw)
In-Reply-To: <20191018090751.28295-3-matthew.auld@intel.com>
Quoting Matthew Auld (2019-10-18 10:07:51)
> Convert stolen memory over to a region object. Still leaves open the
> question with what to do with pre-allocated objects...
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
> ---
With the exception that I think this patch should introduce
INTEL_MEMORY_STOLEN and INTEL_REGION_STOLEN as well,
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-10-18 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 9:07 [PATCH v2 1/3] drm/i915: enumerate and init each supported region Matthew Auld
2019-10-18 9:07 ` [PATCH v2 2/3] drm/i915: treat shmem as a region Matthew Auld
2019-10-18 9:55 ` Chris Wilson
2019-10-18 9:07 ` [PATCH v2 3/3] drm/i915: treat stolen " Matthew Auld
2019-10-18 9:56 ` Chris Wilson [this message]
2019-10-18 9:49 ` [PATCH v2 1/3] drm/i915: enumerate and init each supported region Chris Wilson
2019-10-18 11:14 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/3] " Patchwork
2019-10-18 11:39 ` ✓ Fi.CI.BAT: success " Patchwork
2019-10-18 15:28 ` ✓ Fi.CI.IGT: " 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=157139261395.10597.5640146663288332929@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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.