From: Bharat Bhushan <Bharat.Bhushan@freescale.com>
To: agraf@suse.de
Cc: Bharat Bhushan <Bharat.Bhushan@freescale.com>,
maddy@linux.vnet.ibm.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/5 v4] ppc: debug stub: Get trap instruction opcode from KVM
Date: Thu, 26 Jun 2014 10:41:29 +0530 [thread overview]
Message-ID: <1403759489-14990-6-git-send-email-Bharat.Bhushan@freescale.com> (raw)
In-Reply-To: <1403759489-14990-1-git-send-email-Bharat.Bhushan@freescale.com>
Get trap instruction opcode from KVM and this opcode will
be used for setting software breakpoint in following patch
Signed-off-by: Bharat Bhushan <Bharat.Bhushan@freescale.com>
---
v3->v4:
- No Change
target-ppc/kvm.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index dfa5a26..1f78cd1 100644
--- a/target-ppc/kvm.c
+++ b/target-ppc/kvm.c
@@ -71,6 +71,8 @@ static int cap_papr;
static int cap_htab_fd;
static int cap_fixup_hcalls;
+static uint32_t debug_inst_opcode;
+
/* XXX We have a race condition where we actually have a level triggered
* interrupt, but the infrastructure can't expose that yet, so the guest
* takes but ignores it, goes to sleep and never gets notified that there's
@@ -434,6 +436,8 @@ int kvm_arch_init_vcpu(CPUState *cs)
break;
}
+ kvm_get_one_reg(cs, KVM_REG_PPC_DEBUG_INST, &debug_inst_opcode);
+
return ret;
}
--
1.9.0
prev parent reply other threads:[~2014-06-26 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 5:11 [Qemu-devel] [PATCH 0/5 v4] ppc: Add debug stub support Bharat Bhushan
2014-06-26 5:11 ` [Qemu-devel] [PATCH 5/5 v4] ppc: Add hw breakpoint watchpoint support Bharat Bhushan
2014-06-26 5:11 ` [Qemu-devel] [PATCH 4/5 v4] ppc: Add software breakpoint support Bharat Bhushan
2014-06-26 5:11 ` [Qemu-devel] [PATCH 3/5 v4] ppc: Add debug interrupt injection handler Bharat Bhushan
2014-06-26 5:11 ` [Qemu-devel] [PATCH 2/5 v4] ppc: Add interface to inject interrupt to guest Bharat Bhushan
2014-06-26 5:11 ` Bharat Bhushan [this message]
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=1403759489-14990-6-git-send-email-Bharat.Bhushan@freescale.com \
--to=bharat.bhushan@freescale.com \
--cc=agraf@suse.de \
--cc=maddy@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).