From: Pierre Morel <pmorel@linux.ibm.com>
To: qemu-s390x@nongnu.org
Cc: thuth@redhat.com, frankja@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, qemu-devel@nongnu.org, pasic@linux.ibm.com,
borntraeger@de.ibm.com
Subject: [PATCH v3 0/1] s390x: css: pong, channel subsystem test device
Date: Mon, 18 May 2020 18:43:40 +0200 [thread overview]
Message-ID: <1589820221-23538-1-git-send-email-pmorel@linux.ibm.com> (raw)
This patch series presents a device to test the channel subsystem.
Currently the pong device does the following:
- on PONG_WRITE requests:
read the CCW buffer, expect a string with an integer in the buffer.
store the integer in a variable initialy initialized to zero.
- on PONG_READ requests:
Store the value of the variable + 1 as a string in a buffer
send back the buffer
- defines a Control Unit property of type CCW_PONG_CU_TYPE
for the guest to recognize the PONG device when using a
SENSE_ID command.
Pierre Morel (1):
s390x: css: pong, channel subsystem test device
default-configs/s390x-softmmu.mak | 1 +
hw/s390x/Kconfig | 3 +
hw/s390x/Makefile.objs | 1 +
hw/s390x/ccw-pong.c | 134 ++++++++++++++++++++++++++++++
include/hw/s390x/pong.h | 48 +++++++++++
5 files changed, 187 insertions(+)
create mode 100644 hw/s390x/ccw-pong.c
create mode 100644 include/hw/s390x/pong.h
--
2.25.1
Changelog:
from v2 to v3
- rebase to devel
- use device_class_set_props()
from v1 to v2
- use ccw_dstream_xxx_buf (Connie)
- adding a cu_type property
- testing the ccw.count
- conditional compiling for TEST_DEVICES (Connie, Thomas)
- suppress the device categorie (Connie ?)
- adding write callback and some funny protocol
next reply other threads:[~2020-05-18 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 16:43 Pierre Morel [this message]
2020-05-18 16:43 ` [PATCH v3 1/1] s390x: css: pong, channel subsystem test device Pierre Morel
-- strict thread matches above, loose matches on Subject: below --
2020-02-20 11:59 [PATCH v3 0/1] " 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=1589820221-23538-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=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.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).