From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tursulin@ursulin.net>,
igt-dev@lists.freedesktop.org
Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] tests/perf_pmu: Give sampling more time
Date: Mon, 12 Feb 2018 09:55:21 +0000 [thread overview]
Message-ID: <e3b92e3a-f162-c049-b45f-249d01c1468d@linux.intel.com> (raw)
In-Reply-To: <151807759064.28809.4247346291445702173@mail.alporthouse.com>
On 08/02/2018 08:13, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-02-08 08:01:31)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> We get occasional errors like:
>>
>> (perf_pmu:21315) CRITICAL: Test assertion failure function sema_wait, file perf_pmu.c:631:
>> (perf_pmu:21315) CRITICAL: Failed assertion: (double)(val[1] - val[0]) <= (1.0 + (tolerance)) * (double)(slept) && (double)(val[1] - val[0]) >= (1.0 - (tolerance)) * (double)(slept)
>> (perf_pmu:21315) CRITICAL: 'val[1] - val[0]' != 'slept' (450000000.000000 not within 5.000000% tolerance of 500129618.000000)
>
> Something to remember when reporting pmu errors is whether it's
> sampling. In this case sema_wait is always sampling... But I wonder if
> we can report it from pmu somehow?
Theoretically I think we could add our own file to sysfs, alongside
<counter-name>(.unit|.scale) etc.. like ".resolution" or something. Not
sure how polite that would be though.. not very I think. Alternative
would be to create additional pmu hierarchy in debugfs with this data.
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-02-12 9:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 8:01 [igt-dev] [PATCH i-g-t 1/3] tests/perf_pmu: Use perf timestamps in a few more places Tvrtko Ursulin
2018-02-08 8:01 ` [igt-dev] [PATCH i-g-t 2/3] tests/perf_pmu: Handle thermally throttled devices Tvrtko Ursulin
2018-02-08 8:10 ` Chris Wilson
2018-02-12 9:47 ` [igt-dev] [PATCH i-g-t v2 " Tvrtko Ursulin
2018-02-12 10:00 ` Chris Wilson
2018-02-12 11:35 ` [igt-dev] [PATCH i-g-t v3 " Tvrtko Ursulin
2018-02-08 8:01 ` [igt-dev] [PATCH i-g-t 3/3] tests/perf_pmu: Give sampling more time Tvrtko Ursulin
2018-02-08 8:13 ` Chris Wilson
2018-02-12 9:55 ` Tvrtko Ursulin [this message]
2018-02-12 10:02 ` Chris Wilson
2018-02-12 11:36 ` [igt-dev] [PATCH i-g-t v2 " Tvrtko Ursulin
2018-02-12 11:39 ` Chris Wilson
2018-02-08 8:09 ` [igt-dev] [PATCH i-g-t 1/3] tests/perf_pmu: Use perf timestamps in a few more places Chris Wilson
2018-02-12 9:46 ` [igt-dev] [PATCH i-g-t v2 " Tvrtko Ursulin
2018-02-12 9:57 ` Chris Wilson
2018-02-08 10:27 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] " Patchwork
2018-02-08 15:13 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-02-12 10:28 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/3] tests/perf_pmu: Use perf timestamps in a few more places (rev3) Patchwork
2018-02-12 12:02 ` [igt-dev] ✗ Fi.CI.IGT: warning " Patchwork
2018-02-12 16:44 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v2,1/3] tests/perf_pmu: Use perf timestamps in a few more places (rev5) Patchwork
2018-02-12 17:02 ` Patchwork
2018-02-12 19:00 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-02-12 19:40 ` 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=e3b92e3a-f162-c049-b45f-249d01c1468d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@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