All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] fix qemu-kvm to build when gdbstub is disabled
Date: Thu, 07 May 2009 12:34:01 +0000	[thread overview]
Message-ID: <4A02D539.6040705@sgi.com> (raw)
In-Reply-To: <4A01AFE8.3020008@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

Avi Kivity wrote:
> I agree, unless
> 
> - we want to make gdbstub support configurable (don't see any 
> overwhelming reason for this, but maybe others do)
> - we want to merge ia64 kvm support upstream, and don't want to impose 
> gdbstub support (though I'd recommend properly implementing gdbstub)
> 
> In any case, I'm okay with dropping the check upstream and applying the 
> local fixup.

Hi,

Here's a patch that fixes the #ifndef to make it the #ifdef as it was
intended.

I am quite fine with us trying to drop all the #ifdefs and introduce
noop wrappers for archs that do not provide the gdbstubs (ie. ia64), but
to start with we better just fix the #ifndef to make it behave like it
was originally intended.

Cheers,
Jes




[-- Attachment #2: 0001-qemu-kdbstub.patch --]
[-- Type: text/x-patch, Size: 560 bytes --]

Fix incorrect #ifndef for CONFIG_GETSTUB, which should have been an
#ifdef.

Signed-off-by: Jes Sorensen <jes@sgi.com>

---
 vl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: qemu/vl.c
===================================================================
--- qemu.orig/vl.c
+++ qemu/vl.c
@@ -4350,7 +4350,7 @@
         }
         if (cpu_can_run(env))
             ret = qemu_cpu_exec(env);
-#ifndef CONFIG_GDBSTUB
+#ifdef CONFIG_GDBSTUB
         if (ret == EXCP_DEBUG) {
             gdb_set_stop_cpu(env);
             debug_requested = 1;

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <jes@sgi.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>,
	"kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [patch] fix qemu-kvm to build when gdbstub is disabled
Date: Thu, 07 May 2009 14:34:01 +0200	[thread overview]
Message-ID: <4A02D539.6040705@sgi.com> (raw)
In-Reply-To: <4A02BF59.6030103@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

Avi Kivity wrote:
> I agree, unless
> 
> - we want to make gdbstub support configurable (don't see any 
> overwhelming reason for this, but maybe others do)
> - we want to merge ia64 kvm support upstream, and don't want to impose 
> gdbstub support (though I'd recommend properly implementing gdbstub)
> 
> In any case, I'm okay with dropping the check upstream and applying the 
> local fixup.

Hi,

Here's a patch that fixes the #ifndef to make it the #ifdef as it was
intended.

I am quite fine with us trying to drop all the #ifdefs and introduce
noop wrappers for archs that do not provide the gdbstubs (ie. ia64), but
to start with we better just fix the #ifndef to make it behave like it
was originally intended.

Cheers,
Jes




[-- Attachment #2: 0001-qemu-kdbstub.patch --]
[-- Type: text/x-patch, Size: 560 bytes --]

Fix incorrect #ifndef for CONFIG_GETSTUB, which should have been an
#ifdef.

Signed-off-by: Jes Sorensen <jes@sgi.com>

---
 vl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: qemu/vl.c
===================================================================
--- qemu.orig/vl.c
+++ qemu/vl.c
@@ -4350,7 +4350,7 @@
         }
         if (cpu_can_run(env))
             ret = qemu_cpu_exec(env);
-#ifndef CONFIG_GDBSTUB
+#ifdef CONFIG_GDBSTUB
         if (ret == EXCP_DEBUG) {
             gdb_set_stop_cpu(env);
             debug_requested = 1;

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <jes@sgi.com>
To: Avi Kivity <avi@redhat.com>
Cc: "kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [patch] fix qemu-kvm to build when gdbstub is disabled
Date: Thu, 07 May 2009 14:34:01 +0200	[thread overview]
Message-ID: <4A02D539.6040705@sgi.com> (raw)
In-Reply-To: <4A02BF59.6030103@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

Avi Kivity wrote:
> I agree, unless
> 
> - we want to make gdbstub support configurable (don't see any 
> overwhelming reason for this, but maybe others do)
> - we want to merge ia64 kvm support upstream, and don't want to impose 
> gdbstub support (though I'd recommend properly implementing gdbstub)
> 
> In any case, I'm okay with dropping the check upstream and applying the 
> local fixup.

Hi,

Here's a patch that fixes the #ifndef to make it the #ifdef as it was
intended.

I am quite fine with us trying to drop all the #ifdefs and introduce
noop wrappers for archs that do not provide the gdbstubs (ie. ia64), but
to start with we better just fix the #ifndef to make it behave like it
was originally intended.

Cheers,
Jes




[-- Attachment #2: 0001-qemu-kdbstub.patch --]
[-- Type: text/x-patch, Size: 560 bytes --]

Fix incorrect #ifndef for CONFIG_GETSTUB, which should have been an
#ifdef.

Signed-off-by: Jes Sorensen <jes@sgi.com>

---
 vl.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: qemu/vl.c
===================================================================
--- qemu.orig/vl.c
+++ qemu/vl.c
@@ -4350,7 +4350,7 @@
         }
         if (cpu_can_run(env))
             ret = qemu_cpu_exec(env);
-#ifndef CONFIG_GDBSTUB
+#ifdef CONFIG_GDBSTUB
         if (ret == EXCP_DEBUG) {
             gdb_set_stop_cpu(env);
             debug_requested = 1;

  parent reply	other threads:[~2009-05-07 12:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 15:42 [patch] fix qemu-kvm to build when gdbstub is disabled Jes Sorensen
2009-05-06 15:42 ` Jes Sorensen
2009-05-07  1:24 ` Zhang, Xiantao
2009-05-07  1:24   ` Zhang, Xiantao
2009-05-07  8:14 ` Jes Sorensen
2009-05-07  8:14   ` Jes Sorensen
2009-05-07  9:31 ` Avi Kivity
2009-05-07  9:31   ` Avi Kivity
2009-05-07  9:50 ` Zhang, Xiantao
2009-05-07  9:50   ` Zhang, Xiantao
2009-05-07  9:59 ` Avi Kivity
2009-05-07  9:59   ` Avi Kivity
2009-05-07 10:51 ` Jan Kiszka
2009-05-07 10:51   ` [Qemu-devel] " Jan Kiszka
2009-05-07 10:51   ` Jan Kiszka
2009-05-07 11:00 ` Avi Kivity
2009-05-07 11:00   ` [Qemu-devel] " Avi Kivity
2009-05-07 11:00   ` Avi Kivity
2009-05-07 11:13 ` Jan Kiszka
2009-05-07 11:13   ` [Qemu-devel] " Jan Kiszka
2009-05-07 11:13   ` Jan Kiszka
2009-05-07 11:28 ` Avi Kivity
2009-05-07 11:28   ` [Qemu-devel] " Avi Kivity
2009-05-07 11:28   ` Avi Kivity
2009-05-07 11:38 ` Jan Kiszka
2009-05-07 11:38   ` [Qemu-devel] " Jan Kiszka
2009-05-07 11:38   ` Jan Kiszka
2009-05-07 12:34 ` Jes Sorensen [this message]
2009-05-07 12:34   ` [Qemu-devel] " Jes Sorensen
2009-05-07 12:34   ` Jes Sorensen
2009-05-07 12:59 ` Jan Kiszka
2009-05-07 12:59   ` [Qemu-devel] " Jan Kiszka
2009-05-07 12:59   ` Jan Kiszka
2009-05-07 13:03 ` Jes Sorensen
2009-05-07 13:03   ` [Qemu-devel] " Jes Sorensen
2009-05-07 13:03   ` Jes Sorensen
2009-05-07 13:07 ` Jan Kiszka
2009-05-07 13:07   ` [Qemu-devel] " Jan Kiszka
2009-05-07 13:07   ` Jan Kiszka
2009-05-07 13:31 ` Jes Sorensen
2009-05-07 13:31   ` [Qemu-devel] " Jes Sorensen
2009-05-07 13:31   ` Jes Sorensen

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=4A02D539.6040705@sgi.com \
    --to=jes@sgi.com \
    --cc=kvm-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.