All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v2] tests/perf_pmu: Avoid RT thread for accuracy test
Date: Tue, 03 Apr 2018 17:24:08 +0100	[thread overview]
Message-ID: <152277264848.32747.5978450744595739772@mail.alporthouse.com> (raw)
In-Reply-To: <0e9ca619-ac6b-ada1-cb2e-1cbbd8ae3170@linux.intel.com>

Quoting Tvrtko Ursulin (2018-04-03 17:09:09)
> 
> On 03/04/2018 14:10, Chris Wilson wrote:
> > To me it seems like the closed system with each loop being "spin then
> > adjusted sleep" will autocorrect and more likely to finish correct (as
> > we are less reliant on the next loop for the accuracy). It's pretty much
> > immaterial, as we expect the pmu to match the measurements (and not our
> > expectations), but I find the one pass does all much simpler to follow.
> 
> Since we do a good number of loops, and hope the calibration will 
> converge quickly (which it does for me), I don't see that there is an 
> issue there.

I'm sitting here drinking coffee trying to decide if it does converge ;)
That's the problem here, I need to actually find a pencil, some paper
and remember some basic maths for series convergence. Not happening with
the amount of coffee I need to drink at the moment.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t v2] tests/perf_pmu: Avoid RT thread for accuracy test
Date: Tue, 03 Apr 2018 17:24:08 +0100	[thread overview]
Message-ID: <152277264848.32747.5978450744595739772@mail.alporthouse.com> (raw)
In-Reply-To: <0e9ca619-ac6b-ada1-cb2e-1cbbd8ae3170@linux.intel.com>

Quoting Tvrtko Ursulin (2018-04-03 17:09:09)
> 
> On 03/04/2018 14:10, Chris Wilson wrote:
> > To me it seems like the closed system with each loop being "spin then
> > adjusted sleep" will autocorrect and more likely to finish correct (as
> > we are less reliant on the next loop for the accuracy). It's pretty much
> > immaterial, as we expect the pmu to match the measurements (and not our
> > expectations), but I find the one pass does all much simpler to follow.
> 
> Since we do a good number of loops, and hope the calibration will 
> converge quickly (which it does for me), I don't see that there is an 
> issue there.

I'm sitting here drinking coffee trying to decide if it does converge ;)
That's the problem here, I need to actually find a pencil, some paper
and remember some basic maths for series convergence. Not happening with
the amount of coffee I need to drink at the moment.
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2018-04-03 16:24 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 10:57 [CI i-g-t] tests/perf_pmu: Avoid RT thread for accuracy test Tvrtko Ursulin
2018-03-26 10:57 ` [Intel-gfx] " Tvrtko Ursulin
2018-03-26 11:17 ` [igt-dev] " Chris Wilson
2018-03-26 11:17   ` Chris Wilson
2018-03-26 12:40   ` Tvrtko Ursulin
2018-03-26 12:40     ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-03-26 11:23 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-03-26 13:04 ` [igt-dev] ✗ Fi.CI.IGT: warning " Patchwork
2018-03-27 14:31 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2018-03-27 17:08 ` [igt-dev] ✗ Fi.CI.BAT: warning " Patchwork
2018-03-28  9:22 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-03-28 14:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-03-28 16:56   ` Tvrtko Ursulin
2018-03-28 17:10     ` Chris Wilson
2018-04-03 12:38 ` [PATCH i-g-t v2] " Tvrtko Ursulin
2018-04-03 12:38   ` [Intel-gfx] " Tvrtko Ursulin
2018-04-03 13:10   ` Chris Wilson
2018-04-03 13:10     ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-03 16:09     ` Tvrtko Ursulin
2018-04-03 16:09       ` [Intel-gfx] " Tvrtko Ursulin
2018-04-03 16:24       ` Chris Wilson [this message]
2018-04-03 16:24         ` [igt-dev] " Chris Wilson
2018-04-03 16:39   ` [PATCH i-g-t v3] " Tvrtko Ursulin
2018-04-03 16:39     ` [igt-dev] " Tvrtko Ursulin
2018-04-04  9:51     ` [PATCH i-g-t v4] " Tvrtko Ursulin
2018-04-04  9:51       ` [Intel-gfx] " Tvrtko Ursulin
2018-04-11 13:23       ` Chris Wilson
2018-04-11 13:23         ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-11 13:52         ` Tvrtko Ursulin
2018-04-11 13:52           ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-04-14 11:35           ` Chris Wilson
2018-04-14 11:35             ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-16  9:55             ` Tvrtko Ursulin
2018-04-16  9:55               ` [igt-dev] [Intel-gfx] " Tvrtko Ursulin
2018-04-16 10:08               ` Chris Wilson
2018-04-16 10:08                 ` [igt-dev] [Intel-gfx] " Chris Wilson
2018-04-03 14:23 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev2) Patchwork
2018-04-03 16:41 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-04-03 17:15 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev3) Patchwork
2018-04-03 18:33 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2018-04-04 11:13   ` Tvrtko Ursulin
2018-04-04 13:46 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/perf_pmu: Avoid RT thread for accuracy test (rev4) Patchwork
2018-04-04 16:58 ` [igt-dev] ✓ Fi.CI.IGT: " 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=152277264848.32747.5978450744595739772@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=Intel-gfx@lists.freedesktop.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    --cc=tvrtko.ursulin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.