From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: thuth@redhat.com, frankja@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, richard.henderson@linaro.org,
drjones@redhat.com, qemu-devel@nongnu.org, pasic@linux.ibm.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org, mst@redhat.com,
imbrenda@linux.ibm.com
Subject: [PATCH 0/2] s390x: ccw: A simple test device for virtio CCW
Date: Fri, 27 Aug 2021 12:50:48 +0200 [thread overview]
Message-ID: <1630061450-18744-1-git-send-email-pmorel@linux.ibm.com> (raw)
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:
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
--
2.25.1
next reply other threads:[~2021-08-27 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 10:50 Pierre Morel [this message]
2021-08-27 10:50 ` [PATCH 1/2] virtio: Linux: Update of virtio_ids Pierre Morel
2021-08-27 10:50 ` [PATCH 2/2] s390x: ccw: A simple test device for virtio CCW Pierre Morel
2021-08-30 9:51 ` [PATCH 0/2] " Christian Borntraeger
2021-08-30 12:05 ` Pierre Morel
2021-08-30 20:42 ` Halil Pasic
2021-09-01 13:59 ` Pierre Morel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1630061450-18744-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).