From: Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
Subject: Re: [Devel] [PATCH vz10] drm/virtio: decline the device with -ENODEV when modesetting is off
Date: Mon, 24 Aug 2026 08:49:06 +0000 [thread overview]
Message-ID: <178756134677.187542.6965762582572098978.b4-review@b4> (raw)
In-Reply-To: <20260821153821.799764-1-eva.kurchatova@virtuozzo.com>
> Our kernels disable modesetting by default, see 7932a11226c8 ("drm:
checkpatch.pl complains about description style here.
Please use git commit description style 'commit <12+ chars of sha1>
> Disable modeset by default"), so on a machine that was not booted with
> "modeset" every KMS driver declines the device it was offered. Of 23
> existing upstream drm drivers, 21 report -ENODEV in such case, which
> really_probe() reports as "rejects match" at debug level. virtio_gpu
> returns -EINVAL instead, which the same function reports as
>
> virtio_gpu virtio0: probe with driver virtio_gpu failed with error -22
>
> at error level, for a device the driver was never going to drive. It is
> the only device error in the log of an otherwise healthy machine, and
> the devices/error_logs selftest reports it, correctly.
>
> Return -ENODEV, as the other drivers do. Nothing else changes: the probe
> still does not happen and no drm device appears.
>
> https://virtuozzo.atlassian.net/browse/VSTOR-139680
> Feature: fix vz kernel
Please add Fixes tag.
--
Vasileios Almpanis <vasileios.almpanis@virtuozzo.com>
next prev parent reply other threads:[~2026-08-24 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 15:38 Eva Kurchatova
2026-08-24 8:49 ` Vasileios Almpanis [this message]
2026-08-24 17:03 ` [Devel] [PATCH vz10 v2] drm: " Konstantin Khorenko
2026-08-24 17:04 ` [Devel] [PATCH RHEL10 COMMIT] " Konstantin Khorenko
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=178756134677.187542.6965762582572098978.b4-review@b4 \
--to=vasileios.almpanis@virtuozzo.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