NVIDIA GPU driver infrastructure
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Danilo Krummrich" <dakr@kernel.org>,
	aliceryhl@google.com, airlied@gmail.com, simona@ffwll.ch,
	ojeda@kernel.org, boqun@kernel.org, gary@garyguo.net,
	bjorn3_gh@protonmail.com, lossin@kernel.org,
	a.hindborg@kernel.org, tmgross@umich.edu,
	daniel.almeida@collabora.com, tamird@kernel.org,
	acourbot@nvidia.com, work@onurozkan.dev, jhubbard@nvidia.com,
	apopple@nvidia.com, ecourtney@nvidia.com, lyude@redhat.com,
	kherbst@redhat.com
Cc: nova-gpu@lists.linux.dev, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/nova: require explicit opt-in to unstable uAPI
Date: Mon, 19 Oct 2026 21:32:33 +0000	[thread overview]
Message-ID: <sashiko-outbox-178261@kernel.org> (raw)
In-Reply-To: <20261019212535.88390-4-dakr@kernel.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/nova: missing kernel-parameters.txt entry for acknowledge_unstable_uapi
--

commit 77a1b4c686914a70a5ae235e8e03b1e3542d6c45
Author: Danilo Krummrich <dakr@kernel.org>

drm/nova: require explicit opt-in to unstable uAPI

This commit adds the acknowledge_unstable_uapi module parameter to
nova-drm to require users to explicitly opt in to the unstable uAPI before
enabling the driver, and taints the kernel when enabled.

> diff --git a/drivers/gpu/drm/nova/Kconfig b/drivers/gpu/drm/nova/Kconfig
> index ba16c74401f8f..2cb62517b2f9b 100644
> --- a/drivers/gpu/drm/nova/Kconfig
> +++ b/drivers/gpu/drm/nova/Kconfig
> @@ -12,6 +12,15 @@ config DRM_NOVA
>  	  Choose this if you want to build the Nova DRM driver for Nvidia
>  	  GSP-based GPUs.
>  
> -	  This driver is work in progress and may not be functional.
> +	  This driver is under active upstream development and may not be
> +	  functional. Its uAPI is intended to be developed upstream alongside
> +	  the driver and is not yet stable. It may change incompatibly during
> +	  development.
> +
> +	  Loading requires the acknowledge_unstable_uapi=1 module parameter, or
> +	  nova-drm.acknowledge_unstable_uapi=1 on the kernel command line when
> +	  built in.
> +
> +	  Enabling the driver taints the kernel.
>  
>  	  If M is selected, the module will be called nova-drm.
> diff --git a/drivers/gpu/drm/nova/nova.rs b/drivers/gpu/drm/nova/nova.rs
> index 1fd454c7e0dfb..ad68f6e1a613b 100644
> --- a/drivers/gpu/drm/nova/nova.rs
> +++ b/drivers/gpu/drm/nova/nova.rs

[ ... ]

> -kernel::module_auxiliary_driver! {
> -    type: NovaDriver,
> +module! {
> +    type: NovaModule,
>      name: "nova-drm",
>      authors: ["Danilo Krummrich"],
>      description: "Nova GPU driver",
>      license: "GPL v2",
> +    params: {
> +        acknowledge_unstable_uapi: bool {
> +            default: false,
> +            description: "Acknowledge that Nova and its uAPI are under active upstream development \
> +                          and the uAPI may change incompatibly; enable the driver (taints kernel)",
> +        },
> +    },
> +}
> +
> +#[pin_data]
> +struct NovaModule {
> +    #[pin]
> +    _driver: Registration<auxiliary::Adapter<NovaDriver>>,
> +}
> +
> +impl NovaModule {
> +    fn check_unstable_uapi() -> Result {
> +        pr_warn!("Nova and its uAPI are under active upstream development\n");
> +
> +        if !module_parameters::acknowledge_unstable_uapi.value() {
> +            pr_err!("Driver disabled: Nova's uAPI is unstable and may change incompatibly\n");
> +            pr_info!("Set nova-drm.acknowledge_unstable_uapi=1 to enable (taints kernel)\n");

[Severity: Low]
Since NovaModule defines the acknowledge_unstable_uapi parameter in
drivers/gpu/drm/nova/nova.rs and both DRM_NOVA in
drivers/gpu/drm/nova/Kconfig and NovaModule::check_unstable_uapi()
instruct users to pass nova-drm.acknowledge_unstable_uapi=1 on the kernel
command line when built in, should this parameter also be documented in
Documentation/admin-guide/kernel-parameters.txt?

> +            return Err(EPERM);
> +        }

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261019212535.88390-1-dakr@kernel.org?part=3

      reply	other threads:[~2026-10-19 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 21:24 [PATCH 0/3] drm/nova: make unstable uAPI use explicit Danilo Krummrich
2026-10-19 21:24 ` [PATCH 1/3] drm/nova: mark the uAPI header as unstable Danilo Krummrich
2026-10-19 22:08   ` Faith Ekstrand
2026-10-20 14:36   ` M Henning
2026-10-19 21:24 ` [PATCH 2/3] rust: add kernel taint abstraction Danilo Krummrich
2026-10-19 21:24 ` [PATCH 3/3] drm/nova: require explicit opt-in to unstable uAPI Danilo Krummrich
2026-10-19 21:32   ` sashiko-bot [this message]

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=sashiko-outbox-178261@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=apopple@nvidia.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ecourtney@nvidia.com \
    --cc=gary@garyguo.net \
    --cc=jhubbard@nvidia.com \
    --cc=kherbst@redhat.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=nova-gpu@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=simona@ffwll.ch \
    --cc=tamird@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=work@onurozkan.dev \
    /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