From: Christian Borntraeger <borntraeger@de.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: [Qemu-devel] [PATCH 5/8] pc-bios/s390-ccw: enable subchannel for IPL I/O devices
Date: Tue, 27 Sep 2016 13:48:34 +0200 [thread overview]
Message-ID: <1474976917-102710-6-git-send-email-borntraeger@de.ibm.com> (raw)
In-Reply-To: <1474976917-102710-1-git-send-email-borntraeger@de.ibm.com>
From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
IPL should cause the IPL I/O device to become enabled. So when handling
the IPL program, we should set the E (Enable) bit. However, virtio-ccw
does not know whether it's dealing with an IPL device or not. Since
trying to perform I/O on a disabled device doesn't make any sense,
let's just always enable it. At the same time we can remove the
SCSW_FCTL_START_FUNC flag as it is ignored for msch anyway and did
not enable the device as intended.
Reported-by: Farhan Ali <alifm@linux.vnet.ibm.com>
Signed-off-by: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
[remove superfluous flag]
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
pc-bios/s390-ccw/virtio.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/pc-bios/s390-ccw/virtio.c b/pc-bios/s390-ccw/virtio.c
index 1d34e8c..b333734 100644
--- a/pc-bios/s390-ccw/virtio.c
+++ b/pc-bios/s390-ccw/virtio.c
@@ -97,7 +97,8 @@ static int run_ccw(VDev *vdev, int cmd, void *ptr, int len)
/* start command processing */
stsch_err(vdev->schid, &schib);
- schib.scsw.ctrl = SCSW_FCTL_START_FUNC;
+ /* enable the subchannel for IPL device */
+ schib.pmcw.ena = 1;
msch(vdev->schid, &schib);
/* start subchannel command */
--
2.5.5
next prev parent reply other threads:[~2016-09-27 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 11:48 [Qemu-devel] [PATCH 0/8] next patches for s390x/kvm Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 1/8] s390x/pci: re-arrange variable declarations Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 2/8] s390x/pci: assign msix io region for each pci device Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 3/8] s390x/pci: code cleanup Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 4/8] s390x/kvm: Fix potential deadlock in sigp handling Christian Borntraeger
2016-09-27 11:48 ` Christian Borntraeger [this message]
2016-09-27 11:48 ` [Qemu-devel] [PATCH 6/8] pc-bios/s390-ccw.img: rebuild image Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 7/8] s390x/css: {c, h, t, r, x}sch: require enable AND device number valid Christian Borntraeger
2016-09-27 11:48 ` [Qemu-devel] [PATCH 8/8] s390x/kvm: fix build against qemu_uuid Christian Borntraeger
2016-09-27 12:32 ` Fam Zheng
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=1474976917-102710-6-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
/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).