kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Avi Kivity <avi@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>
Subject: Re: [PATCH] KVM: Qemu: Build fix for !CONFIG_GDBSTUB case.
Date: Thu, 27 Nov 2008 11:31:02 +0100	[thread overview]
Message-ID: <492E76E6.8060004@siemens.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC219BCA9F2@pdsmsx503.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> From ee96ecb2c86e820278f3332d32a452f31c72dc30 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Thu, 27 Nov 2008 17:23:27 +0800
> Subject: [PATCH] KVM: Qemu: Build fix for !CONFIG_GDBSTUB case.
> 
> Once CONFIG_GDBSTUB not configured, compile will generate error.
> 
> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> ---
>  qemu/vl.c |    2 ++
>  1 files changed, 2 insertions(+), 0 deletions(-)
> 
> diff --git a/qemu/vl.c b/qemu/vl.c
> index 92325e6..46733e9 100644
> --- a/qemu/vl.c
> +++ b/qemu/vl.c
> @@ -3862,10 +3862,12 @@ static int main_loop(void)
>  		qemu_system_powerdown();
>                  ret = EXCP_INTERRUPT;
>              }
> +#ifdef CONFIG_GDBSTUB
>              if (unlikely(ret == EXCP_DEBUG)) {
>                  gdb_set_stop_cpu(cur_cpu);
>                  vm_stop(EXCP_DEBUG);
>              }
> +#endif
>              /* If all cpus are halted then wait until the next IRQ */
>              /* XXX: use timeout computed from timers */
>              if (ret == EXCP_HALTED) {

This rather looks like a qemu upstream issue. But as no qemu arch comes
without gdbstub support and this switch is always true, no one noticed it.

But why not fixing the core issue, ie. adding gdbstub support, or at
least some intermediate dummy functions until qemu gains full ia64
support? That would also allow to clean up the CONFIG_GDBSTUB #ifdef'ery
from upstream. And it would be the first step towards kvm guest
debugging support for ia64.

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2 ES-OS
Corporate Competence Center Embedded Linux

  reply	other threads:[~2008-11-27 10:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27  9:35 [PATCH] KVM: Qemu: Build fix for !CONFIG_GDBSTUB case Zhang, Xiantao
2008-11-27 10:31 ` Jan Kiszka [this message]
2008-11-28  1:25   ` Zhang, Xiantao

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=492E76E6.8060004@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm-ia64@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=xiantao.zhang@intel.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;
as well as URLs for NNTP newsgroup(s).