[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b699fce8-4c76-c997-f989-7406cc3d4c92@vmware.com>
Date: Thu, 5 Apr 2018 13:42:11 +0200
From: Thomas Hellstrom <thellstrom@...are.com>
To: Deepak Rawat <drawat@...are.com>, dri-devel@...ts.freedesktop.org,
syeh@...are.com, linux-graphics-maintainer@...are.com,
ville.syrjala@...ux.intel.com, lukasz.spintzyk@...playlink.com,
noralf@...nnes.org, robdclark@...il.com, gustavo@...ovan.org,
maarten.lankhorst@...ux.intel.com, seanpaul@...omium.org,
airlied@...ux.ie, linux-kernel@...r.kernel.org
Subject: Re: [RFC 1/3] drm: Add DAMAGE_CLIPS property to plane
On 04/05/2018 12:03 PM, Daniel Vetter wrote:
>
> On the topic of input validation: Should the kernel check in shared code
> that all the clip rects are sensible, i.e. within the dimensions of the
> fb? Relying on drivers for that seems like a bad idea.
I guess we could do that.
There seems to be different needs for different kinds of iterators, but
otherwise
I was thinking that an iterator could just skip invalid rects if found.
Then we
don't need a separate validation step, but OTOH user-space won't get
notified if
that was intended.
I'm not 100% sure user-space would do anything sensible with any error
information, though.
/Thomas
>
> That could be done in core code in drm_atomic_plane_check().
> -Daniel
>> /Thomas
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@...ts.freedesktop.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_dri-2Ddevel&d=DwIBAg&c=uilaK90D4TOVoH58JNXRgQ&r=wnSlgOCqfpNS4d02vP68_E9q2BNMCwfD2OZ_6dCFVQQ&m=JV7fhQ4zTiyiKsY8M0Zlf81l7szYePUke8kwSvQv1T8&s=HEcbr-8aoWqRvWGY6RcL1QeAtEyxMRLHbsOtdJFk78I&e=
Powered by blists - more mailing lists