Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915/perf: Subtract gtt_offset from hw_tail
Date: Tue, 18 Jul 2023 10:17:11 -0700	[thread overview]
Message-ID: <87y1jd9m20.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <46c126f6-5287-7e83-9e79-20b3662fccbe@intel.com>

On Tue, 18 Jul 2023 01:39:35 -0700, Lionel Landwerlin wrote:
>

Hi Lionel,

> On 18/07/2023 05:43, Ashutosh Dixit wrote:
> > The code in oa_buffer_check_unlocked() is correct only if the OA buffer is
> > 16 MB aligned (which seems to be the case today in i915). However when the
> > 16 MB alignment is dropped, when we "Subtract partial amount off the tail",
> > the "& (OA_BUFFER_SIZE - 1)" operation in OA_TAKEN() will result in an
> > incorrect hw_tail value.
> >
> > Therefore hw_tail must be brought to the same base as head and read_tail
> > prior to OA_TAKEN by subtracting gtt_offset from hw_tail.
> >
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > ---
> >   drivers/gpu/drm/i915/i915_perf.c | 1 +
> >   1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> > index 49c6f1ff11284..f7888a44d1284 100644
> > --- a/drivers/gpu/drm/i915/i915_perf.c
> > +++ b/drivers/gpu/drm/i915/i915_perf.c
> > @@ -565,6 +565,7 @@ static bool oa_buffer_check_unlocked(struct i915_perf_stream *stream)
> >	partial_report_size %= report_size;
> >		/* Subtract partial amount off the tail */
> > +	hw_tail -= gtt_offset;
> >	hw_tail = OA_TAKEN(hw_tail, partial_report_size);
> >		/* NB: The head we observe here might effectively be a little
>
>
> You should squash this patch with the next one. Otherwise further down this
> function there is another
>
> hw_tail -= gtt_offset;

Are you looking at old code, because this line is not there in this
function any more. There have been several changes to the function lately,
aging tail etc. is gone e.g.

But otherwise you are right, Patch 2 basically writes over Patch 1, so the
two patches can be squashed. I separated out Patch 1 since it shows the bug
(incidentally the bug doesn't show up in i915 since a 16 MB BO in i915 is
16 MB aligned, I discovered the bug while porting stuff to xe).

So if you are going to R-b this series I can repost after squashing. But if
we wait for Umesh to return (he is out till the end of the month) and
review this, I'd rather leave the two patches as they are till Umesh
reviews them.

Thanks.
--
Ashutosh

  reply	other threads:[~2023-07-18 17:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18  2:43 [Intel-gfx] [PATCH 0/2] gtt_offset and OA buffer cached head/tail Ashutosh Dixit
2023-07-18  2:43 ` [Intel-gfx] [PATCH 1/2] drm/i915/perf: Subtract gtt_offset from hw_tail Ashutosh Dixit
2023-07-18  8:39   ` Lionel Landwerlin
2023-07-18 17:17     ` Dixit, Ashutosh [this message]
2023-07-18  2:43 ` [Intel-gfx] [PATCH 2/2] drm/i915/perf: Remove gtt_offset from stream->oa_buffer.head/.tail Ashutosh Dixit
2023-07-18  3:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success for gtt_offset and OA buffer cached head/tail Patchwork
2023-07-18  5:38 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=87y1jd9m20.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lionel.g.landwerlin@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