From: Pierre Morel <pmorel@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, frankja@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, richard.henderson@linaro.org,
pasic@linux.ibm.com, borntraeger@de.ibm.com,
qemu-s390x@nongnu.org, mst@redhat.com, pbonzini@redhat.com,
marcandre.lureau@redhat.com, imbrenda@linux.ibm.com
Subject: [PATCH v1 0/1] s390x: css: report errors from ccw_dstream_read/write
Date: Tue, 6 Apr 2021 09:44:12 +0200 [thread overview]
Message-ID: <1617695053-7328-1-git-send-email-pmorel@linux.ibm.com> (raw)
By checking the results of errors on SSCH in the kvm-unit-tests
We noticed that no error was reported when a SSCH is started
to access addresses not existing in the guest.
For exemple accessing 3G on a guest with 1G memory.
If we look at QEMU ccw_dstream_write/write functions we see that they
are often not checked for error in various places.
It follows that accessing an invalid address does not trigger a
subchannel status program check to the guest as it should.
Regards,
Pierre
Pierre Morel (1):
s390x: css: report errors from ccw_dstream_read/write
hw/char/terminal3270.c | 11 +++++--
hw/s390x/3270-ccw.c | 3 ++
hw/s390x/css.c | 16 +++++-----
hw/s390x/virtio-ccw.c | 66 ++++++++++++++++++++++++++++++------------
4 files changed, 69 insertions(+), 27 deletions(-)
--
2.17.1
next reply other threads:[~2021-04-06 7:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 7:44 Pierre Morel [this message]
2021-04-06 7:44 ` [PATCH v1 1/1] s390x: css: report errors from ccw_dstream_read/write Pierre Morel
2021-04-06 15:03 ` Cornelia Huck
2021-04-07 11:41 ` Pierre Morel
2021-04-07 16:54 ` Halil Pasic
2021-04-08 8:53 ` Cornelia Huck
2021-04-07 17:47 ` Halil Pasic
2021-04-08 9:02 ` Cornelia Huck
2021-04-08 12:32 ` Pierre Morel
2021-04-08 13:23 ` Cornelia Huck
2021-04-08 16:18 ` Pierre Morel
2021-04-08 12:39 ` Halil Pasic
2021-04-08 13:26 ` Cornelia Huck
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=1617695053-7328-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=imbrenda@linux.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.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).