From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Laguna, Lukasz" <lukasz.laguna@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs
Date: Fri, 10 Nov 2023 20:44:15 +0100 [thread overview]
Message-ID: <e8d16680-0b19-44d1-9cbc-3cbd7b295c03@intel.com> (raw)
In-Reply-To: <cfd5dfb7-25bd-b6d1-069b-cf53c9c021d9@intel.com>
On 09.11.2023 08:06, Laguna, Lukasz wrote:
>
> On 11/6/2023 23:59, Michal Wajdeczko wrote:
>>
>> On 06.11.2023 20:59, Lukasz Laguna wrote:
>>> From: Katarzyna Dec <katarzyna.dec@intel.com>
>>>
>>> Test enables VFs in range <1..totalvfs>, bind driver to all of them and
>>> then unbind driver from all of them.
>> commit message seems outdated
> What do you mean? I don't see anything wrong
>>
>>> Signed-off-by: Katarzyna Dec <katarzyna.dec@intel.com>
>>> Reviewed-by: Lukasz Laguna <lukasz.laguna@intel.com>
>>> Signed-off-by: Lukasz Laguna <lukasz.laguna@intel.com>
>>> Reviewed-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
>>> ---
>>> tests/sriov_basic.c | 51 +++++++++++++++++++++++++++++++++++++++++++++
>>> 1 file changed, 51 insertions(+)
>>>
>>> diff --git a/tests/sriov_basic.c b/tests/sriov_basic.c
>>> index fc0914962..179731daf 100644
>>> --- a/tests/sriov_basic.c
>>> +++ b/tests/sriov_basic.c
>>> @@ -61,6 +61,38 @@ static void probe_disable_vfs(int pf_fd, unsigned
>>> int num_vfs)
>>> igt_assert(!err);
>>> }
>>> +/**
>>> + * SUBTEST: enable-vfs-bind-all-unbind-all
>>> + * Description:
>>> + * Verify VFs enabling, binding the driver and then unbinding it
>>> from all of them
>>> + */
>>> +static void enable_vfs_bind_all_unbind_all(int pf_fd, unsigned int
>>> num_vfs)
>>> +{
>>> + igt_debug("Using num_vfs=%u\n", num_vfs);
>> nit: "Testing %u VFs" ?
> Done
>>
>>> +
>>> + igt_require(igt_sriov_get_enabled_vfs(pf_fd) == 0);
>> duplicates main fixture
> As already answered in different patch - first fixtureis not executed
> between dynamic subtests.
>>
>>> + igt_warn_on(!igt_sriov_disable_driver_autoprobe(pf_fd));
>>> + igt_skip_on(igt_sriov_is_driver_autoprobe_enabled(pf_fd));
>> why do we need warn/skip here ?
>> can't we just assert that 'disable' worked ?
> Done
>>
>>> +
>>> + igt_warn_on(!igt_sriov_enable_vfs(pf_fd, num_vfs));
>> can't we just assert ?
> Done
>>
>>> + igt_assert_eq(num_vfs, igt_sriov_get_enabled_vfs(pf_fd));
>> why we care here ? if not all are enabled then we fail just later
>> and this is not a test for "enable VFs" that enabled==requested
> Done
>>
>>> + igt_warn_on(!igt_sriov_enable_driver_autoprobe(pf_fd));
>>> + igt_assert(igt_sriov_is_driver_autoprobe_enabled(pf_fd));
>> can't we just warn ?
>> if that we fail to enable then probe below will fail anyway
> Done
>>
>>> +
>>> + for (int i = 1; i <= num_vfs; i++) {
>>> + igt_assert(!igt_sriov_is_vf_drm_driver_probed(pf_fd, i));
>>> + igt_assert(igt_sriov_bind_vf_drm_driver(pf_fd, i));
>>> + igt_assert(igt_sriov_is_vf_drm_driver_probed(pf_fd, i));
>> shouldn't we just "expect" to make sure to call "disable VFs" ?
> VFs will be disabled in exit fixture. VFs disabling in subtest is needed
> between dynamic subtests.
but if test passed, then it should do a proper cleanup
maybe problem is that if something went wrong, your igt_assert() aborts
current test which doesn't have a chance to do proper cleanup ?
or maybe that cleanup should be in some mid-test fixture ?
anyway, just seems broken that we need to duplicate the code/logic every
time
>>
>>> + }
>>> +
>>> + for (int i = 1; i <= num_vfs; i++) {
>>> + igt_assert(igt_sriov_unbind_vf_drm_driver(pf_fd, i));
>>> + igt_assert(!igt_sriov_is_vf_drm_driver_probed(pf_fd, i));
>> do we need to have all VFs loaded ?
>> maybe for BAT test we can just bind/unload one VF at the time ?
> We have such test as well:
> [PATCH i-g-t 8/8] tests/sriov_basic: add more tests for VF driver binding
> SUBTEST: enable-vfs-bind-unbind-each
> SUBTEST: bind-unbind-vf
that's good
but the question is still open?
what the benefit of having this test which just open-coded the VF probe
loop that would be otherwise done by the PCI subsystem ?
and again, like autoprobe-on, this doesn't seem good candidate for "BAT"
runs, more like a "STRESS"
>>
>> otherwise it will be almost the same level of stress as in
>> "enable-vfs-autoprobe-on" but with 'manual probe' loop of all VFs
>>
>>> + }
>>> +
>>> + igt_assert(igt_sriov_disable_vfs(pf_fd));
>>> +}
>>> +
>>> igt_main
>>> {
>>> int pf_fd;
>>> @@ -113,6 +145,25 @@ igt_main
>>> }
>>> }
>>> + igt_describe("Verify VFs enabling, binding the driver and then
>>> unbinding it from all of them");
>>> + igt_subtest_with_dynamic("enable-vfs-bind-all-unbind-all") {
>>> + for_each_num_vfs(pf_fd, num_vfs) {
>>> + igt_dynamic_f("numvfs-%u", num_vfs) {
>>> + enable_vfs_bind_all_unbind_all(pf_fd, num_vfs);
>>> + }
>>> + }
>>> + for_random_num_vfs(pf_fd, num_vfs) {
>>> + igt_dynamic_f("numvfs-random") {
>>> + enable_vfs_bind_all_unbind_all(pf_fd, num_vfs);
>>> + }
>>> + }
>>> + for_max_num_vfs(pf_fd, num_vfs) {
>>> + igt_dynamic_f("numvfs-all") {
>>> + enable_vfs_bind_all_unbind_all(pf_fd, num_vfs);
>>> + }
>>> + }
>>> + }
>>> +
>>> igt_fixture {
>>> igt_sriov_disable_vfs(pf_fd);
>>> /* abort to avoid execution of next tests with enabled VFs */
next prev parent reply other threads:[~2023-11-10 19:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 19:59 [igt-dev] [PATCH i-g-t 0/8] Initial SR-IOV validation Lukasz Laguna
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 1/8] lib/igt_sriov_device: add core SR-IOV helpers Lukasz Laguna
2023-11-06 22:07 ` Michal Wajdeczko
2023-11-09 6:55 ` Laguna, Lukasz
2023-11-10 19:22 ` Michal Wajdeczko
2023-11-17 14:34 ` Laguna, Lukasz
2023-11-20 14:26 ` Laguna, Lukasz
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 2/8] lib/igt_sriov_device: add helper for opening VF device Lukasz Laguna
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 3/8] lib/igt_sriov_device: add helper for checking if VF DRM driver is probed Lukasz Laguna
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 4/8] lib/igt_sriov_device: add helpers for operations in different VFs scenarios Lukasz Laguna
2023-11-06 22:13 ` Michal Wajdeczko
2023-11-09 6:58 ` Laguna, Lukasz
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 5/8] tests/sriov_basic: add basic tests for enabling SR-IOV VFs Lukasz Laguna
2023-11-06 22:46 ` Michal Wajdeczko
2023-11-09 7:04 ` Laguna, Lukasz
2023-11-10 19:37 ` Michal Wajdeczko
2023-11-20 14:29 ` Laguna, Lukasz
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 6/8] lib/igt_sriov_device: add helpers for VF DRM driver bind and unbind Lukasz Laguna
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs Lukasz Laguna
2023-11-06 22:59 ` Michal Wajdeczko
2023-11-09 7:06 ` Laguna, Lukasz
2023-11-10 19:44 ` Michal Wajdeczko [this message]
2023-11-20 14:31 ` Laguna, Lukasz
2023-11-06 19:59 ` [igt-dev] [PATCH i-g-t 8/8] tests/sriov_basic: add more tests for VF driver binding Lukasz Laguna
2023-11-06 20:55 ` [igt-dev] ✓ CI.xeBAT: success for Initial SR-IOV validation Patchwork
2023-11-06 21:00 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-11-07 6:03 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 6:51 [igt-dev] [PATCH i-g-t 0/8] " Lukasz Laguna
2023-11-09 6:51 ` [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs Lukasz Laguna
2023-11-20 14:14 [igt-dev] [PATCH i-g-t 0/8] Initial SR-IOV validation Lukasz Laguna
2023-11-20 14:14 ` [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs Lukasz Laguna
2023-11-24 8:52 [igt-dev] [PATCH i-g-t 0/8] Initial SR-IOV validation Lukasz Laguna
2023-11-24 8:52 ` [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs Lukasz Laguna
2023-11-30 12:48 [igt-dev] [PATCH i-g-t 0/8] Initial SR-IOV validation Lukasz Laguna
2023-11-30 12:48 ` [igt-dev] [PATCH i-g-t 7/8] tests/sriov_basic: validate driver binding to VFs Lukasz Laguna
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=e8d16680-0b19-44d1-9cbc-3cbd7b295c03@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lukasz.laguna@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