From: Rob Clark <robdclark@gmail.com>
To: "Maíra Canal" <mcanal@igalia.com>
Cc: "Rob Clark" <robdclark@chromium.org>,
"André Almeida" <andrealmeid@igalia.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Melissa Wen" <mwen@igalia.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/gem: Check for valid formats
Date: Tue, 3 Jan 2023 18:22:01 -0800 [thread overview]
Message-ID: <CAF6AEGs+GP2MCbD=wW+ords=MPFBcV4ncag-5KBfO=2KWg3G0Q@mail.gmail.com> (raw)
In-Reply-To: <8d5deb15-e412-180f-585d-f57d193ae658@igalia.com>
On Tue, Jan 3, 2023 at 5:11 PM Maíra Canal <mcanal@igalia.com> wrote:
>
> On 1/3/23 19:46, Rob Clark wrote:
> > drive-by thought/concern, what are the odds that there is some wayland
> > compositor out there that creates an fb for every window surface, even
> > if it later decides to composite on the GPU because the display does
> > not support the format? It seems like there is a non-zero chance of
> > breaking userspace..
> >
>
> As Simon pointed out, drivers like i915 and AMDGPU already reject IOCTLs
> with invalid parameters, as you can see on [1] and [2], so this patch
> would make the behavior more consistent between the drivers. That said,
> I don't believe that this patch would break userspace, as userspace
> already needs to handle with the existing drivers.
ok, maybe this won't be a problem then
BR,
-R
> [1] https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/i915/display/intel_fb.c#n1917
> [2] https://cgit.freedesktop.org/drm/drm-misc/tree/drivers/gpu/drm/amd/amdgpu/amdgpu_display.c#n1124
>
> Best Regards,
> - Maíra Canal
>
> > BR,
> > -R
> >
>
next prev parent reply other threads:[~2023-01-04 2:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 12:53 [PATCH] drm/gem: Check for valid formats Maíra Canal
2023-01-03 13:16 ` Thomas Zimmermann
2023-01-05 15:24 ` Daniel Vetter
2023-01-05 15:43 ` Thomas Zimmermann
2023-01-05 15:51 ` Daniel Vetter
2023-01-03 22:46 ` Rob Clark
2023-01-03 23:27 ` Simon Ser
2023-01-04 1:11 ` Maíra Canal
2023-01-04 2:22 ` Rob Clark [this message]
2023-01-05 15:26 ` Daniel Vetter
2023-01-05 17:48 ` Maíra Canal
2023-01-05 18:22 ` Daniel Vetter
2023-01-05 18:30 ` Maíra Canal
2023-01-05 18:36 ` Simon Ser
2023-01-05 18:48 ` Maíra Canal
2023-01-05 18:54 ` Simon Ser
2023-01-05 19:00 ` Maíra Canal
2023-01-05 20:04 ` Simon Ser
2023-01-06 17:42 ` Daniel Vetter
2023-01-06 7:10 ` Thomas Zimmermann
2023-01-05 15:59 ` Thomas Zimmermann
2023-04-12 14:29 Maíra Canal
2023-04-12 14:53 ` Ville Syrjälä
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='CAF6AEGs+GP2MCbD=wW+ords=MPFBcV4ncag-5KBfO=2KWg3G0Q@mail.gmail.com' \
--to=robdclark@gmail.com \
--cc=andrealmeid@igalia.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=mcanal@igalia.com \
--cc=mwen@igalia.com \
--cc=robdclark@chromium.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).