Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <christian.koenig@amd.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Simon Ser <contact@emersion.fr>,
	Matthew Wilcox <willy@infradead.org>,
	Oded Gabbay <ogabbay@kernel.org>, James Zhu <James.Zhu@amd.com>,
	Pekka Paalanen <pekka.paalanen@collabora.com>,
	Emil Velikov <emil.l.velikov@gmail.com>,
	Alex Deucher <alexdeucher@gmail.com>
Subject: Re: [PATCH v7 0/3] drm: Use full allocated minor range for DRM
Date: Mon, 26 Aug 2024 20:07:43 +0200	[thread overview]
Message-ID: <b313a6f7-a857-4ec9-bc98-0480cd64bc20@amd.com> (raw)
In-Reply-To: <20240823163048.2676257-1-michal.winiarski@intel.com>

Am 23.08.24 um 18:30 schrieb Michał Winiarski:
> 64 DRM device nodes is not enough for everyone.
> Upgrade it to ~512K (which definitely is more than enough).
>
> Additionally, convert minors to use XArray instead of IDR to simplify
> the locking.
>
> Corresponding libdrm changes were merged in:
> https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/305

Added my Acked-by and pushed the result to drm-misc-next.

Regards,
Christian.

>
> v1 -> v2:
> Don't touch DRM_MINOR_CONTROL and its range (Simon Ser)
>
> v2 -> v3:
> Don't use legacy scheme for >=192 minor range (Dave Airlie)
> Add modparam for testing (Dave Airlie)
> Add lockdep annotation for IDR (Daniel Vetter)
>
> v3 -> v4:
> Convert from IDR to XArray (Matthew Wilcox)
>
> v4 -> v5:
> Fixup IDR to XArray conversion (Matthew Wilcox)
>
> v5 -> v6:
> Also convert Accel to XArray
> Rename skip_legacy_minors to force_extended_minors
>
> v6 -> v7:
> Drop the force_extended_minors patch intended for debug
> Rebase on latest drm-tip
> Update the cover letter, pointing out libdrm changes
>
> Michał Winiarski (3):
>    drm: Use XArray instead of IDR for minors
>    accel: Use XArray instead of IDR for minors
>    drm: Expand max DRM device number to full MINORBITS
>
>   drivers/accel/drm_accel.c      | 110 +++------------------------------
>   drivers/gpu/drm/drm_drv.c      |  97 ++++++++++++++---------------
>   drivers/gpu/drm/drm_file.c     |   2 +-
>   drivers/gpu/drm/drm_internal.h |   4 --
>   include/drm/drm_accel.h        |  18 +-----
>   include/drm/drm_file.h         |   5 ++
>   6 files changed, 62 insertions(+), 174 deletions(-)
>


      parent reply	other threads:[~2024-08-26 18:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 16:30 [PATCH v7 0/3] drm: Use full allocated minor range for DRM Michał Winiarski
2024-08-23 16:30 ` [PATCH v7 1/3] drm: Use XArray instead of IDR for minors Michał Winiarski
2024-08-23 16:30 ` [PATCH v7 2/3] accel: " Michał Winiarski
2024-08-23 16:30 ` [PATCH v7 3/3] drm: Expand max DRM device number to full MINORBITS Michał Winiarski
2024-08-23 17:10 ` ✓ CI.Patch_applied: success for drm: Use full allocated minor range for DRM Patchwork
2024-08-23 17:11 ` ✓ CI.checkpatch: " Patchwork
2024-08-23 17:12 ` ✓ CI.KUnit: " Patchwork
2024-08-23 17:31 ` ✓ CI.Build: " Patchwork
2024-08-23 17:34 ` ✓ CI.Hooks: " Patchwork
2024-08-23 17:35 ` ✗ CI.checksparse: warning " Patchwork
2024-08-23 18:07 ` ✓ CI.BAT: success " Patchwork
2024-08-23 23:59 ` ✗ CI.FULL: failure " Patchwork
2024-08-26 18:07 ` Christian König [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=b313a6f7-a857-4ec9-bc98-0480cd64bc20@amd.com \
    --to=christian.koenig@amd.com \
    --cc=James.Zhu@amd.com \
    --cc=airlied@gmail.com \
    --cc=alexdeucher@gmail.com \
    --cc=contact@emersion.fr \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=pekka.paalanen@collabora.com \
    --cc=tzimmermann@suse.de \
    --cc=willy@infradead.org \
    /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