Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dong, Zhanjun" <zhanjun.dong@intel.com>
To: "Yang, Fei" <fei.yang@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Remove incorrect hard coded cache coherrency setting
Date: Fri, 23 Jun 2023 14:02:01 -0400	[thread overview]
Message-ID: <0ef48abf-a0d6-7ec6-82ac-afd7d83947cc@intel.com> (raw)
In-Reply-To: <BYAPR11MB2567EBC3DA33B7D1D4DABD599A22A@BYAPR11MB2567.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2240 bytes --]

Hi Fei,

Thanks for review. I put my answers inline below.

Regards,

Zhanjun

On 2023-06-22 6:20 p.m., Yang, Fei wrote:
> > The previouse i915_gem_object_create_internal already set it with 
> proper
> > value before function return. This hard coded setting is incorrect for
> > platforms like MTL, thus need to be removed.
> >
> > Signed-off-by: Zhanjun Dong <zhanjun.dong@intel.com>
> > ---
> >  drivers/gpu/drm/i915/gt/intel_timeline.c | 2 --
> >  1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_timeline.c 
> b/drivers/gpu/drm/i915/gt/intel_timeline.c
> > index b9640212d659..693d18e14b00 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_timeline.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_timeline.c
> > @@ -26,8 +26,6 @@ static struct i915_vma *hwsp_alloc(struct intel_gt 
> *gt)
> >          if (IS_ERR(obj))
> >                  return ERR_CAST(obj);
> >
> > - i915_gem_object_set_cache_coherency(obj, I915_CACHE_LLC);
> > -
>
> Does this change really fix the coherency issue?

Testing in progress. Issue reported by E2E team, now is their public 
holiday. Meanwhile, I have trouble to run the test case on my setup. 
Need to sync with them later.


> I consulted with Chris and he said that the hwsp is purposely set to be
> cacheable. The mapping on CPU side also indicates it's cacheable,

For single end access area that setting works well. Here the problem is 
the head/tail memory area requires different cache setting.

As  the previous i915_gem_object_create_internal already set the cache 
setting for current platform properly, why we overwrite it here?


>
> intel_timeline_pin_map(struct intel_timeline *timeline)
>         {
>                 struct drm_i915_gem_object *obj = 
> timeline->hwsp_ggtt->obj;
>                 u32 ofs = offset_in_page(timeline->hwsp_offset);
>                 void *vaddr;
>
>                 vaddr = i915_gem_object_pin_map(obj, I915_MAP_WB);
>                 ...
>         }
Maybe we should also set it to match platform as well?
>
> >          vma = i915_vma_instance(obj, &gt->ggtt->vm, NULL);
> >          if (IS_ERR(vma))
> >  i915_gem_object_put(obj);
> > --
> > 2.34.1
>

[-- Attachment #2: Type: text/html, Size: 43160 bytes --]

  reply	other threads:[~2023-06-23 18:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 15:26 [Intel-gfx] [PATCH] drm/i915/gt: Remove incorrect hard coded cache coherrency setting Zhanjun Dong
2023-06-22 15:29 ` Dong, Zhanjun
2023-06-22 18:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt: Remove incorrect hard coded cache coherrency setting (rev2) Patchwork
2023-06-22 22:20 ` [Intel-gfx] [PATCH] drm/i915/gt: Remove incorrect hard coded cache coherrency setting Yang, Fei
2023-06-23 18:02   ` Dong, Zhanjun [this message]
2023-06-23  7:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/gt: Remove incorrect hard coded cache coherrency setting (rev2) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-06-16 22:11 [Intel-gfx] [PATCH] drm/i915/gt: Remove incorrect hard coded cache coherrency setting Zhanjun Dong
2023-06-22 12:27 ` Nirmoy Das

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=0ef48abf-a0d6-7ec6-82ac-afd7d83947cc@intel.com \
    --to=zhanjun.dong@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fei.yang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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