From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: James Zhu <James.Zhu@amd.com>
Cc: dri-devel@lists.freedesktop.org, Alexander.Deucher@amd.com,
christian.koenig@amd.com, daniel.vetter@ffwll.ch,
epilmore@gigaio.com, jamesz@amd.com
Subject: Re: [PATCH v2] drm: register more drm device nodes
Date: Mon, 2 Sep 2024 12:40:47 +0200 [thread overview]
Message-ID: <ZtWWL6q3hL3O2nl3@phenom.ffwll.local> (raw)
In-Reply-To: <20240829213730.308885-1-James.Zhu@amd.com>
On Thu, Aug 29, 2024 at 05:37:30PM -0400, James Zhu wrote:
> Since the default number 256 can't handle large modern systems
> with large numbers of GPUs, specify a more reasonable default.
>
> -v2: update drm_core_exit to unregister more drm device nodes
>
> Signed-off-by: James Zhu <James.Zhu@amd.com>
We've merged a more complete solution meanwhile, I think this should also
cover your case:
https://lore.kernel.org/dri-devel/b313a6f7-a857-4ec9-bc98-0480cd64bc20@amd.com/
Cheers, Sima
> ---
> drivers/gpu/drm/drm_drv.c | 4 ++--
> include/drm/drm_drv.h | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> index 243cacb3575c..bfc6c18a7a92 100644
> --- a/drivers/gpu/drm/drm_drv.c
> +++ b/drivers/gpu/drm/drm_drv.c
> @@ -1063,7 +1063,7 @@ static void drm_core_exit(void)
> {
> drm_privacy_screen_lookup_exit();
> accel_core_exit();
> - unregister_chrdev(DRM_MAJOR, "drm");
> + __unregister_chrdev(DRM_MAJOR, 0, DRM_CHRDEV_MAX, "drm");
> debugfs_remove(drm_debugfs_root);
> drm_sysfs_destroy();
> idr_destroy(&drm_minors_idr);
> @@ -1086,7 +1086,7 @@ static int __init drm_core_init(void)
>
> drm_debugfs_root = debugfs_create_dir("dri", NULL);
>
> - ret = register_chrdev(DRM_MAJOR, "drm", &drm_stub_fops);
> + ret = __register_chrdev(DRM_MAJOR, 0, DRM_CHRDEV_MAX, "drm", &drm_stub_fops);
> if (ret < 0)
> goto error;
>
> diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
> index 8878260d7529..8a2da92f02b7 100644
> --- a/include/drm/drm_drv.h
> +++ b/include/drm/drm_drv.h
> @@ -45,6 +45,8 @@ struct drm_mode_create_dumb;
> struct drm_printer;
> struct sg_table;
>
> +#define DRM_CHRDEV_MAX 1024
> +
> /**
> * enum drm_driver_feature - feature flags
> *
> --
> 2.34.1
>
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
prev parent reply other threads:[~2024-09-02 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 15:34 [PATCH] drm: register more drm device nodes James Zhu
2024-08-29 19:51 ` James Zhu
2024-08-29 19:56 ` James Zhu
2024-08-29 21:37 ` [PATCH v2] " James Zhu
2024-09-02 10:40 ` Daniel Vetter [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=ZtWWL6q3hL3O2nl3@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=Alexander.Deucher@amd.com \
--cc=James.Zhu@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=epilmore@gigaio.com \
--cc=jamesz@amd.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