[PATCH] virtio_pmem: fix sparse warning

2019-07-10 Thread Pankaj Gupta
This patch fixes below sparse warning related to __virtio type in virtio pmem driver. This is reported by Intel test bot on linux-next tree. nd_virtio.c:56:28: warning: incorrect type in assignment (different base types) nd_virtio.c:56:28:expected unsigned int [unsigned] [usertype] type

[RFC] virtio-net: share receive_*() and add_recvbuf_*() with virtio-vsock

2019-07-10 Thread Stefano Garzarella
Hi, as Jason suggested some months ago, I looked better at the virtio-net driver to understand if we can reuse some parts also in the virtio-vsock driver, since we have similar challenges (mergeable buffers, page allocation, small packets, etc.). Initially, I would add the skbuff in the

[PATCH v2] virtio_pmem: fix sparse warning

2019-07-10 Thread Pankaj Gupta
This patch fixes below sparse warning related to __virtio type in virtio pmem driver. This is reported by Intel test bot on linux-next tree. nd_virtio.c:56:28: warning: incorrect type in assignment (different base types) nd_virtio.c:56:28:expected unsigned int

[PATCH AUTOSEL 5.1 03/11] drm/virtio: move drm_connector_update_edid_property() call

2019-07-10 Thread Sasha Levin
From: Gerd Hoffmann [ Upstream commit 41de4be6f6efa4132b29af51158cd672d93f2543 ] drm_connector_update_edid_property can sleep, we must not call it while holding a spinlock. Move the callsite. Fixes: b4b01b4995fb ("drm/virtio: add edid support") Reported-by: Max Filippov Signed-off-by: Gerd

Re: [PATCH v2 3/6] drm/fb-helper: Instanciate shadow FB if configured in device's mode_config

2019-07-10 Thread Daniel Vetter
On Sun, Jul 07, 2019 at 06:14:50PM +0200, Thomas Zimmermann wrote: > Hi > > Am 07.07.19 um 16:37 schrieb Noralf Trønnes: > > > > > > Den 05.07.2019 11.26, skrev Thomas Zimmermann: > >> Generic framebuffer emulation uses a shadow buffer for framebuffers with > >> dirty() function. If drivers

[PATCH] drm/virtio: kick vq outside of the vq lock

2019-07-10 Thread Chia-I Wu
Replace virtqueue_kick by virtqueue_kick_prepare, which requires serialization, and virtqueue_notify, which does not. Repurpose the return values to indicate whether the vq should be notified. This fixes a lock contention with qemu host. When the guest calls vibad rtqueue_notify, the qemu vcpu

Re: [PATCH v6 08/18] drm/virtio: rework virtio_gpu_execbuffer_ioctl fencing

2019-07-10 Thread Chia-I Wu
On Thu, Jul 4, 2019 at 11:46 AM Chia-I Wu wrote: > > On Thu, Jul 4, 2019 at 4:25 AM Gerd Hoffmann wrote: > > > > Hi, > > > > > > if (fence) > > > > virtio_gpu_fence_emit(vgdev, hdr, fence); > > > > + if (vbuf->objs) { > > > > +

[PATCH] drm/virtio: kick vq outside of the vq lock

2019-07-10 Thread Chia-I Wu
Replace virtqueue_kick by virtqueue_kick_prepare, which requires serialization, and virtqueue_notify, which does not. Repurpose the return values to indicate whether the vq should be notified. This fixes a bad spinlock contention when the host is qemu. When the guest calls virtqueue_notify, the

Re: [RFC v2] vhost: introduce mdev based hardware vhost backend

2019-07-10 Thread Tiwei Bie
On Wed, Jul 10, 2019 at 10:26:10AM +0800, Jason Wang wrote: > On 2019/7/9 下午2:33, Tiwei Bie wrote: > > On Tue, Jul 09, 2019 at 10:50:38AM +0800, Jason Wang wrote: > > > On 2019/7/8 下午2:16, Tiwei Bie wrote: > > > > On Fri, Jul 05, 2019 at 08:49:46AM -0600, Alex Williamson wrote: > > > > > On Thu, 4

Re: [RFC v2] vhost: introduce mdev based hardware vhost backend

2019-07-10 Thread Jason Wang
On 2019/7/10 下午2:22, Tiwei Bie wrote: On Wed, Jul 10, 2019 at 10:26:10AM +0800, Jason Wang wrote: On 2019/7/9 下午2:33, Tiwei Bie wrote: On Tue, Jul 09, 2019 at 10:50:38AM +0800, Jason Wang wrote: On 2019/7/8 下午2:16, Tiwei Bie wrote: On Fri, Jul 05, 2019 at 08:49:46AM -0600, Alex Williamson