similar to: [PATCH v2 1/8] drm: Disable the cursor plane on atomic contexts with virtualized drivers

On Thu, 4 May 2023 01:50:25 +0000 Zack Rusin <zackr at vmware.com> wrote: > On Wed, 2023-05-03 at 09:48 +0200, Javier Martinez Canillas wrote: > > Zack Rusin <zackr at vmware.com> writes: > > > > > On Tue, 2023-05-02 at 11:32 +0200, Javier Martinez Canillas wrote: > > > > AFAICT this is the only remaining thing to be addressed for this series

On Thu, 4 May 2023 01:43:51 +0000 Zack Rusin <zackr at vmware.com> wrote: > On Wed, 2023-05-03 at 10:54 +0300, Pekka Paalanen wrote: > > On Wed, 3 May 2023 03:35:29 +0000 > > Zack Rusin <zackr at vmware.com> wrote: > > > > > On Tue, 2023-05-02 at 11:32 +0200, Javier Martinez Canillas wrote: > > > > !! External Email > > > >

On Thu, Dec 03, 2020 at 03:06:20AM +0000, Zack Rusin wrote: > > > > On Dec 2, 2020, at 11:03, Daniel Vetter <daniel at ffwll.ch> wrote: > > > > On Wed, Dec 2, 2020 at 4:37 PM Zack Rusin <zackr at vmware.com> wrote: > >> > >> > >> > >>> On Dec 2, 2020, at 09:27, Thomas Zimmermann <tzimmermann at suse.de> wrote:

> On Dec 2, 2020, at 09:27, Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Hi > > Am 02.12.20 um 09:01 schrieb Thomas Zimmermann: >> Hi >> Am 30.11.20 um 21:59 schrieb Zack Rusin: >>> >>> >>>> On Nov 24, 2020, at 06:38, Thomas Zimmermann <tzimmermann at suse.de> wrote: >>>> >>>> Using struct

> On Nov 24, 2020, at 06:38, Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Using struct drm_device.pdev is deprecated. Convert vmwgfx to struct > drm_device.dev. No functional changes. > > Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> > Cc: Roland Scheidegger <sroland at vmware.com> > --- > drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c |

Prepare for the coming implementation by GCC and Clang of the __counted_by attribute. Flexible array members annotated with __counted_by can have their accesses bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). As found with Coccinelle[1], add __counted_by for struct vmw_surface_dirty. [1]

Prepare for the coming implementation by GCC and Clang of the __counted_by attribute. Flexible array members annotated with __counted_by can have their accesses bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). As found with Coccinelle[1], add __counted_by for struct vmw_surface_dirty. [1]

Prepare for the coming implementation by GCC and Clang of the __counted_by attribute. Flexible array members annotated with __counted_by can have their accesses bounds-checked at run-time checking via CONFIG_UBSAN_BOUNDS (for array indexing) and CONFIG_FORTIFY_SOURCE (for strcpy/memcpy-family functions). As found with Coccinelle[1], add __counted_by for struct vmw_surface_dirty. [1]

Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: > From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> > > Currently drm_gem_handle_create_tail exposes the handle to userspace > before the buffer object constructions is complete. This allowing > of working against a partially constructed object, which may also be in > the process of having its creation fail, can have a range of

Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: > From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> > > Currently drm_gem_handle_create_tail exposes the handle to userspace > before the buffer object constructions is complete. This allowing > of working against a partially constructed object, which may also be in > the process of having its creation fail, can have a range of

Hello Thomas, On 1/10/23 13:35, Thomas Zimmermann wrote: > Commit 4a16dd9d18a0 ("drm/nouveau/kms: switch to drm fbdev helpers") > converted nouveau to generic fbdev emulation. The driver's internal > implementation later got accidentally restored during a merge commit. > Remove the file from the driver. No functional changes. > > v2: > * point Fixes tag to

Am 20.02.23 um 10:55 schrieb Tvrtko Ursulin: > > Hi, > > On 14/02/2023 13:59, Christian K?nig wrote: >> Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: >>> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> >>> >>> Currently drm_gem_handle_create_tail exposes the handle to userspace >>> before the buffer object constructions is complete.

On Fri, Mar 10, 2023 at 01:59:42PM +0100, Javier Martinez Canillas wrote: > Christian Hergert reports that the driver doesn't enable the property and > that leads to always doing a full plane update, even when the driver does > support damage clipping for the primary plane. > > Don't enable it for the cursor plane, because its .atomic_update callback > doesn't handle

From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> Currently drm_gem_handle_create_tail exposes the handle to userspace before the buffer object constructions is complete. This allowing of working against a partially constructed object, which may also be in the process of having its creation fail, can have a range of negative outcomes. A lot of those will depend on what the individual

From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> Currently drm_gem_handle_create_tail exposes the handle to userspace before the buffer object constructions is complete. This allowing of working against a partially constructed object, which may also be in the process of having its creation fail, can have a range of negative outcomes. A lot of those will depend on what the individual

On 20/02/2023 10:01, Christian K?nig wrote: > Am 20.02.23 um 10:55 schrieb Tvrtko Ursulin: >> >> Hi, >> >> On 14/02/2023 13:59, Christian K?nig wrote: >>> Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: >>>> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> >>>> >>>> Currently drm_gem_handle_create_tail exposes the handle

On 20/02/2023 10:01, Christian K?nig wrote: > Am 20.02.23 um 10:55 schrieb Tvrtko Ursulin: >> >> Hi, >> >> On 14/02/2023 13:59, Christian K?nig wrote: >>> Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: >>>> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> >>>> >>>> Currently drm_gem_handle_create_tail exposes the handle

Hi, On 14/02/2023 13:59, Christian K?nig wrote: > Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: >> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> >> >> Currently drm_gem_handle_create_tail exposes the handle to userspace >> before the buffer object constructions is complete. This allowing >> of working against a partially constructed object, which may

Hi, On 14/02/2023 13:59, Christian K?nig wrote: > Am 14.02.23 um 13:50 schrieb Tvrtko Ursulin: >> From: Tvrtko Ursulin <tvrtko.ursulin at intel.com> >> >> Currently drm_gem_handle_create_tail exposes the handle to userspace >> before the buffer object constructions is complete. This allowing >> of working against a partially constructed object, which may

From: Rob Clark <robdclark at chromium.org> Add a build option to disable modesetting support. This is useful in cases where the guest only needs to use the GPU in a headless mode, or (such as in the CrOS usage) window surfaces are proxied to a host compositor. As the modesetting ioctls are a big surface area for potential security bugs to be found (it's happened in the past, we