public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx@lists.freedesktop.org,
	Patchwork <patchwork@emeril.freedesktop.org>,
	Tvrtko Ursulin <tursulin@ursulin.net>
Subject: Re: ✗ Fi.CI.IGT: failure for drm/i915: Use seqlock in engine stats (rev2)
Date: Mon, 19 Feb 2018 09:25:00 +0000	[thread overview]
Message-ID: <ac21b342-1487-c0f4-2726-ed0eb4224c13@linux.intel.com> (raw)
In-Reply-To: <151877599503.7225.16711066134170134232@mail.alporthouse.com>


On 16/02/2018 10:13, Chris Wilson wrote:
> Quoting Patchwork (2018-02-15 23:50:52)
>> == Series Details ==
>>
>> Series: drm/i915: Use seqlock in engine stats (rev2)
>> URL   : https://patchwork.freedesktop.org/series/38347/
>> State : failure
>>
>> == Summary ==
>>
>> Test perf_pmu:
>>          Subgroup busy-start-vcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup busy-idle-check-all-vecs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup render-node-busy-idle-vcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup most-busy-idle-check-all-bcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup busy-idle-check-all-bcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup most-busy-check-all-bcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup render-node-busy-bcs0:
>>                  pass       -> DMESG-WARN (shard-apl)
>>          Subgroup busy-idle-vecs0:
>>                  pass       -> DMESG-WARN (shard-apl)
> 
> Afaict, it's complaining that because the writer is special the reader
> needs irq protection. Which I don't understand, as the point is that the
> writer can run concurrently to the readers (the readers have to
> restart). What am I missing?

As discussed on IRC, issue is courtesy of perf read callback running in 
hardirq context, that the reader can interrupt the writer and so 
incorrectly declare a stable sequence number while reading the mixed up 
version of the underlying data.

Writer:
   seqno++
   modify some fields
   <Reader IRQ...
     read seqno
     read fields
     re-read seqno -> OK
   >..Reader IRQ
   modify other fields
   seqno++

So we need to go back to the first, irqsave version. Do you want to 
pursue this change right now or leave it for some future work?

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-02-19  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-15 11:13 [PATCH] drm/i915: Use seqlock in engine stats Tvrtko Ursulin
2018-02-15 11:47 ` Chris Wilson
2018-02-15 11:59   ` Tvrtko Ursulin
2018-02-15 12:04     ` Chris Wilson
2018-02-15 13:45       ` [PATCH v2] " Tvrtko Ursulin
2018-02-15 11:47 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-02-15 14:50 ` ✓ Fi.CI.BAT: success for drm/i915: Use seqlock in engine stats (rev2) Patchwork
2018-02-15 23:50 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-02-16 10:13   ` Chris Wilson
2018-02-19  9:25     ` Tvrtko Ursulin [this message]
2018-02-19  9:29       ` Chris Wilson

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=ac21b342-1487-c0f4-2726-ed0eb4224c13@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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