From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>
Cc: "Kolakowski, Jakub1" <jakub1.kolakowski@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"Chegondi, Harish" <harish.chegondi@intel.com>,
Adam Miszczak <adam.miszczak@linux.intel.com>,
"Laguna, Lukasz" <lukasz.laguna@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/xe_eu_stall: Skip test on SR-IOV VF
Date: Fri, 23 May 2025 09:06:17 -0700 [thread overview]
Message-ID: <87o6vjjoqu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <9696a2b7-e85a-4fc1-b400-c16f4df1c31a@linux.intel.com>
On Fri, 23 May 2025 06:56:52 -0700, Bernatowicz, Marcin wrote:
>
>
>
> On 5/23/2025 3:11 PM, Bernatowicz, Marcin wrote:
> > Hi Jakub,
> >
> > On 5/23/2025 2:23 PM, Kolakowski, Jakub1 wrote:
> >> Hi Marcin,
> >> I was trying to align the code of the IGT test with kernel code, where
> >> we have an explicit check for SR-IOV VF.
> >> See https://gitlab.freedesktop.org/drm/tip/-/
> >> commit/1d622a4fe2b9a30cd4af2e858d793d05f8a82774
> >>
> And with this approach, the kernel check itself isn't really being tested ;)
> --
> marcin>> Jakub
Marcin is correct. This patch is wrong, IGT should check for -ENODEV
returned from kernel.
Both opening a stream as well as the EU stall query will return -ENODEV on
SRIOV VF.
@Chegondi, Harish: weren't you adding something for EU stall query if it's
not there?
> >
> > Still, I wonder if relying on VF checks is the best long-term approach -
> > we might enable the feature on a VF at some point, and the test would
> > keep skipping.
> > What about other apps using this feature - how should they detect
> > availability?
> > If they just try to use it on a VF, do they get ENODEV or something else?
> > Wouldn’t it be more robust to base this on a real feature check from
> > userspace if possible?
> > --
> > marcin
next prev parent reply other threads:[~2025-05-23 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 17:24 [PATCH i-g-t] tests/intel/xe_eu_stall: Skip test on SR-IOV VF Jakub Kolakowski
2025-05-22 19:17 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-05-22 19:30 ` ✓ Xe.CI.BAT: success " Patchwork
2025-05-23 6:51 ` [PATCH i-g-t] " Harish Chegondi
2025-05-23 10:40 ` Bernatowicz, Marcin
2025-05-23 12:23 ` Kolakowski, Jakub1
2025-05-23 13:11 ` Bernatowicz, Marcin
2025-05-23 13:56 ` Bernatowicz, Marcin
2025-05-23 16:06 ` Dixit, Ashutosh [this message]
2025-05-23 10:47 ` Kamil Konieczny
2025-05-23 12:20 ` ✗ Xe.CI.Full: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-05-23 12:44 [PATCH i-g-t] " Jakub Kolakowski
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=87o6vjjoqu.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=adam.miszczak@linux.intel.com \
--cc=harish.chegondi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jakub1.kolakowski@intel.com \
--cc=lukasz.laguna@intel.com \
--cc=marcin.bernatowicz@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.