similar to: [PATCH 0/2] remoteproc : support for host virtio

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

Implement the vringh callback functions in order to manage host virito rings and handle kicks. This allows virtio device to request host-virtio-rings. Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi Ohad and Rusty, This v2 version is simpler, more readable and verbose (+50 lines) compared to the previous patch. This patch probably should to go via Rusty's

Implement the vringh callback functions in order to manage host virito rings and handle kicks. This allows virtio device to request host-virtio-rings. Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi Ohad and Rusty, This v2 version is simpler, more readable and verbose (+50 lines) compared to the previous patch. This patch probably should to go via Rusty's

Rusty, here is just patch 1 (using bool as return value in notify API). Thanks. Heinz Graalfs (9): virtio_ring: change host notification API virtio_ring: let virtqueue_{kick()/notify()} return a bool virtio_net: verify if virtqueue_kick() succeeded virtio_test: verify if virtqueue_kick() succeeded virtio_ring: add new function virtqueue_is_broken() virtio_blk: verify if queue is

Rusty, here is just patch 1 (using bool as return value in notify API). Thanks. Heinz Graalfs (9): virtio_ring: change host notification API virtio_ring: let virtqueue_{kick()/notify()} return a bool virtio_net: verify if virtqueue_kick() succeeded virtio_test: verify if virtqueue_kick() succeeded virtio_ring: add new function virtqueue_is_broken() virtio_blk: verify if queue is

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Hi Ohad, Ido and Rusty. Rusty has implemented host-side virtio ring. I will be using vringh for the caif_virtio driver. But we need to figure out how to integrate the vringh into remoteproc. Below is my initial stab on this. This code is completely untested, but I'd love to get some initial feedback on this. Ohad/Ido are you

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> Hi Ohad, Ido and Rusty. Rusty has implemented host-side virtio ring. I will be using vringh for the caif_virtio driver. But we need to figure out how to integrate the vringh into remoteproc. Below is my initial stab on this. This code is completely untested, but I'd love to get some initial feedback on this. Ohad/Ido are you

Hi, this patch-set solves a hang situation when a vlan network device is hot-unplugged from a KVM guest. On System z there exists no handshake mechanism between host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. The guest is notified about the hard removal with a CRW machine check. As per architecture, the host must repond to any I/O operation

Hi, this patch-set solves a hang situation when a vlan network device is hot-unplugged from a KVM guest. On System z there exists no handshake mechanism between host and guest when a device is hot-unplugged. The device is removed and no further I/O is possible. The guest is notified about the hard removal with a CRW machine check. As per architecture, the host must repond to any I/O operation

On Wed, 20 Dec 2017 12:27:33 +0800 weiping zhang <zwp10758 at gmail.com> wrote: > rproc_virtio_dev_release will be called iff virtio_device.dev's > refer count became to 0. Here we should check if we call device_register "reference count drops to 0" s/call/called/ > or not, if called, put vdev.dev, and then rproc->dev's cleanup will be > done in

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 8ab881d0e8136390da79aa0902fe03d2f6c65e32 commit: 281310d52c1d63630f54b1ac5cca6e9eb8715b3a [6/19] virtio: add context flag to find vqs config: x86_64-randconfig-i0-201713 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout 281310d52c1d63630f54b1ac5cca6e9eb8715b3a

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 8ab881d0e8136390da79aa0902fe03d2f6c65e32 commit: 281310d52c1d63630f54b1ac5cca6e9eb8715b3a [6/19] virtio: add context flag to find vqs config: x86_64-randconfig-i0-201713 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout 281310d52c1d63630f54b1ac5cca6e9eb8715b3a

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 8ab881d0e8136390da79aa0902fe03d2f6c65e32 commit: 281310d52c1d63630f54b1ac5cca6e9eb8715b3a [6/19] virtio: add context flag to find vqs config: i386-randconfig-s0-201713 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: git checkout 281310d52c1d63630f54b1ac5cca6e9eb8715b3a

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: 8ab881d0e8136390da79aa0902fe03d2f6c65e32 commit: 281310d52c1d63630f54b1ac5cca6e9eb8715b3a [6/19] virtio: add context flag to find vqs config: i386-randconfig-s0-201713 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: git checkout 281310d52c1d63630f54b1ac5cca6e9eb8715b3a

Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get

Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get

Currently a host kick error is silently ignored and not reflected in the virtqueue of a particular virtio device. Changing the notify API for guest->host notification seems to be one prerequisite in order to be able to handle such errors in the context where the kick is triggered. This patch changes the notify API. The notify function must return a negative int return value in case the host