From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
david@redhat.com, thuth@redhat.com
Subject: [PATCH v1 0/4] s390x: Testing the Subchannel I/O
Date: Wed, 13 Nov 2019 13:23:15 +0100 [thread overview]
Message-ID: <1573647799-30584-1-git-send-email-pmorel@linux.ibm.com> (raw)
Goal of the series is to have a framwork to test Channel-Subsystem I/O with
QEMU/KVM.
To be able to support interrupt for CSS I/O and for SCLP we need to modify
the interrupt framework to allow re-entrant interruptions.
Making the interrupt handler weak allows the test programm to define its own
interrupt handler. We need to do special work under interrupt like acknoledging
the interrupt.
Being working on PSW bits to allow I/O interrupt, we define all PSW bits in a
dedicated file.
The simple test tests the I/O reading by the SUB Channel. It needs QEMU to
be patched to have the pong device defined.
The pong device answers, for now, with a Hello World to the read request.
Pierre Morel (4):
s390x: saving regs for interrupts
s390x: Define the PSW bits
s390x:irq: make IRQ handler weak
s390x: Testing the Subchannel I/O read
lib/s390x/asm/arch_bits.h | 32 ++++++
lib/s390x/asm/arch_def.h | 6 +-
lib/s390x/asm/interrupt.h | 15 ++-
lib/s390x/css.h | 244 ++++++++++++++++++++++++++++++++++++++++++++++
lib/s390x/css_dump.c | 141 +++++++++++++++++++++++++++
lib/s390x/interrupt.c | 16 +--
s390x/Makefile | 2 +
s390x/css.c | 222 +++++++++++++++++++++++++++++++++++++++++
s390x/cstart64.S | 30 ++++--
s390x/unittests.cfg | 4 +
10 files changed, 686 insertions(+), 26 deletions(-)
create mode 100644 lib/s390x/asm/arch_bits.h
create mode 100644 lib/s390x/css.h
create mode 100644 lib/s390x/css_dump.c
create mode 100644 s390x/css.c
--
2.7.4
next reply other threads:[~2019-11-13 12:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 12:23 Pierre Morel [this message]
2019-11-13 12:23 ` [PATCH v1 1/4] s390x: saving regs for interrupts Pierre Morel
2019-11-13 16:12 ` Janosch Frank
2019-11-14 10:11 ` Pierre Morel
2019-11-14 10:28 ` David Hildenbrand
2019-11-14 11:57 ` Pierre Morel
2019-11-14 12:11 ` David Hildenbrand
2019-11-14 15:21 ` Pierre Morel
2019-11-14 15:25 ` David Hildenbrand
2019-11-14 16:15 ` Pierre Morel
2019-11-13 12:23 ` [PATCH v1 2/4] s390x: Define the PSW bits Pierre Morel
2019-11-13 16:05 ` Janosch Frank
2019-11-14 8:40 ` Pierre Morel
2019-11-14 8:53 ` Janosch Frank
2019-11-14 15:25 ` Pierre Morel
2019-11-13 12:23 ` [PATCH v1 3/4] s390x:irq: make IRQ handler weak Pierre Morel
2019-11-15 7:12 ` Thomas Huth
2019-11-18 9:04 ` Pierre Morel
2019-11-13 12:23 ` [PATCH v1 4/4] s390x: Testing the Subchannel I/O read Pierre Morel
2019-11-13 13:05 ` Cornelia Huck
2019-11-14 10:11 ` Pierre Morel
2019-11-21 16:02 ` Cornelia Huck
2019-11-22 9:03 ` Pierre Morel
2019-11-22 10:54 ` Cornelia Huck
2019-11-22 12:48 ` Pierre Morel
2019-11-14 9:15 ` Janosch Frank
2019-11-14 16:38 ` Pierre Morel
2019-11-14 16:51 ` Thomas Huth
2019-11-14 17:50 ` Pierre Morel
2019-11-14 17:09 ` Janosch Frank
2019-11-14 17:55 ` Pierre Morel
2019-11-13 12:35 ` [PATCH v1 0/4] s390x: Testing the Subchannel I/O Thomas Huth
2019-11-13 12:43 ` 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=1573647799-30584-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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