From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Robert Beckett <bob.beckett@collabora.com>,
dri-devel@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>
Cc: Matthew Auld <matthew.auld@intel.com>, linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v2 2/5] drm/i915: sanitize mem_flags for stolen buffers
Date: Thu, 14 Apr 2022 15:58:53 +0200 [thread overview]
Message-ID: <955ad2c80d540ba9eee884d6a1f15b4d1604e306.camel@linux.intel.com> (raw)
In-Reply-To: <20220412151838.1298956-3-bob.beckett@collabora.com>
On Tue, 2022-04-12 at 15:18 +0000, Robert Beckett wrote:
> stolen regions are not page backed or considered iomem.
thus...
A little more elaborate commit message please.
>
> Signed-off-by: Robert Beckett <bob.beckett@collabora.com>
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
> b/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
> index 358f8a1a30ce..9fe8132de3b2 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
> @@ -122,8 +122,9 @@ void i915_ttm_adjust_gem_after_move(struct
> drm_i915_gem_object *obj)
>
> obj->mem_flags &= ~(I915_BO_FLAG_STRUCT_PAGE |
> I915_BO_FLAG_IOMEM);
>
> - obj->mem_flags |= i915_ttm_cpu_maps_iomem(bo->resource) ?
> I915_BO_FLAG_IOMEM :
> - I915_BO_FLAG_STRUCT_PAGE;
> + if (obj->mm.region->id != INTEL_REGION_STOLEN_SMEM)
> + obj->mem_flags |= i915_ttm_cpu_maps_iomem(bo-
> >resource) ? I915_BO_FLAG_IOMEM :
> + I915_BO_FLAG_STRUCT_PAGE;
>
> cache_level = i915_ttm_cache_level(to_i915(bo->base.dev), bo-
> >resource,
> bo->ttm);
next prev parent reply other threads:[~2022-04-14 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:18 [Intel-gfx] [PATCH v2 0/5] drm/i915: ttm for stolen region Robert Beckett
2022-04-12 15:18 ` [Intel-gfx] [PATCH v2 1/5] drm/i915: instantiate ttm ranger manager for stolen memory Robert Beckett
2022-04-12 15:18 ` [Intel-gfx] [PATCH v2 2/5] drm/i915: sanitize mem_flags for stolen buffers Robert Beckett
2022-04-14 13:58 ` Thomas Hellström [this message]
2022-04-12 15:18 ` [Intel-gfx] [PATCH v2 3/5] drm/i915: ttm move/clear logic fix Robert Beckett
2022-04-14 14:00 ` Thomas Hellström
2022-04-12 15:18 ` [Intel-gfx] [PATCH v2 4/5] drm/i915: ttm backend dont provide mmap_offset for kernel buffers Robert Beckett
2022-04-14 14:05 ` Thomas Hellström
2022-04-14 16:13 ` Robert Beckett
2022-04-27 10:14 ` Thomas Hellström
2022-04-12 15:18 ` [Intel-gfx] [PATCH v2 5/5] drm/i915: stolen memory use ttm backend Robert Beckett
2022-04-12 15:34 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: ttm for stolen region (rev2) Patchwork
2022-04-12 15:48 ` [Intel-gfx] ✗ Fi.CI.BAT: 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=955ad2c80d540ba9eee884d6a1f15b4d1604e306.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@linux.ie \
--cc=bob.beckett@collabora.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.auld@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@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