From: Andi Shyti <andi@etezian.org>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: IGT dev <igt-dev@lists.freedesktop.org>, Andi Shyti <andi@etezian.org>
Subject: Re: [igt-dev] [PATCH v21 6/6] test: perf_pmu: use the gem_engine_topology library
Date: Wed, 17 Apr 2019 02:05:11 +0300 [thread overview]
Message-ID: <20190416230511.GA14233@jack.zhora.eu> (raw)
In-Reply-To: <af7395ff-d54e-ac6d-1fe5-98e455f7e5f2@linux.intel.com>
> > @@ -1046,14 +1057,18 @@ static void cpu_hotplug(int gem_fd)
> > igt_require(cpu0_hotplug_support());
> > + ctx = gem_context_create(gem_fd);
>
> TODO left was to try without new contexts for a handful of tests where I
> added them. Instead try I915_EXEC_DEFAULT when submitting and (ab)use the
> fact RCS is at index zero for foreseeable future. When it fails we'll know
> about it. This applies to hotplug, frequency, interrupts subtests AFAIR.
yes, I was also thinking about adding a few wrappers around.
I managed to build quite a hefty list of things to do in these 21
versions (22 with the coming)
But I would happily send them once this series gets accepted to
not procrastinate it further.
Thanks,
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-04-16 23:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:11 [igt-dev] [PATCH v21 0/6] new engine discovery interface Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 1/6] include/drm-uapi: import i915_drm.h header file Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 2/6] lib/i915: add gem_engine_topology library and for_each loop definition Andi Shyti
2019-04-16 15:21 ` Chris Wilson
2019-04-16 15:28 ` Andi Shyti
2019-04-16 17:09 ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 3/6] lib: igt_gt: add execution buffer flags to class helper Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 4/6] lib: igt_gt: make gem_engine_can_store_dword() check engine class Andi Shyti
2019-04-16 15:11 ` [igt-dev] [PATCH v21 5/6] lib: igt_dummyload: use for_each_context_engine() Andi Shyti
2019-04-17 15:42 ` Daniele Ceraolo Spurio
2019-04-17 15:48 ` Chris Wilson
2019-04-17 16:14 ` Tvrtko Ursulin
2019-04-17 16:21 ` Chris Wilson
2019-04-18 8:46 ` Tvrtko Ursulin
2019-04-16 15:11 ` [igt-dev] [PATCH v21 6/6] test: perf_pmu: use the gem_engine_topology library Andi Shyti
2019-04-16 17:06 ` Tvrtko Ursulin
2019-04-16 23:05 ` Andi Shyti [this message]
2019-04-17 13:42 ` Tvrtko Ursulin
2019-04-16 16:36 ` [igt-dev] ✓ Fi.CI.BAT: success for new engine discovery interface Patchwork
2019-04-17 0:46 ` [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=20190416230511.GA14233@jack.zhora.eu \
--to=andi@etezian.org \
--cc=igt-dev@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox