From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>,
Avi Kivity <avi@redhat.com>,
kvm-ppc@vger.kernel.org, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] [PATCH] qemu: ppc: kvm-userspace: KVM PowerPC support for qemu gdbstub
Date: Thu, 11 Dec 2008 12:31:14 -0600 [thread overview]
Message-ID: <1229020274.26586.24.camel@localhost.localdomain> (raw)
In-Reply-To: <49413A5A.8090008@siemens.com>
On Thu, 2008-12-11 at 17:05 +0100, Jan Kiszka wrote:
> Hollis Blanchard wrote:
> > On Thu, 2008-12-11 at 13:53 +0100, Christian Ehrhardt wrote:
> >> This is v2 as version one had a type in it occured when splitting patches.
> >> Mercurial somehow lost my changes to the patch description explaining
> >> that, but the patch is right this way.
> >>
> >> Christian Ehrhardt wrote:
> >>> # HG changeset patch
> >>> # User Christian Ehrhardt <ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> >>> # Date 1228999833 -3600
> >>> # Node ID dc1466c9077ab162f4637fffee1869f26be02299
> >>> # Parent 4c07fe2a56c7653a9113e05bb08c2de9aec210ce
> >>> [PATCH] qemu: ppc: kvm-userspace: KVM PowerPC support for qemu gdbstub
> >>>
> >>> From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> >>>
> >>> Add basic KVM PowerPC support to qemu's gdbstub introducing a kvm ppc style
> >>> mmu implementation that uses the kvm_translate ioctl.
> >>> This also requires to save the kvm registers prior to the 'm' gdb operations.
> >>>
> >>> Signed-off-by: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
> >>> Signed-off-by: Christian Ehrhardt <ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
> >
> > Let's *not* apply this to kvm-userspace. We will submit this to qemu,
> > and once we work out the right solution there it will be merged
> > naturally.
> >
>
> I don't oversee yet what you want to push upstream, but in case it's the
> gdbstub support for kvm (including ppc bits): please note that I plan to
> push the new interface once it is merged into kvm-userspace, avoiding to
> spread the current, limited one as far as possible.
>
> BTW, would be great if you could have a look / provide patches for ppc
> to support the new interface already. I am open for feedback,
> specifically regarding its suitability beyond x86.
I've been meaning to do this for a while, sorry. We'll take a look soon.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-12-11 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 12:52 [PATCH] [PATCH] qemu: ppc: kvm-userspace: KVM PowerPC support for qemu gdbstub Christian Ehrhardt
2008-12-11 12:53 ` Christian Ehrhardt
[not found] ` <49410D61.9090309-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-12-11 15:53 ` Hollis Blanchard
2008-12-11 16:05 ` Jan Kiszka
2008-12-11 18:31 ` Hollis Blanchard [this message]
[not found] ` <1229020274.26586.24.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-12-12 12:42 ` Christian Ehrhardt
[not found] ` <49425C2B.5040701-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-12-13 8:35 ` Jan Kiszka
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=1229020274.26586.24.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=avi@redhat.com \
--cc=ehrhardt@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.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