From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
arjun.melkaveri@intel.com, igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] i915/gem_exec_nop:Adjusted test to utilize all available engines
Date: Tue, 21 Jan 2020 13:50:34 +0000 [thread overview]
Message-ID: <bd4c78e6-59fd-ebdd-d18e-0c8cbf0d30ac@linux.intel.com> (raw)
In-Reply-To: <157961043554.3096.4464531165987455648@skylake-alporthouse-com>
On 21/01/2020 12:40, Chris Wilson wrote:
> Quoting Arjun Melkaveri (2020-01-21 12:31:20)
>> Added __for_each_physical_engine to utilize all available engines.
>> Moved single, signal, preempt, poll and headless test cases
>> from static to dynamic group.
>
> But doesn't this prevent us from exercising the legacy ABI?
It was my suggestion that for gem_exec_nop (measuring execution speed)
we don't care about legacy ABI.
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:[~2020-01-21 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 12:31 [igt-dev] [PATCH i-g-t] i915/gem_exec_nop:Adjusted test to utilize all available engines Arjun Melkaveri
2020-01-21 12:40 ` Chris Wilson
2020-01-21 13:50 ` Tvrtko Ursulin [this message]
2020-01-21 13:56 ` Chris Wilson
2020-01-21 14:35 ` Chris Wilson
2020-01-21 13:20 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-21 13:51 ` [igt-dev] [PATCH i-g-t] " Tvrtko Ursulin
2020-01-21 14:26 ` Tvrtko Ursulin
2020-01-21 14:36 ` Melkaveri, Arjun
2020-01-22 10:22 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=bd4c78e6-59fd-ebdd-d18e-0c8cbf0d30ac@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=arjun.melkaveri@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
/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