From: Jens Freimann <jfrei@linux.vnet.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: David Hildenbrand <dahi@linux.vnet.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 09/10] s390x/kvm: deliver SIGP RESTART directly if stopped
Date: Tue, 24 Feb 2015 14:15:30 +0100 [thread overview]
Message-ID: <1424783731-43426-10-git-send-email-jfrei@linux.vnet.ibm.com> (raw)
In-Reply-To: <1424783731-43426-1-git-send-email-jfrei@linux.vnet.ibm.com>
From: David Hildenbrand <dahi@linux.vnet.ibm.com>
According to the PoP, a restart irq has to be delivered "without first honoring
any other pending interruptions", if a cpu is in the STOPPED state.
While it is hard to implement this case in kvm, it can easily be handled in qemu.
Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
---
target-s390x/kvm.c | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/target-s390x/kvm.c b/target-s390x/kvm.c
index ed56b3c..7f9fd02 100644
--- a/target-s390x/kvm.c
+++ b/target-s390x/kvm.c
@@ -1241,8 +1241,17 @@ static void sigp_restart(void *arg)
.type = KVM_S390_RESTART,
};
- kvm_s390_vcpu_interrupt(si->cpu, &irq);
- s390_cpu_set_state(CPU_STATE_OPERATING, si->cpu);
+ switch (s390_cpu_get_state(si->cpu)) {
+ case CPU_STATE_STOPPED:
+ /* the restart irq has to be delivered prior to any other pending irq */
+ cpu_synchronize_state(CPU(si->cpu));
+ do_restart_interrupt(&si->cpu->env);
+ s390_cpu_set_state(CPU_STATE_OPERATING, si->cpu);
+ break;
+ case CPU_STATE_OPERATING:
+ kvm_s390_vcpu_interrupt(si->cpu, &irq);
+ break;
+ }
si->cc = SIGP_CC_ORDER_CODE_ACCEPTED;
}
--
2.1.4
next prev parent reply other threads:[~2015-02-24 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 13:15 [Qemu-devel] [PATCH 00/10] s390x: move sigp handling to user space Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 01/10] s390x: introduce defines for SIGP condition codes Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 02/10] s390x/kvm: more details for SIGP handler with one destination vcpu Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 03/10] s390x/kvm: pass the SIGP instruction parameter to the SIGP handler Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 04/10] s390x/kvm: helper to set the SIGP status in SigpInfo Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 05/10] s390x/kvm: trace all SIGP orders Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 06/10] s390x/kvm: implement handling of new " Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 07/10] s390x/kvm: SIGP START is only applicable when STOPPED Jens Freimann
2015-02-24 13:15 ` [Qemu-devel] [PATCH 08/10] s390x: add function to deliver restart irqs Jens Freimann
2015-02-24 13:15 ` Jens Freimann [this message]
2015-02-24 13:15 ` [Qemu-devel] [PATCH 10/10] s390x/kvm: enable the new SIGP handling in user space Jens Freimann
2015-03-03 14:02 ` [Qemu-devel] [PATCH 00/10] s390x: move sigp handling to " Christian Borntraeger
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=1424783731-43426-10-git-send-email-jfrei@linux.vnet.ibm.com \
--to=jfrei@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=dahi@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).