similar to: [PATCH v7 08/19] virtio_input: pull in slab.h

In preparation to virtio header changes, include slab.h directly as this module is using it. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_input.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/virtio/virtio_input.c b/drivers/virtio/virtio_input.c index 5ae529671b3d..efaf65b0f42d 100644 --- a/drivers/virtio/virtio_input.c +++

For multi-touch devices the frontend needs to initialize the correct number of slots for touch tracking. Hardware drivers do this by calling input_mt_init_slots() on initialization. For virtio_input the function must be called when the backend sends ABS_MT_SLOT. Signed-off-by: Rudolf J Streif <rstreif at blackberry.com> --- drivers/virtio/virtio_input.c | 4 ++++ 1 file changed, 4

Resubmit. Thank you. ________________________________ From: Virtualization <virtualization-bounces at lists.linux-foundation.org> on behalf of Rudolf Streif <rstreif at blackberry.com> Sent: Thursday, January 2, 2020 11:12 AM To: kraxel at redhat.com Cc: virtualization at lists.linux-foundation.org Subject: [PATCH] virtio_input: Initialize multi-touch slots on ABS_MT_SLOT For

Virtio input is modern-only. Use LE accessors for config space. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_input.c | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) diff --git a/drivers/virtio/virtio_input.c b/drivers/virtio/virtio_input.c index efaf65b0f42d..877b2ea3ed05 100644 --- a/drivers/virtio/virtio_input.c

This patch adds virtio-pmem driver for KVM guest. Guest reads the persistent memory range information from Qemu over VIRTIO and registers it on nvdimm_bus. It also creates a nd_region object with the persistent memory range information so that existing 'nvdimm/pmem' driver can reserve this into system memory map. This way 'virtio-pmem' driver uses existing functionality of pmem

Hi Dan, Thank you for the review. Please see my reply inline. > > Hi Pankaj, > > Some minor file placement comments below. Sure. > > On Thu, Apr 25, 2019 at 10:02 PM Pankaj Gupta <pagupta at redhat.com> wrote: > > > > This patch adds virtio-pmem driver for KVM guest. > > > > Guest reads the persistent memory range information from > >

The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136: Linux 5.7-rc1 (2020-04-12 12:35:55 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to d085eb8ce727e581abf8145244eaa3339021be2f: vhost: disable for OABI (2020-04-20 10:19:22 -0400) Changes from v1: Dropped a

In preparation to virtio header changes, include uaccess.h directly as this file is using copy to/from user. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_ioctl.c index 205ec4abae2b..2342a8baa5f8 100644 ---

The following changes since commit 835a6a649d0dd1b1f46759eb60fff2f63ed253a7: virtio-balloon: Revert "virtio-balloon: Switch back to OOM handler for VIRTIO_BALLOON_F_DEFLATE_ON_OOM" (2020-04-07 05:44:57 -0400) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to

The following changes since commit 835a6a649d0dd1b1f46759eb60fff2f63ed253a7: virtio-balloon: Revert "virtio-balloon: Switch back to OOM handler for VIRTIO_BALLOON_F_DEFLATE_ON_OOM" (2020-04-07 05:44:57 -0400) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to

virtio-input is basically evdev-events-over-virtio, so this driver isn't much more than reading configuration from config space and forwarding incoming events to the linux input layer. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_input.c | 313

virtio-input is basically evdev-events-over-virtio, so this driver isn't much more than reading configuration from config space and forwarding incoming events to the linux input layer. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 + drivers/virtio/virtio_input.c | 313

On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Looks pretty neat overall. I think I still see some small

On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > virtio-input is basically evdev-events-over-virtio, so this driver isn't > much more than reading configuration from config space and forwarding > incoming events to the linux input layer. > > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Looks pretty neat overall. I think I still see some small

On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > > > much more than reading configuration from config space and forwarding > >

On Tue, Mar 24, 2015 at 09:23:37AM -0700, Dmitry Torokhov wrote: > On Tue, Mar 24, 2015 at 11:36:31AM +0100, Michael S. Tsirkin wrote: > > On Tue, Mar 24, 2015 at 08:32:01AM +0100, Gerd Hoffmann wrote: > > > virtio-input is basically evdev-events-over-virtio, so this driver isn't > > > much more than reading configuration from config space and forwarding > >

On Fri, Apr 26, 2019 at 10:30:35AM +0530, Pankaj Gupta wrote: > This patch adds virtio-pmem driver for KVM guest. > > Guest reads the persistent memory range information from > Qemu over VIRTIO and registers it on nvdimm_bus. It also > creates a nd_region object with the persistent memory > range information so that existing 'nvdimm/pmem' driver > can reserve this

virtio-input is basically evdev-events-over-virtio, so this driver isn't much more than reading configuration from config space and forwarding incoming events to the linux input layer. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- MAINTAINERS | 6 + drivers/virtio/Kconfig | 10 + drivers/virtio/Makefile | 1 +

virtio-input is basically evdev-events-over-virtio, so this driver isn't much more than reading configuration from config space and forwarding incoming events to the linux input layer. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- MAINTAINERS | 6 + drivers/virtio/Kconfig | 10 + drivers/virtio/Makefile | 1 +

virtio-input is basically evdev-events-over-virtio, so this driver isn't much more than reading configuration from config space and forwarding incoming events to the linux input layer. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- MAINTAINERS | 6 + drivers/virtio/Kconfig | 10 ++ drivers/virtio/Makefile | 1 +