Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: 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 11:54:51 +0200	[thread overview]
Message-ID: <20140424093253.GA26374@phenom.ffwll.local> (raw)
In-Reply-To: <1398305745-15846-1-git-send-email-yakui.zhao@intel.com>

On Thu, Apr 24, 2014 at 10:15:43AM +0800, Zhao Yakui wrote:
> 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
> 
> V3->V4: Add gem_multi_bsd_sync_loop.c into the tests/.gitignore
> 
> 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

Merged, thanks for the patches.
-Daniel

> 
>  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
> 
> -- 
> 1.7.10.1
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2014-04-24  9:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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  2:15 ` [PATCH I-g-t V4 1/2] tests: Add one ring sync case based on multi drm_fd to test ring semaphore sync under multi BSD rings Zhao Yakui
2014-04-24  2:15 ` [PATCH I-g-t V4 2/2] tests/gem_dummy_reloc_loop: Add one subtest based on multi drm_fd to test CPU<->GPU " Zhao Yakui
2014-04-24  9:54 ` Daniel Vetter [this message]
  -- strict thread matches above, loose matches on Subject: below --
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:20 ` Zhao Yakui

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=20140424093253.GA26374@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=yakui.zhao@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