From: Jes Sorensen <jes@sgi.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [patch] fix qemu-kvm to build when gdbstub is disabled
Date: Thu, 07 May 2009 15:31:59 +0200 [thread overview]
Message-ID: <4A02E2CF.2080105@sgi.com> (raw)
In-Reply-To: <4A02DD02.8020705@siemens.com>
Jan Kiszka wrote:
> I'm not asking for full gdbstub support at this point, just for a build
> workaround at arch-level (or in arch-specific blocks, in gdbstub.c e.g.)
> instead of patching generic code with global risk of regressions.
Oh, I see.
I already submitted that to Avi, making gdb_set_stop_cpu() a noop on
ia64. Since there's no target-ia64/ directory in mainline qemu.git yet,
that fix will have to live in qemu-kvm for the time being.
I am fine if you wish to remove all the #ifdef CONFIG_GDBSTUB bits.
Cheers,
Jes
prev parent reply other threads:[~2009-05-07 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A01AFE8.3020008@sgi.com>
[not found] ` <706158FABBBA044BAD4FE898A02E4BC236AC6F59@pdsmsx503.ccr.corp.intel.com>
[not found] ` <4A02AA81.90809@redhat.com>
2009-05-07 10:51 ` [Qemu-devel] Re: [patch] fix qemu-kvm to build when gdbstub is disabled Jan Kiszka
2009-05-07 11:00 ` Avi Kivity
2009-05-07 11:13 ` Jan Kiszka
2009-05-07 11:28 ` Avi Kivity
2009-05-07 11:38 ` Jan Kiszka
2009-05-07 12:34 ` Jes Sorensen
2009-05-07 12:59 ` Jan Kiszka
2009-05-07 13:03 ` Jes Sorensen
2009-05-07 13:07 ` Jan Kiszka
2009-05-07 13:31 ` Jes Sorensen [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=4A02E2CF.2080105@sgi.com \
--to=jes@sgi.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm-ia64@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--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).