From: Zack Rusin <zackr@vmware.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"kamil.konieczny@linux.intel.com"
<kamil.konieczny@linux.intel.com>
Cc: Martin Krastev <krastevm@vmware.com>,
Michael Banack <banackm@vmware.com>,
Maaz Mombasawala <mombasawalam@vmware.com>
Subject: Re: [igt-dev] [PATCH i-g-t 3/3] igt: Switch warning to an info when not using i915
Date: Thu, 26 Jan 2023 19:11:18 +0000 [thread overview]
Message-ID: <3ea9b093fc7ff70788c035a74f065c1b6075c478.camel@vmware.com> (raw)
In-Reply-To: <20230126181733.5lgq2rq43gqy5qd2@kamilkon-desk1>
On Thu, 2023-01-26 at 19:17 +0100, Kamil Konieczny wrote:
> !! External Email
>
> Hi Zack,
>
> On 2022-11-29 at 12:27:18 -0500, Zack Rusin wrote:
> > From: Zack Rusin <zackr@vmware.com>
> >
> > Because igt always tries to load i915 driver first for DRIVER_ANY every
> > test using DRIVER_ANY on anything but i915 starts by printing a warning
> > that i915 couldn't be loaded.
> > Lets switch it to a general info line because it makes it hard to spot
> > actual warnings when every subtest starts by warning about not being
> > able to load i915.
> >
> > Signed-off-by: Zack Rusin <zackr@vmware.com>
> > ---
> > lib/igt_kmod.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/igt_kmod.c b/lib/igt_kmod.c
> > index bcf7dfeb..74924b5f 100644
> > --- a/lib/igt_kmod.c
> > +++ b/lib/igt_kmod.c
> > @@ -389,7 +389,7 @@ igt_i915_driver_load(const char *opts)
>
> This is i915 driver load so maybe we should find a way to not
> call this function ?
That'd be fine, how would you do that? IGT has a number of tests (the core ones)
that use DRIVER_ANY for load the first available driver. Unless we explicitly
exclude i915 from running those tests, or reorder the enum to try i915 after all the
other options then it's not a trivial fix. We'd need to do add proper pci device id
matching to always use the correct driver, which would be great, but is probably a
little out of scope for this change.
z
next prev parent reply other threads:[~2023-01-26 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 17:27 [igt-dev] [PATCH i-g-t 0/3] Add vmwgfx support Zack Rusin
2022-11-29 17:27 ` [igt-dev] [PATCH i-g-t 1/3] igt/vmwgfx: Add support for testing vmwgfx Zack Rusin
2023-01-26 18:13 ` Kamil Konieczny
2023-01-26 19:06 ` Zack Rusin
2023-02-17 17:50 ` Kamil Konieczny
2022-11-29 17:27 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_kms: vmwgfx returns 8 crtc Zack Rusin
2023-02-17 17:32 ` Kamil Konieczny
2022-11-29 17:27 ` [igt-dev] [PATCH i-g-t 3/3] igt: Switch warning to an info when not using i915 Zack Rusin
2023-01-26 18:17 ` Kamil Konieczny
2023-01-26 19:11 ` Zack Rusin [this message]
2023-01-27 14:29 ` Kamil Konieczny
2023-01-27 14:35 ` Petri Latvala
2023-01-27 16:51 ` Kamil Konieczny
2023-02-17 17:35 ` Kamil Konieczny
2022-11-29 19:42 ` [igt-dev] ✗ GitLab.Pipeline: warning for Add vmwgfx support Patchwork
2022-11-29 20:02 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
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=3ea9b093fc7ff70788c035a74f065c1b6075c478.camel@vmware.com \
--to=zackr@vmware.com \
--cc=banackm@vmware.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.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