[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190704111927.u34xaaqeeiwrwrtb@sirius.home.kraxel.org>
Date: Thu, 4 Jul 2019 13:19:27 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Chia-I Wu <olvaffe@...il.com>
Cc: ML dri-devel <dri-devel@...ts.freedesktop.org>,
Gurchetan Singh <gurchetansingh@...omium.org>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
"open list:VIRTIO GPU DRIVER"
<virtualization@...ts.linux-foundation.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v6 07/18] drm/virtio: add virtio_gpu_object_array &
helpers
> > > +int virtio_gpu_array_lock_resv(struct virtio_gpu_object_array *objs)
> > > +{
> > > + return drm_gem_lock_reservations(objs->objs, objs->nents,
> > > + &objs->ticket);
> Unlike in other drivers where an "object array" is only needed in
> execbuffer, we will use this in several places, and often with only 1
> object in the array. Can we special case that and do a quick
> reservation_object_lock?
Yes, done.
> > > +void virtio_gpu_array_unlock_resv(struct virtio_gpu_object_array *objs)
> > > +{
> > > + drm_gem_unlock_reservations(objs->objs, objs->nents,
> > > + &objs->ticket);
> > > +}
> > > +
Likewise here.
cheers,
Gerd
Powered by blists - more mailing lists