From: Andrey Grodzovsky <andrey.grodzovsky@amd.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "Alex Deucher" <Alexander.Deucher@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/7] libdrm tests for hot-unplug feature
Date: Thu, 3 Jun 2021 10:22:37 -0400 [thread overview]
Message-ID: <baf1d1f8-48c7-ed83-8e42-a4a317bfa74d@amd.com> (raw)
In-Reply-To: <de4b3521-42f7-7fc2-7271-e4fa3cd91708@amd.com>
Ping
Andrey
On 2021-06-02 10:20 a.m., Andrey Grodzovsky wrote:
>
> On 2021-06-02 3:59 a.m., Daniel Vetter wrote:
>> On Tue, Jun 1, 2021 at 10:17 PM Andrey Grodzovsky
>> <andrey.grodzovsky@amd.com> wrote:
>>> Adding some tests to acompany the recently added hot-unplug
>>> feature. For now the test suite is disabled until the feature
>>> propagates from drm-misc-next to drm-next.
>>>
>>> Andrey Grodzovsky (7):
>>> tests/amdgpu: Fix valgrind warning
>>> xf86drm: Add function to retrieve char device path
>>> test/amdgpu: Add helper functions for hot unplug
>>> test/amdgpu/hotunplug: Add test suite for GPU unplug
>>> test/amdgpu/hotunplug: Add basic test
>>> tests/amdgpu/hotunplug: Add unplug with cs test.
>>> tests/amdgpu/hotunplug: Add hotunplug with exported bo test
>> Given how nasty hotunplug is I really think collaborating on igt tests
>> on this would be best for everyone ... do we have to keep doing
>> parallel tests here for amdgpu?
>> -Daniel
>
> AFAIK as far as AMD goes a lot of developers use libdrm for regression
> testing
> while developing their features and also QA as i can see from some
> internal ticket
> specifically opened for failing to pass libdrm tests. From my bitter
> experience with
> GPU reset - features which are not part of a common use case such as
> device loading,
> mode setting or commands submissions tend to very quickly break as
> people develop
> features but never test them in those uncommon use cases - this is why
> I feel it will be
> very helpful to include those tests in libdrm.
>
> Also given that this is libdrm amdgpu code it fits naturally into libdrm.
>
> Regarding IGT - as you may remember I have them there too -
> https://gitlab.freedesktop.org/agrodzov/igt-gpu-tools/-/commits/master
> I hit some compile breakage on debian platform there which i need to
> resolve before i will submit for review there too.
>
> Andrey
>
>
>>
>>> tests/amdgpu/amdgpu_test.c | 42 +++-
>>> tests/amdgpu/amdgpu_test.h | 26 +++
>>> tests/amdgpu/basic_tests.c | 5 +-
>>> tests/amdgpu/hotunplug_tests.c | 357
>>> +++++++++++++++++++++++++++++++++
>>> tests/amdgpu/meson.build | 1 +
>>> xf86drm.c | 23 +++
>>> xf86drm.h | 1 +
>>> 7 files changed, 450 insertions(+), 5 deletions(-)
>>> create mode 100644 tests/amdgpu/hotunplug_tests.c
>>>
>>> --
>>> 2.25.1
>>>
>>
next prev parent reply other threads:[~2021-06-03 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 20:16 [PATCH 0/7] libdrm tests for hot-unplug feature Andrey Grodzovsky
2021-06-01 20:16 ` [PATCH 1/7] tests/amdgpu: Fix valgrind warning Andrey Grodzovsky
2021-06-01 20:16 ` [PATCH 2/7] xf86drm: Add function to retrieve char device path Andrey Grodzovsky
2021-06-02 9:16 ` Simon Ser
2021-06-02 14:25 ` Andrey Grodzovsky
2021-06-01 20:16 ` [PATCH 3/7] test/amdgpu: Add helper functions for hot unplug Andrey Grodzovsky
2021-06-01 20:16 ` [PATCH 4/7] test/amdgpu/hotunplug: Add test suite for GPU unplug Andrey Grodzovsky
2021-06-01 20:17 ` [PATCH 5/7] test/amdgpu/hotunplug: Add basic test Andrey Grodzovsky
2021-06-01 20:17 ` [PATCH 6/7] tests/amdgpu/hotunplug: Add unplug with cs test Andrey Grodzovsky
2021-06-01 20:17 ` [PATCH 7/7] tests/amdgpu/hotunplug: Add hotunplug with exported bo test Andrey Grodzovsky
2021-06-02 7:59 ` [PATCH 0/7] libdrm tests for hot-unplug feature Daniel Vetter
2021-06-02 14:20 ` Andrey Grodzovsky
2021-06-03 14:22 ` Andrey Grodzovsky [this message]
2021-06-03 21:11 ` Daniel Vetter
2021-06-03 21:20 ` Alex Deucher
2021-06-03 21:20 ` Alex Deucher
2021-06-03 22:02 ` [PATCH 0/7] libdrm tests for hot-unplug fe goature Grodzovsky, Andrey
2021-06-04 2:26 ` Alex Deucher
2021-06-07 14:29 ` Andrey Grodzovsky
2021-06-04 1:37 ` [PATCH 0/7] libdrm tests for hot-unplug feature Dave Airlie
2021-06-04 2:53 ` Alex Deucher
2021-06-04 3:31 ` Andrey Grodzovsky
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=baf1d1f8-48c7-ed83-8e42-a4a317bfa74d@amd.com \
--to=andrey.grodzovsky@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).