Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/perf: rework aging tail workaround
Date: Sat, 21 Mar 2020 21:44:43 -0700	[thread overview]
Message-ID: <877dzddmmc.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <87zhc9p9vx.wl-ashutosh.dixit@intel.com>

On Sat, 21 Mar 2020 16:26:42 -0700, Dixit, Ashutosh wrote:
>
> On Thu, 19 Mar 2020 15:52:01 -0700, Umesh Nerlige Ramappa wrote:
> >
> > From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>
> > @@ -477,16 +468,6 @@ static bool oa_buffer_check_unlocked(struct i915_perf_stream *stream)
> >	 */
> >	spin_lock_irqsave(&stream->oa_buffer.ptr_lock, flags);
> >
> >	hw_tail = stream->perf->ops.oa_hw_tail_read(stream);
> >
> >	hw_tail &= ~(report_size - 1);
> >
> > @@ -496,64 +477,64 @@ static bool oa_buffer_check_unlocked(struct i915_perf_stream *stream)
> >
> >	now = ktime_get_mono_fast_ns();
> >
> > +	if (hw_tail == stream->oa_buffer.aging_tail &&
> > +	   (now - stream->oa_buffer.aging_timestamp) > OA_TAIL_MARGIN_NSEC) {
> > +		/* If the HW tail hasn't move since the last check and the HW
> > +		 * tail has been aging for long enough, declare it the new
> > +		 * tail.
> > +		 */
> > +		stream->oa_buffer.tail = stream->oa_buffer.aging_tail;
> > +	} else {
> > +		u32 head, tail;
> >
> > +		/* NB: The head we observe here might effectively be a little
> > +		 * out of date. If a read() is in progress, the head could be
> > +		 * anywhere between this head and stream->oa_buffer.tail.
> > +		 */
> > +		head = stream->oa_buffer.head - gtt_offset;
> >
> > +		hw_tail -= gtt_offset;
> > +		tail = hw_tail;
> >
> > +		/* Walk the stream backward until we find a report with dword 0
> > +		 * & 1 not at 0. Since the circular buffer pointers progress by
> > +		 * increments of 64 bytes and that reports can be up to 256
> > +		 * bytes long, we can't tell whether a report has fully landed
> > +		 * in memory before the first 2 dwords of the following report
> > +		 * have effectively landed.
> > +		 *
> > +		 * This is assuming that the writes of the OA unit land in
> > +		 * memory in the order they were written to.
> > +		 * If not : (╯°□°)╯︵ ┻━┻
> >		 */
> > +		while (OA_TAKEN(tail, head) >= report_size) {
> > +			u32 previous_tail = (tail - report_size) & (OA_BUFFER_SIZE - 1);
> > +			u32 *report32 = (void *)(stream->oa_buffer.vaddr + previous_tail);
>
> Sorry, this is wrong. This should just be:
>
>			tail = (tail - report_size) & (OA_BUFFER_SIZE - 1);
>			report32 = (void *)(stream->oa_buffer.vaddr + tail);
>
> Otherwise when we break out of the loop below tail is still set one
> report_size ahead. previous_tail is not needed. (In the previous version of
> the patch this used to work out correctly).
>
> > +
> > +			/* Head of the report indicated by the HW tail register has
> > +			 * indeed landed into memory.
> > +			 */
> > +			if (report32[0] != 0 || report32[1] != 0)
> > +				break;
> > +
> > +			tail = previous_tail;
> >		}

Actually a couple of further improvements to the loop above are
possible. First there is no reason to start at previous_tail, we can just
start at the aligned hw_tail itself. Therefore the loop becomes:

		while (OA_TAKEN(tail, head) >= report_size) {
			u32 *report32 = (void *)(stream->oa_buffer.vaddr + tail);

			if (report32[0] != 0 || report32[1] != 0)
				break;

			tail = (tail - report_size) & (OA_BUFFER_SIZE - 1);
		}

Further, there is no reason to go back to the head but only to the old
tail. Therefore:

		head = stream->oa_buffer.head - gtt_offset;
		old_tail = stream->oa_buffer.tail - gtt_offset;

		hw_tail -= gtt_offset;
		tail = hw_tail;

		while (OA_TAKEN(tail, old_tail) >= report_size) {
			u32 *report32 = (void *)(stream->oa_buffer.vaddr + tail);

			if (report32[0] != 0 || report32[1] != 0)
				break;

			tail = (tail - report_size) & (OA_BUFFER_SIZE - 1);
		}

Please review and see if these two improvements are possible. Thanks!
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2020-03-22  4:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 22:52 [Intel-gfx] [PATCH 0/3] drm/i915/perf: add OA interrupt support Umesh Nerlige Ramappa
2020-03-19 22:52 ` [Intel-gfx] [PATCH 1/3] drm/i915/perf: rework aging tail workaround Umesh Nerlige Ramappa
2020-03-21 23:26   ` Dixit, Ashutosh
2020-03-22  4:44     ` Dixit, Ashutosh [this message]
2020-03-22 19:47       ` Dixit, Ashutosh
2020-03-24  3:17       ` Umesh Nerlige Ramappa
2020-03-24  3:15     ` Umesh Nerlige Ramappa
2020-03-19 22:52 ` [Intel-gfx] [PATCH 2/3] drm/i915/perf: move pollin setup to non hw specific code Umesh Nerlige Ramappa
2020-03-19 22:52 ` [Intel-gfx] [PATCH 3/3] drm/i915/perf: add new open param to configure polling of OA buffer Umesh Nerlige Ramappa
2020-03-21  7:16   ` Dixit, Ashutosh
2020-03-19 23:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/perf: add OA interrupt support (rev7) Patchwork
2020-03-19 23:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-03-20  0:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-03-24 18:54 [Intel-gfx] [PATCH 0/3] drm/i915/perf: add OA interrupt support Umesh Nerlige Ramappa
2020-03-24 18:54 ` [Intel-gfx] [PATCH 1/3] drm/i915/perf: rework aging tail workaround Umesh Nerlige Ramappa
2020-03-24 21:25   ` Dixit, Ashutosh

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=877dzddmmc.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=umesh.nerlige.ramappa@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