On 27.08.21 12:50, Pierre Morel wrote:
Hello All,
This series presents a VIRTIO test device which receives data on its
input channel and sends back a simple checksum for the data it received
on its output channel.
The goal is to allow a simple VIRTIO device driver to check the VIRTIO
initialization and various data transfer.
For this I introduced a new device ID for the device and having no
Linux driver but a kvm-unit-test driver, I have the following
questions:
I think we should reserve an ID in the official virtio spec then for such a device?
Maybe also add mst for such things.
Is there another way to advertise new VIRTIO IDs but Linux?
If this QEMU test meet interest, should I write a Linux test program?
Regards,
Pierre
Pierre Morel (2):
virtio: Linux: Update of virtio_ids
s390x: ccw: A simple test device for virtio CCW
hw/s390x/meson.build | 1 +
hw/s390x/virtio-ccw-pong.c | 66 ++++++++
hw/s390x/virtio-ccw.h | 13 ++
hw/virtio/Kconfig | 5 +
hw/virtio/meson.build | 1 +
hw/virtio/virtio-pong.c | 161 ++++++++++++++++++++
include/hw/virtio/virtio-pong.h | 34 +++++
include/standard-headers/linux/virtio_ids.h | 1 +
8 files changed, 282 insertions(+)
create mode 100644 hw/s390x/virtio-ccw-pong.c
create mode 100644 hw/virtio/virtio-pong.c
create mode 100644 include/hw/virtio/virtio-pong.h
