From: Dominik Grzegorzek <dominik.grzegorzek@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 0/3] tests/gem_exec_alignment.c: Update subtests
Date: Thu, 12 Mar 2020 10:09:30 +0100 [thread overview]
Message-ID: <20200312090933.20001-1-dominik.grzegorzek@intel.com> (raw)
Changes modify many subtest, and implement priority inversion test
case. Splited into three patches due to code sections shared between
pi and many subtest. "PATCH i-g-t 1/3 tests/gem_exec_alignment.c: Timeout
alarm wrappers" has no sense without at least one of next patches.
Dominik Grzegorzek (3):
tests/gem_exec_alignment.c: Timeout alarm wrappers
tests/gem_exec_alignment.c: Update subtest many
tests/gem_exec_alignment.c: Add priority inversion test
tests/i915/gem_exec_alignment.c | 283 +++++++++++++++++++++++++++++---
1 file changed, 260 insertions(+), 23 deletions(-)
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-03-12 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 9:09 Dominik Grzegorzek [this message]
2020-03-12 9:09 ` [igt-dev] [PATCH i-g-t 1/3] tests/gem_exec_alignment.c: Timeout alarm wrappers Dominik Grzegorzek
2020-03-12 9:09 ` [igt-dev] [PATCH i-g-t 2/3] tests/gem_exec_alignment.c: Update subtest many Dominik Grzegorzek
2020-03-12 9:09 ` [igt-dev] [PATCH i-g-t 3/3] tests/gem_exec_alignment.c: Add priority inversion test Dominik Grzegorzek
2020-03-12 9:32 ` [igt-dev] ✗ GitLab.Pipeline: failure for tests/gem_exec_alignment.c: Update subtests Patchwork
2020-03-12 9:47 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2020-03-12 10:06 ` [igt-dev] [PATCH i-g-t 0/3] " Chris Wilson
2020-03-13 2:37 ` [igt-dev] ✗ Fi.CI.IGT: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-03-16 12:03 [igt-dev] [PATCH i-g-t 0/3] " Dominik Grzegorzek
2020-03-19 7:38 Dominik Grzegorzek
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=20200312090933.20001-1-dominik.grzegorzek@intel.com \
--to=dominik.grzegorzek@intel.com \
--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