intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Clear the whole first page of LRC on gen9
Date: Tue, 21 Jan 2020 13:50:38 +0000	[thread overview]
Message-ID: <157961463891.4434.14485421708219131239@skylake-alporthouse-com> (raw)
In-Reply-To: <87lfq0q5zd.fsf@gaia.fi.intel.com>

Quoting Mika Kuoppala (2020-01-21 13:44:22)
> Chris Wilson <chris@chris-wilson.co.uk> writes:
> 
> > Try clearing the whole first page of the LRC on gen9, just in case HW
> 
> First page of LRC is a bit misleading as this is first page of
> LRC registers and techincally first page of LRC would be hwsp?

I refer to the "Logical Ring" :)

> So,
> 
> s/LRC/LRC register state
> 
> > tries peeking at the poisoned data.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> > ---
> >  drivers/gpu/drm/i915/gt/intel_lrc.c | 16 ++++++++--------
> >  1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> > index 2d6b41e66b16..bf0c5a998428 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> > @@ -549,7 +549,7 @@ static void set_offsets(u32 *regs,
> >       }
> >  
> >       if (clear) {
> > -             u8 count = *++data;
> > +             unsigned int count = *++data * 16u;
> 
> Nitpick: const 
> 
> >  
> >               /* Clear past the tail for HW access */
> >               GEM_BUG_ON(dword_in_page(regs) > count);
> 
> You might want to add also check that you dont write past page.
> As this seems to be always confined inside a page.
> 
> No other complaints, and above are minor so
> 
> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>

It didn't stop gen9 from eating the poison, so something else is afoot.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2020-01-21 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 10:52 [Intel-gfx] [PATCH] drm/i915/gt: Clear the whole first page of LRC on gen9 Chris Wilson
2020-01-18 11:50 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-18 11:50 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-20 21:52 ` [Intel-gfx] ✓ Fi.CI.IGT: success " Patchwork
2020-01-21 13:44 ` [Intel-gfx] [PATCH] " Mika Kuoppala
2020-01-21 13:50   ` Chris Wilson [this message]

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=157961463891.4434.14485421708219131239@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mika.kuoppala@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;
as well as URLs for NNTP newsgroup(s).