From: Matthew Auld <matthew.auld@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Jianshui Yu <jianshui.yu@intel.com>, Nirmoy Das <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH v5 4/5] drm/i915/display: consider DG2_RC_CCS_CC when migrating buffers
Date: Tue, 11 Oct 2022 15:39:59 +0100 [thread overview]
Message-ID: <519a0e90-3396-ba3e-5b82-e9d0dc9c452e@intel.com> (raw)
In-Reply-To: <c2639c20-6abc-08bb-76bf-bc8693f2f418@linux.intel.com>
Hi,
On 11/10/2022 14:54, Tvrtko Ursulin wrote:
>
> Hi Matt,
>
> On 04/10/2022 14:19, Matthew Auld wrote:
>> For these types of display buffers, we need to able to CPU access some
>> part of the backing memory in prepare_plane_clear_colors(). As a result
>> we need to ensure we always place in the mappable part of lmem, which
>> becomes necessary on small-bar systems.
>>
>> v2(Nirmoy & Ville):
>> - Add some commentary for why we need to CPU access the buffer.
>> - Split out the other changes, so we just consider the display change
>> here.
>> v3:
>> - Handle this in the dpt path.
>> v4(Ville):
>> - Drop the intel_fb_rc_ccs_cc_plane() sanity check in
>> pin_and_fence_fb_obj(), since we can also trigger this on DG1 it
>> seems.
>>
>> Fixes: eb1c535f0d69 ("drm/i915: turn on small BAR support")
>
> That one landed in 6.0 - do you want to send this (with
> pre-requisite(s)) to stable? Or if not do you want me to send for 6.1 as
> part of fixes flow? In which case what are the per-requisites?
This one is only for DG2, which is still hidden behind force_probe, so
not too sure if it needs stable? I think the only pre-requisite is
999f45620772 ("drm/i915: allow control over the flags when migrating"),
but again I'm not too sure how much we care about fixes for platforms
hidden behind force_probe? What do you think?
>
> Regards,
>
> Tvrtko
>
>> Reported-by: Jianshui Yu <jianshui.yu@intel.com>
>> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Cc: Nirmoy Das <nirmoy.das@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_fb_pin.c | 13 ++++++++++++-
>> 1 file changed, 12 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_fb_pin.c
>> b/drivers/gpu/drm/i915/display/intel_fb_pin.c
>> index 5031ee5695dd..e12339f46640 100644
>> --- a/drivers/gpu/drm/i915/display/intel_fb_pin.c
>> +++ b/drivers/gpu/drm/i915/display/intel_fb_pin.c
>> @@ -50,7 +50,18 @@ intel_pin_fb_obj_dpt(struct drm_framebuffer *fb,
>> continue;
>> if (HAS_LMEM(dev_priv)) {
>> - ret = i915_gem_object_migrate(obj, &ww,
>> INTEL_REGION_LMEM_0);
>> + unsigned int flags = obj->flags;
>> +
>> + /*
>> + * For this type of buffer we need to able to read from
>> the CPU
>> + * the clear color value found in the buffer, hence we
>> need to
>> + * ensure it is always in the mappable part of lmem, if
>> this is
>> + * a small-bar device.
>> + */
>> + if (intel_fb_rc_ccs_cc_plane(fb) >= 0)
>> + flags &= ~I915_BO_ALLOC_GPU_ONLY;
>> + ret = __i915_gem_object_migrate(obj, &ww,
>> INTEL_REGION_LMEM_0,
>> + flags);
>> if (ret)
>> continue;
>> }
next prev parent reply other threads:[~2022-10-11 14:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 13:19 [Intel-gfx] [PATCH v5 1/5] drm/i915: remove the TODO in pin_and_fence_fb_obj Matthew Auld
2022-10-04 13:19 ` [Intel-gfx] [PATCH v5 2/5] drm/i915/display: handle migration for dpt Matthew Auld
2022-10-04 13:31 ` Ville Syrjälä
2022-10-04 13:19 ` [Intel-gfx] [PATCH v5 3/5] drm/i915: allow control over the flags when migrating Matthew Auld
2022-10-04 13:19 ` [Intel-gfx] [PATCH v5 4/5] drm/i915/display: consider DG2_RC_CCS_CC when migrating buffers Matthew Auld
2022-10-04 13:39 ` Ville Syrjälä
2022-10-04 13:40 ` Das, Nirmoy
2022-10-11 13:54 ` Tvrtko Ursulin
2022-10-11 14:39 ` Matthew Auld [this message]
2022-10-11 15:03 ` Tvrtko Ursulin
2022-10-11 15:28 ` Matthew Auld
2022-10-11 16:35 ` Tvrtko Ursulin
2022-10-04 13:19 ` [Intel-gfx] [PATCH v5 5/5] drm/i915: check memory is mappable in read_from_page Matthew Auld
2022-10-04 19:28 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v5,1/5] drm/i915: remove the TODO in pin_and_fence_fb_obj Patchwork
2022-10-04 19:28 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-04 19:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-05 5:41 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-10-04 10:51 [Intel-gfx] [PATCH v5 1/5] " Matthew Auld
2022-10-04 10:51 ` [Intel-gfx] [PATCH v5 4/5] drm/i915/display: consider DG2_RC_CCS_CC when migrating buffers Matthew Auld
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=519a0e90-3396-ba3e-5b82-e9d0dc9c452e@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jianshui.yu@intel.com \
--cc=nirmoy.das@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