public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
	Patchwork <patchwork@emeril.freedesktop.org>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Tomi Sarvela <tomi.p.sarvela@intel.com>,
	Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Subject: Re: ✓ Fi.CI.BAT: success for IGT PMU support (rev18)
Date: Wed, 22 Nov 2017 11:57:19 +0000	[thread overview]
Message-ID: <e7d8a733-4259-aee1-e80b-9b23ef1cfc01@linux.intel.com> (raw)
In-Reply-To: <20171122114132.7156.70610@emeril.freedesktop.org>


Hi guys,

On 22/11/2017 11:41, Patchwork wrote:

[snip]

> Testlist changes:
> +igt@perf_pmu@all-busy-check-all
> +igt@perf_pmu@busy-bcs0
> +igt@perf_pmu@busy-check-all-bcs0
> +igt@perf_pmu@busy-check-all-rcs0
> +igt@perf_pmu@busy-check-all-vcs0
> +igt@perf_pmu@busy-check-all-vcs1
> +igt@perf_pmu@busy-check-all-vecs0
> +igt@perf_pmu@busy-no-semaphores-bcs0
> +igt@perf_pmu@busy-no-semaphores-rcs0
> +igt@perf_pmu@busy-no-semaphores-vcs0
> +igt@perf_pmu@busy-no-semaphores-vcs1
> +igt@perf_pmu@busy-no-semaphores-vecs0
> +igt@perf_pmu@busy-rcs0
> +igt@perf_pmu@busy-vcs0
> +igt@perf_pmu@busy-vcs1
> +igt@perf_pmu@busy-vecs0
> +igt@perf_pmu@cpu-hotplug
> +igt@perf_pmu@event-wait-rcs0
> +igt@perf_pmu@frequency
> +igt@perf_pmu@idle-bcs0
> +igt@perf_pmu@idle-no-semaphores-bcs0
> +igt@perf_pmu@idle-no-semaphores-rcs0
> +igt@perf_pmu@idle-no-semaphores-vcs0
> +igt@perf_pmu@idle-no-semaphores-vcs1
> +igt@perf_pmu@idle-no-semaphores-vecs0
> +igt@perf_pmu@idle-rcs0
> +igt@perf_pmu@idle-vcs0
> +igt@perf_pmu@idle-vcs1
> +igt@perf_pmu@idle-vecs0
> +igt@perf_pmu@init-busy-bcs0
> +igt@perf_pmu@init-busy-rcs0
> +igt@perf_pmu@init-busy-vcs0
> +igt@perf_pmu@init-busy-vcs1
> +igt@perf_pmu@init-busy-vecs0
> +igt@perf_pmu@init-sema-bcs0
> +igt@perf_pmu@init-sema-rcs0
> +igt@perf_pmu@init-sema-vcs0
> +igt@perf_pmu@init-sema-vcs1
> +igt@perf_pmu@init-sema-vecs0
> +igt@perf_pmu@init-wait-bcs0
> +igt@perf_pmu@init-wait-rcs0
> +igt@perf_pmu@init-wait-vcs0
> +igt@perf_pmu@init-wait-vcs1
> +igt@perf_pmu@init-wait-vecs0
> +igt@perf_pmu@interrupts
> +igt@perf_pmu@invalid-init
> +igt@perf_pmu@most-busy-check-all-bcs0
> +igt@perf_pmu@most-busy-check-all-rcs0
> +igt@perf_pmu@most-busy-check-all-vcs0
> +igt@perf_pmu@most-busy-check-all-vcs1
> +igt@perf_pmu@most-busy-check-all-vecs0
> +igt@perf_pmu@multi-client-bcs0
> +igt@perf_pmu@multi-client-rcs0
> +igt@perf_pmu@multi-client-vcs0
> +igt@perf_pmu@multi-client-vcs1
> +igt@perf_pmu@multi-client-vecs0
> +igt@perf_pmu@other-init-0
> +igt@perf_pmu@other-init-1
> +igt@perf_pmu@other-init-2
> +igt@perf_pmu@other-init-3
> +igt@perf_pmu@other-init-4
> +igt@perf_pmu@other-init-5
> +igt@perf_pmu@other-init-6
> +igt@perf_pmu@other-read-0
> +igt@perf_pmu@other-read-1
> +igt@perf_pmu@other-read-2
> +igt@perf_pmu@other-read-3
> +igt@perf_pmu@other-read-4
> +igt@perf_pmu@other-read-5
> +igt@perf_pmu@other-read-6
> +igt@perf_pmu@rc6
> +igt@perf_pmu@rc6p
> +igt@perf_pmu@render-node-busy-bcs0
> +igt@perf_pmu@render-node-busy-rcs0
> +igt@perf_pmu@render-node-busy-vcs0
> +igt@perf_pmu@render-node-busy-vcs1
> +igt@perf_pmu@render-node-busy-vecs0
> +igt@perf_pmu@semaphore-wait-bcs0
> +igt@perf_pmu@semaphore-wait-rcs0
> +igt@perf_pmu@semaphore-wait-vcs0
> +igt@perf_pmu@semaphore-wait-vcs1
> +igt@perf_pmu@semaphore-wait-vecs0

Would it be possible to have a test run of these new tests on the shards?

If successful then we can add it to the testlist. Total runtime should 
be up to 30 seconds.

But I wouldn't be surprised if there will be issues since I was only 
able to test on SKL during development.

Regards,

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

  reply	other threads:[~2017-11-22 11:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10  9:29 [PATCH v4 i-g-t 0/7] IGT PMU support Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 1/9] intel-gpu-overlay: Move local perf implementation to a library Tvrtko Ursulin
2017-11-21 19:34   ` [PATCH i-g-t v3 " Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 2/9] intel-gpu-overlay: Consolidate perf PMU access to library Tvrtko Ursulin
2017-10-10 12:21   ` Chris Wilson
2017-10-10  9:30 ` [PATCH i-g-t 3/9] lib/perf: Fix data types and general tidy Tvrtko Ursulin
2017-10-10 12:22   ` Chris Wilson
2017-10-10  9:30 ` [PATCH i-g-t 4/9] intel-gpu-overlay: Fix interrupts PMU readout Tvrtko Ursulin
2017-10-10 12:23   ` Chris Wilson
2017-10-10 14:17     ` [PATCH i-g-t v2 " Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 5/9] intel-gpu-overlay: Catch-up to new i915 PMU Tvrtko Ursulin
2017-11-21 18:20   ` Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 6/9] intel-gpu-overlay: Use RAPL PMU for power reading Tvrtko Ursulin
2017-10-10 11:30   ` [PATCH i-g-t v2 " Tvrtko Ursulin
2017-10-10 12:05     ` [PATCH i-g-t v3 " Tvrtko Ursulin
2017-10-10 12:25       ` Chris Wilson
2017-11-21 19:35       ` [PATCH i-g-t v4 " Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 7/9] tests/perf_pmu: Tests for i915 PMU API Tvrtko Ursulin
2017-10-10 12:37   ` Chris Wilson
2017-10-10 13:38     ` Tvrtko Ursulin
2017-10-10 13:46       ` Chris Wilson
2017-10-10 14:17         ` [PATCH i-g-t v6 " Tvrtko Ursulin
2017-10-10 16:39           ` Chris Wilson
2017-10-11 12:54             ` [PATCH i-g-t v7 " Tvrtko Ursulin
2017-11-21 11:50               ` Chris Wilson
2017-11-21 18:21               ` [PATCH i-g-t v8 " Tvrtko Ursulin
2017-11-21 19:36                 ` [PATCH i-g-t v9 " Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 8/9] gem_wsim: Busy stats balancers Tvrtko Ursulin
2017-11-21 19:37   ` [PATCH i-g-t v3 " Tvrtko Ursulin
2017-10-10  9:30 ` [PATCH i-g-t 9/9] media-bench.pl: Add busy balancers to the list Tvrtko Ursulin
2017-11-21 11:51   ` Chris Wilson
2017-10-10  9:42 ` ✗ Fi.CI.BAT: failure for IGT PMU support (rev7) Patchwork
2017-10-10 12:06 ` ✓ Fi.CI.BAT: success for IGT PMU support (rev8) Patchwork
2017-10-10 13:48 ` ✓ Fi.CI.BAT: success for IGT PMU support (rev9) Patchwork
2017-10-10 15:19 ` ✗ Fi.CI.IGT: failure for IGT PMU support (rev8) Patchwork
2017-10-10 18:42 ` ✓ Fi.CI.BAT: success for IGT PMU support (rev11) Patchwork
2017-10-11  1:28 ` ✓ Fi.CI.IGT: " Patchwork
2017-10-11 14:09 ` ✓ Fi.CI.BAT: success for IGT PMU support (rev12) Patchwork
2017-10-11 20:16 ` ✗ Fi.CI.IGT: failure " Patchwork
2017-11-22 11:41 ` ✓ Fi.CI.BAT: success for IGT PMU support (rev18) Patchwork
2017-11-22 11:57   ` Tvrtko Ursulin [this message]
2017-11-22 12:47     ` Petri Latvala
2017-11-22 14:31 ` ✓ Fi.CI.IGT: " Patchwork
2017-11-22 14:39   ` Petri Latvala
2017-11-22 14:50     ` Petri Latvala
2017-11-22 17:09     ` Tvrtko Ursulin

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=e7d8a733-4259-aee1-e80b-9b23ef1cfc01@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=arkadiusz.hiler@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=patchwork@emeril.freedesktop.org \
    --cc=tomi.p.sarvela@intel.com \
    --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