From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [patch] fix qemu-kvm to build when gdbstub is disabled
Date: Thu, 07 May 2009 13:07:14 +0000 [thread overview]
Message-ID: <4A02DD02.8020705@siemens.com> (raw)
In-Reply-To: <4A01AFE8.3020008@sgi.com>
Jes Sorensen wrote:
> Jan Kiszka wrote:
>> As the original change this patch (correctly) fixes broke gdbstub
>> support in qemu-kvm for all archs + it is still a deviation from
>> upstream, please take the chance and go for ia64 stubs.
>
> Jan,
>
> There's far more to do in upstream than just gdbstubs for ia64 to be
> usable :-(
>
> We'll get to gdbstubs at some point, but there's too many other higher
> priority items to deal with first.
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.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jes Sorensen <jes@sgi.com>
Cc: Avi Kivity <avi@redhat.com>,
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 15:07:14 +0200 [thread overview]
Message-ID: <4A02DD02.8020705@siemens.com> (raw)
In-Reply-To: <4A02DC14.9010507@sgi.com>
Jes Sorensen wrote:
> Jan Kiszka wrote:
>> As the original change this patch (correctly) fixes broke gdbstub
>> support in qemu-kvm for all archs + it is still a deviation from
>> upstream, please take the chance and go for ia64 stubs.
>
> Jan,
>
> There's far more to do in upstream than just gdbstubs for ia64 to be
> usable :-(
>
> We'll get to gdbstubs at some point, but there's too many other higher
> priority items to deal with first.
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.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jes Sorensen <jes@sgi.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:07:14 +0200 [thread overview]
Message-ID: <4A02DD02.8020705@siemens.com> (raw)
In-Reply-To: <4A02DC14.9010507@sgi.com>
Jes Sorensen wrote:
> Jan Kiszka wrote:
>> As the original change this patch (correctly) fixes broke gdbstub
>> support in qemu-kvm for all archs + it is still a deviation from
>> upstream, please take the chance and go for ia64 stubs.
>
> Jan,
>
> There's far more to do in upstream than just gdbstubs for ia64 to be
> usable :-(
>
> We'll get to gdbstubs at some point, but there's too many other higher
> priority items to deal with first.
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.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-05-07 13:07 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
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 [this message]
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=4A02DD02.8020705@siemens.com \
--to=jan.kiszka@siemens.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.