From: "Jason J. Herne" <jjherne@us.ibm.com>
To: agraf@suse.de, borntraeger@de.ibm.com, aliguori@us.ibm.com,
mtosatti@redhat.com, qemu-devel@nongnu.org, R65777@freescale.com,
jan.kiszka@siemens.com
Cc: "Jason J. Herne" <jjherne@us.ibm.com>
Subject: [Qemu-devel] [PATCH 7/7 v2] KVM regsync: S390 Relax register synchronization parameters
Date: Thu, 10 Jan 2013 10:29:27 -0500 [thread overview]
Message-ID: <1357831767-4049-1-git-send-email-jjherne@us.ibm.com> (raw)
From: "Jason J. Herne" <jjherne@us.ibm.com>
Some S390 code paths do not need to synchronize the full register state.
This patch changes those paths to only synchronize the runtime register set.
Signed-off-by: Jason J. Herne <jjherne@us.ibm.com>
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
---
target-s390x/kvm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/target-s390x/kvm.c b/target-s390x/kvm.c
index 81fe1a7..d338078 100644
--- a/target-s390x/kvm.c
+++ b/target-s390x/kvm.c
@@ -354,7 +354,7 @@ static int kvm_sclp_service_call(S390CPU *cpu, struct kvm_run *run,
uint64_t code;
int r = 0;
- cpu_synchronize_state(env, KVM_REGSYNC_FULL_STATE);
+ cpu_synchronize_state(env, KVM_REGSYNC_RUNTIME_STATE);
sccb = env->regs[ipbh0 & 0xf];
code = env->regs[(ipbh0 & 0xf0) >> 4];
@@ -388,7 +388,7 @@ static int handle_priv(S390CPU *cpu, struct kvm_run *run, uint8_t ipa1)
static int handle_hypercall(CPUS390XState *env, struct kvm_run *run)
{
- cpu_synchronize_state(env, KVM_REGSYNC_FULL_STATE);
+ cpu_synchronize_state(env, KVM_REGSYNC_RUNTIME_STATE);
env->regs[2] = s390_virtio_hypercall(env, env->regs[2], env->regs[1]);
return 0;
@@ -463,7 +463,7 @@ static int handle_sigp(S390CPU *cpu, struct kvm_run *run, uint8_t ipa1)
S390CPU *target_cpu;
CPUS390XState *target_env;
- cpu_synchronize_state(env, KVM_REGSYNC_FULL_STATE);
+ cpu_synchronize_state(env, KVM_REGSYNC_RUNTIME_STATE);
/* get order code */
order_code = run->s390_sieic.ipb >> 28;
--
1.7.9.5
reply other threads:[~2013-01-10 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1357831767-4049-1-git-send-email-jjherne@us.ibm.com \
--to=jjherne@us.ibm.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.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).