Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Jakub Kolakowski <jakub1.kolakowski@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: Adam Miszczak <adam.miszczak@intel.com>,
	Marcin Bernatowicz <marcin.bernatowicz@intel.com>,
	Lukasz Laguna <lukasz.laguna@intel.com>,
	Kamil Konieczny <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH i-g-t] tests/intel-ci/fast-feedback: Add SR-IOV tests
Date: Thu, 4 Jul 2024 16:20:35 +0200	[thread overview]
Message-ID: <047f72ab-e531-4d0d-8c6c-31d11c3b7ba6@intel.com> (raw)
In-Reply-To: <20240703111221.616274-1-jakub1.kolakowski@intel.com>



On 03.07.2024 13:12, Jakub Kolakowski wrote:
> This commit adds SR-IOV tests to fast-feedback testlist so that

nit: not sure about IGT rules, but usually we don't start commit message
with "This commit", from [1]

"Describe your changes in imperative mood, e.g. “make xyzzy do frotz”
instead of “[This patch] makes xyzzy do frotz” or “[I] changed xyzzy to
do frotz”, as if you are giving orders to the codebase to change its
behaviour."


[1] https://docs.kernel.org/process/submitting-patches.html

> they will be executed in BAT runs. Added tests are about basic
> single VF enablement with and without autoprobe.
> 
> Signed-off-by: Jakub Kolakowski <jakub1.kolakowski@intel.com>
> Cc: Adam Miszczak <adam.miszczak@intel.com>
> Cc: Marcin Bernatowicz <marcin.bernatowicz@intel.com>
> Cc: Lukasz Laguna <lukasz.laguna@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
>  tests/intel-ci/xe-fast-feedback.testlist | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/tests/intel-ci/xe-fast-feedback.testlist b/tests/intel-ci/xe-fast-feedback.testlist
> index aa98b37e6..fc312a123 100644
> --- a/tests/intel-ci/xe-fast-feedback.testlist
> +++ b/tests/intel-ci/xe-fast-feedback.testlist
> @@ -65,6 +65,8 @@ igt@kms_prop_blob@basic
>  igt@kms_psr@psr-primary-page-flip
>  igt@kms_psr@psr-cursor-plane-move
>  igt@kms_psr@psr-sprite-plane-onoff
> +igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-1

maybe instead of numvfs-1 we should select numvfs-all variant:

	igt@sriov_basic@enable-vfs-autoprobe-off@numvfs-all

as otherwise this case will be fully duplicated by the test below (where
auto-provisioning of one VF will be exactly the same, just a VF driver
will be probed on that config), while with numvfs-all variant we will
check auto-provisioning for all available VFs

> +igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1
>  igt@xe_compute@compute-square
>  igt@xe_create@create-execqueues-noleak
>  igt@xe_create@create-execqueues-leak

  parent reply	other threads:[~2024-07-04 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 11:12 [PATCH i-g-t] tests/intel-ci/fast-feedback: Add SR-IOV tests Jakub Kolakowski
2024-07-03 16:08 ` Kamil Konieczny
2024-07-04 14:20 ` Michal Wajdeczko [this message]
2024-07-05 18:24   ` Kolakowski, Jakub1

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=047f72ab-e531-4d0d-8c6c-31d11c3b7ba6@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=adam.miszczak@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=marcin.bernatowicz@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