From: Thomas Huth <thuth@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Pierre Morel <pmorel@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, imbrenda@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 6/7] s390x: virtio tests setup
Date: Wed, 3 Nov 2021 09:14:30 +0100 [thread overview]
Message-ID: <c977b200-ba2d-d3eb-eae0-75a17d16496d@redhat.com> (raw)
In-Reply-To: <20211103075636.hgxckmxs62bsdrha@gator.home>
On 03/11/2021 08.56, Andrew Jones wrote:
> On Fri, Aug 27, 2021 at 12:17:19PM +0200, Pierre Morel wrote:
>> +
>> +#define VIRTIO_ID_PONG 30 /* virtio pong */
>
> I take it this is a virtio test device that ping-pong's I/O. It sounds
> useful for other VIRTIO transports too. Can it be ported? Hmm, I can't
> find it in QEMU at all?
I also wonder whether we could do testing with an existing device instead?
E.g. do a loopback with a virtio-serial device? Or use two virtio-net
devices, connect them to a QEMU hub and send a packet from one device to the
other? ... that would be a little bit more complicated here, but would not
require a PONG device upstream first, so it could also be used for testing
older versions of QEMU...
Thomas
next prev parent reply other threads:[~2021-11-03 8:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 10:17 [kvm-unit-tests PATCH 0/7] Extending VIRTIO with a data transfer test Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 1/7] arm: virtio: move VIRTIO transport initialization inside virtio-mmio Pierre Morel
2021-11-03 7:00 ` Thomas Huth
2021-11-03 7:41 ` Andrew Jones
2021-11-08 12:20 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 2/7] s390x: css: add callback for emnumeration Pierre Morel
2021-11-03 7:29 ` Thomas Huth
2021-11-08 12:21 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 3/7] s390x: virtio: CCW transport implementation Pierre Morel
2021-11-03 7:46 ` Andrew Jones
2021-11-08 12:35 ` Pierre Morel
2021-11-03 7:49 ` Thomas Huth
2021-11-08 12:34 ` Pierre Morel
2021-11-09 7:01 ` Thomas Huth
2021-11-09 8:51 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 4/7] s390x: css: registering IRQ Pierre Morel
2021-11-03 8:01 ` Thomas Huth
2021-11-08 12:36 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 5/7] virtio: implement the virtio_add_inbuf routine Pierre Morel
2021-11-03 7:51 ` Andrew Jones
2021-11-08 12:36 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 6/7] s390x: virtio tests setup Pierre Morel
2021-11-03 7:56 ` Andrew Jones
2021-11-03 8:14 ` Thomas Huth [this message]
2021-11-08 13:00 ` Pierre Morel
2021-11-09 7:10 ` Thomas Huth
2021-11-09 8:42 ` Andrew Jones
2021-11-09 9:01 ` Pierre Morel
2021-11-08 12:53 ` Pierre Morel
2021-08-27 10:17 ` [kvm-unit-tests PATCH 7/7] s390x: virtio data transfer 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=c977b200-ba2d-d3eb-eae0-75a17d16496d@redhat.com \
--to=thuth@redhat.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=pmorel@linux.ibm.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