From: Zhao Yakui <yakui.zhao@intel.com>
To: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH I-g-t V4 0/2] Tests: Add test cases based on multi drm_fd to test sync
Date: Thu, 24 Apr 2014 10:20:06 +0800 [thread overview]
Message-ID: <1398306006.2045.195.camel@genxdev-ykzhao.sh.intel.com> (raw)
In-Reply-To: <1398304966-15651-1-git-send-email-yakui.zhao@intel.com>
On Wed, 2014-04-23 at 20:02 -0600, Zhao, Yakui wrote:
It seems that the patch 01 is filter out.
So I will try to resend it again.
Thanks.
Yakui
> This follows Daniel's advice to add the two test cases based on multi drm_fd to
> test the ring sync and CPU<->GPU sync.
> The Broadwell GT3 machine has two independent BSD rings that can be used
> to process the video commands. This is implemented in kernel driver and transparent
> to the user-space. But we still need to check the ring sync and CPU<->GPU sync for
> the second BSD ring. Two tests are created based on the multi drm_fds to
> test the sync. Multi drm_fd can assure that the second BSD ring has the opportunity
> to dispatch the GPU command.
>
> V1->V2: Follow Daniel's comment to add one subtext instead of one individual
> test case, which is used to test the CPU<->GPU sync under multi BSD rings/
>
> V2->V3: Follow Imre's comment to remove the unnecessary initialization and
> use igt_assert_f instead of igt_assert
>
>
> Zhao Yakui (2):
> tests: Add one ring sync case based on multi drm_fd to test ring
> semaphore sync under multi BSD rings
> tests/gem_dummy_reloc_loop: Add one subtest based on multi drm_fd to
> test CPU<->GPU sync under multi BSD rings
>
> tests/.gitignore | 1 +
> tests/Makefile.sources | 1 +
> tests/gem_dummy_reloc_loop.c | 107 +++++++++++++++++++++++-
> tests/gem_multi_bsd_sync_loop.c | 175 +++++++++++++++++++++++++++++++++++++++
> 4 files changed, 283 insertions(+), 1 deletion(-)
> create mode 100644 tests/gem_multi_bsd_sync_loop.c
>
next prev parent reply other threads:[~2014-04-24 2:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 2:02 [PATCH I-g-t V4 0/2] Tests: Add test cases based on multi drm_fd to test sync Zhao Yakui
2014-04-24 2:02 ` [PATCH I-g-t 2/2] tests/gem_dummy_reloc_loop: Add one subtest based on multi drm_fd to test CPU<->GPU sync under multi BSD rings Zhao Yakui
2014-04-24 2:20 ` Zhao Yakui [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-24 2:15 [PATCH I-g-t V4 0/2] Tests: Add test cases based on multi drm_fd to test sync Zhao Yakui
2014-04-24 9:54 ` Daniel Vetter
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=1398306006.2045.195.camel@genxdev-ykzhao.sh.intel.com \
--to=yakui.zhao@intel.com \
--cc=intel-gfx@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