From: Alexander Graf <agraf@suse.de>
To: Bharat Bhushan <Bharat.Bhushan@freescale.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org, scottwood@freescale.com, stuart.yoder@freescale.com
Subject: Re: [PATCH 0/7 v3] Guest debug emulation
Date: Tue, 12 Aug 2014 12:25:11 +0200 [thread overview]
Message-ID: <53E9EB87.8090502@suse.de> (raw)
In-Reply-To: <1407307137-5083-1-git-send-email-Bharat.Bhushan@freescale.com>
On 06.08.14 08:38, Bharat Bhushan wrote:
> This patchset adds debug register and interrupt emulation
> support for guest, which enables running gdb/kgdb etc in guest.
>
> v2->v3
> - Added One-reg interface for DBSR
> - removed arch->shadow_dbg_reg
> - Addressed some more comments on v2 (detail in individual patch)
Thanks, applied patches 1-6 to kvm-ppc-queue. That way you only need to
respin patch 7 and add the documentation patch.
Alex
next prev parent reply other threads:[~2014-08-12 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 6:38 [PATCH 0/7 v3] Guest debug emulation Bharat Bhushan
2014-08-06 6:38 ` [PATCH 1/7 v3] KVM: PPC: BOOKE: allow debug interrupt at "debug level" Bharat Bhushan
2014-08-06 6:38 ` [PATCH 2/7 v3] KVM: PPC: BOOKE : Emulate rfdi instruction Bharat Bhushan
2014-08-06 6:38 ` [PATCH 3/7 v3] KVM: PPC: BOOKE: Allow guest to change MSR_DE Bharat Bhushan
2014-08-06 6:38 ` [PATCH 4/7 v3] KVM: PPC: BOOKE: Clear guest dbsr in userspace exit KVM_EXIT_DEBUG Bharat Bhushan
2014-08-06 6:38 ` [PATCH 5/7 v3] KVM: PPC: BOOKE: Guest and hardware visible debug registers are same Bharat Bhushan
2014-08-06 6:38 ` [PATCH 6/7 v3] KVM: PPC: BOOKE: Add one reg interface for DBSR Bharat Bhushan
2014-08-12 10:24 ` Alexander Graf
2014-08-06 6:38 ` [PATCH 7/7 v3] KVM: PPC: BOOKE: Emulate debug registers and exception Bharat Bhushan
2014-08-12 0:00 ` Scott Wood
2014-08-12 7:36 ` Bharat.Bhushan
2014-08-12 19:46 ` Scott Wood
2014-08-12 10:25 ` Alexander Graf [this message]
2014-08-12 10:27 ` [PATCH 0/7 v3] Guest debug emulation Bharat.Bhushan
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=53E9EB87.8090502@suse.de \
--to=agraf@suse.de \
--cc=Bharat.Bhushan@freescale.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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