From: Thomas Zimmermann <tzimmermann@suse.de>
To: oushixiong1025@163.com, "Christian König" <christian.koenig@amd.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Sean Paul <sean@poorly.run>,
Jocelyn Falempe <jfalempe@redhat.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Shixiong Ou <oushixiong@kylinos.cn>
Subject: Re: [PATCH v5 RESEND 3/3] drm/udl: use DRM_GEM_SHMEM_DRIVER_OPS_NO_MAP_SGT
Date: Mon, 26 May 2025 15:57:31 +0200 [thread overview]
Message-ID: <ee9ca879-4bb7-4339-b827-78eb2d46a97f@suse.de> (raw)
In-Reply-To: <20250522070714.439824-3-oushixiong1025@163.com>
Am 22.05.25 um 09:07 schrieb oushixiong1025@163.com:
> From: Shixiong Ou <oushixiong@kylinos.cn>
>
> Import dmabuf without mapping its sg_table to avoid issues likes:
> udl 2-1.4:1.0: swiotlb buffer is full (sz: 2097152 bytes), total 65536 (slots), used 1 (slots)
>
> Signed-off-by: Shixiong Ou <oushixiong@kylinos.cn>
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> ---
> drivers/gpu/drm/udl/udl_drv.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/udl/udl_drv.c b/drivers/gpu/drm/udl/udl_drv.c
> index 1922988625eb..ce5ae7cacb90 100644
> --- a/drivers/gpu/drm/udl/udl_drv.c
> +++ b/drivers/gpu/drm/udl/udl_drv.c
> @@ -57,7 +57,7 @@ static const struct drm_driver driver = {
>
> /* GEM hooks */
> .fops = &udl_driver_fops,
> - DRM_GEM_SHMEM_DRIVER_OPS,
> + DRM_GEM_SHMEM_DRIVER_OPS_NO_MAP_SGT,
> DRM_FBDEV_SHMEM_DRIVER_OPS,
>
> .name = DRIVER_NAME,
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2025-05-26 13:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 7:07 [PATCH v5 RESEND 1/3] drm/shmem-helper: Import dmabuf without mapping its sg_table oushixiong1025
2025-05-22 7:07 ` [PATCH v5 RESEND 2/3] drm/ast: use DRM_GEM_SHMEM_DRIVER_OPS_NO_MAP_SGT oushixiong1025
2025-05-26 13:56 ` Thomas Zimmermann
2025-05-22 7:07 ` [PATCH v5 RESEND 3/3] drm/udl: " oushixiong1025
2025-05-26 13:57 ` Thomas Zimmermann [this message]
2025-05-26 15:00 ` [PATCH v5 RESEND 1/3] drm/shmem-helper: Import dmabuf without mapping its sg_table Thomas Zimmermann
2025-06-03 7:49 ` Thomas Zimmermann
2025-07-11 14:16 ` Thomas Zimmermann
[not found] ` <7d974eaa-d8a4-4430-a999-7b06c4e17a81@163.com>
2025-07-14 10:47 ` Thomas Zimmermann
2025-08-13 9:25 ` Thomas Zimmermann
2025-08-13 11:18 ` Christian König
2025-08-13 12:08 ` Thomas Zimmermann
2025-08-13 12:16 ` Thomas Zimmermann
2025-08-13 13:35 ` Christian König
2025-08-13 14:06 ` Thomas Zimmermann
2025-08-14 10:22 ` Christian König
2025-08-14 12:51 ` Thomas Zimmermann
2025-08-14 13:16 ` Christian König
2025-08-15 12:46 ` Thomas Zimmermann
2025-08-15 13:28 ` Christian König
2025-08-15 13:48 ` Thomas Zimmermann
2025-08-18 8:45 ` 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=ee9ca879-4bb7-4339-b827-78eb2d46a97f@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=oushixiong1025@163.com \
--cc=oushixiong@kylinos.cn \
--cc=sean@poorly.run \
--cc=simona@ffwll.ch \
/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
all inboxes | Powered by JetHome®