From: Matthew Auld <matthew.auld@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
airlied@gmail.com, simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org,
linux-mediatek@lists.infradead.org,
freedreno@lists.freedesktop.org, linux-arm-msm@vger.kernel.org,
imx@lists.linux.dev, linux-samsung-soc@vger.kernel.org,
nouveau@lists.freedesktop.org, virtualization@lists.linux.dev,
spice-devel@lists.freedesktop.org,
linux-renesas-soc@vger.kernel.org,
linux-rockchip@lists.infradead.org, linux-tegra@vger.kernel.org,
intel-xe@lists.freedesktop.org, xen-devel@lists.xenproject.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v3 23/25] drm/xe: Compute dumb-buffer sizes with drm_mode_size_dumb()
Date: Thu, 20 Feb 2025 10:08:33 +0000 [thread overview]
Message-ID: <92c1b182-5a0b-4d13-9b16-172ac970b62e@intel.com> (raw)
In-Reply-To: <20250218142542.438557-24-tzimmermann@suse.de>
On 18/02/2025 14:23, Thomas Zimmermann wrote:
> Call drm_mode_size_dumb() to compute dumb-buffer scanline pitch
> and buffer size. Align the pitch to a multiple of 8. Align the
> buffer size according to hardware requirements.
>
> Xe's internal calculation allowed for 64-bit wide buffer sizes, but
> the ioctl's internal checks always verified against 32-bit wide limits.
> Hance, it is safe to limit the driver code to 32-bit calculations as
> well.
>
> v3:
> - mention 32-bit calculation in commit description (Matthew)
>
> Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
> ---
> drivers/gpu/drm/xe/xe_bo.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index 78d09c5ed26d..b34f446ad57d 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -9,6 +9,7 @@
> #include <linux/nospec.h>
>
> #include <drm/drm_drv.h>
> +#include <drm/drm_dumb_buffers.h>
> #include <drm/drm_gem_ttm_helper.h>
> #include <drm/drm_managed.h>
> #include <drm/ttm/ttm_device.h>
> @@ -2672,14 +2673,13 @@ int xe_bo_dumb_create(struct drm_file *file_priv,
> struct xe_device *xe = to_xe_device(dev);
> struct xe_bo *bo;
> uint32_t handle;
> - int cpp = DIV_ROUND_UP(args->bpp, 8);
> int err;
> u32 page_size = max_t(u32, PAGE_SIZE,
> xe->info.vram_flags & XE_VRAM_FLAGS_NEED64K ? SZ_64K : SZ_4K);
>
> - args->pitch = ALIGN(args->width * cpp, 64);
> - args->size = ALIGN(mul_u32_u32(args->pitch, args->height),
> - page_size);
> + err = drm_mode_size_dumb(dev, args, SZ_64, page_size);
> + if (err)
> + return err;
>
> bo = xe_bo_create_user(xe, NULL, NULL, args->size,
> DRM_XE_GEM_CPU_CACHING_WC,
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-20 10:08 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-18 14:23 [PATCH v3 00/25] drm/dumb-buffers: Fix and improve buffer-size calculation Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 01/25] drm/dumb-buffers: Sanitize output on errors Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 02/25] drm/dumb-buffers: Provide helper to set pitch and size Thomas Zimmermann
2025-02-18 19:32 ` Geert Uytterhoeven
2025-02-19 8:08 ` Thomas Zimmermann
2025-02-20 9:18 ` Tomi Valkeinen
2025-02-20 10:05 ` Thomas Zimmermann
2025-02-20 10:53 ` Tomi Valkeinen
2025-02-21 9:19 ` Thomas Zimmermann
2025-02-21 9:57 ` Geert Uytterhoeven
2025-02-21 10:08 ` Thomas Zimmermann
2025-02-25 13:45 ` Tomi Valkeinen
2025-02-26 10:16 ` Thomas Zimmermann
2025-03-07 8:42 ` Simona Vetter
2025-03-07 13:19 ` Simona Vetter
2025-02-18 14:23 ` [PATCH v3 03/25] drm/gem-dma: Compute dumb-buffer sizes with drm_mode_size_dumb() Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 04/25] drm/gem-shmem: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 05/25] drm/gem-vram: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 06/25] drm/armada: " Thomas Zimmermann
2025-02-18 15:57 ` Russell King (Oracle)
2025-02-19 8:09 ` Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 07/25] drm/exynos: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 08/25] drm/gma500: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 09/25] drm/hibmc: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 10/25] drm/imx/ipuv3: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 11/25] drm/loongson: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 12/25] drm/mediatek: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 13/25] drm/msm: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 14/25] drm/nouveau: " Thomas Zimmermann
2025-02-20 22:17 ` Lyude Paul
2025-02-18 14:23 ` [PATCH v3 15/25] drm/omapdrm: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 16/25] drm/qxl: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 17/25] drm/renesas/rcar-du: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 18/25] drm/renesas/rz-du: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 19/25] drm/rockchip: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 20/25] drm/tegra: " Thomas Zimmermann
2025-03-06 19:26 ` Thierry Reding
2025-02-18 14:23 ` [PATCH v3 21/25] drm/virtio: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 22/25] drm/vmwgfx: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 23/25] drm/xe: " Thomas Zimmermann
2025-02-20 10:08 ` Matthew Auld [this message]
2025-02-18 14:23 ` [PATCH v3 24/25] drm/xen: " Thomas Zimmermann
2025-02-18 14:23 ` [PATCH v3 25/25] drm/xlnx: " Thomas Zimmermann
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=92c1b182-5a0b-4d13-9b16-172ac970b62e@intel.com \
--to=matthew.auld@intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=imx@lists.linux.dev \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=spice-devel@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=xen-devel@lists.xenproject.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