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
Subject: [PATCH v3 0/1] s390x: css: pong, channel subsystem test device
Date: Thu, 20 Feb 2020 12:59:24 +0100 [thread overview]
Message-ID: <1582199965-21584-1-git-send-email-pmorel@linux.ibm.com> (raw)
This patch series presents a device to test the channel subsystem.
Currently it only does the following:
- answer to WRITE requests by incrementing an integer stored as
string in the data of a PONG_WRITE CCW command.
- send back the same buffer, with the incremented integer when
receiving a PONG_READ CCW command.
- defines a Control Unit property.
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 | 140 ++++++++++++++++++++++++++++++
include/hw/s390x/pong.h | 54 ++++++++++++
5 files changed, 199 insertions(+)
create mode 100644 hw/s390x/ccw-pong.c
create mode 100644 include/hw/s390x/pong.h
--
2.17.0
Changelog:
v2 to v3:
- use device_class_set_props() instead to access
the properties directly
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-02-20 12:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 11:59 Pierre Morel [this message]
2020-02-20 11:59 ` [PATCH v3 1/1] s390x: css: pong, channel subsystem test device Pierre Morel
-- strict thread matches above, loose matches on Subject: below --
2020-05-18 16:43 [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=1582199965-21584-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.