From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Mark McLoughlin <markmc@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 12:03:33 -0500 [thread overview]
Message-ID: <4A577465.1050104@us.ibm.com> (raw)
In-Reply-To: <4A5771C3.7050103@siemens.com>
Jan Kiszka wrote:
> Something went wrong during transmission, and I missed that. Just sent
> out those two as well.
>
Thanks, it's now all in staging.
> That's nothing those patches changes (it's our current and only
> debugging model for SMP until gdb provides a complete solution).
>
It Paul agrees, I'll pull it. But my understanding from the previous
threads and posts was that Paul did not want to implement vCont even as
a stop-gap and that he preferred to fix gdb properly.
> The recent discussion went around how to deal with some other gdb
> limitation: debugging targets that run in x86's 16/32 bit mode vs. the
> target arch being advertised as 64 bit. Existing qemu code doesn't work
> with existing gdb in this scenario, and the question was how to deal
> with it until gdb is improved.
>
Right, that part I'm okay with. But the vCont based gdb model presumes
a unified address space which while usually true for kernel address
spaces, isn't universally true and certainly not true when PC is in
userspace. That's what I understood to be the major objection to vCont.
>> I'm not qualified to
>> appreciate the difference so I'm inclined to side with Paul. Am I
>> missing something there?
>>
>
> I interpreted [1] as that the rest is OK for Paul.
>
Paul, can you clarify?
--
Regards,
Anthony Liguori
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
Paul Brook <paul@codesourcery.com>,
Markus Armbruster <armbru@redhat.com>,
kvm-devel <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 12:03:33 -0500 [thread overview]
Message-ID: <4A577465.1050104@us.ibm.com> (raw)
In-Reply-To: <4A5771C3.7050103@siemens.com>
Jan Kiszka wrote:
> Something went wrong during transmission, and I missed that. Just sent
> out those two as well.
>
Thanks, it's now all in staging.
> That's nothing those patches changes (it's our current and only
> debugging model for SMP until gdb provides a complete solution).
>
It Paul agrees, I'll pull it. But my understanding from the previous
threads and posts was that Paul did not want to implement vCont even as
a stop-gap and that he preferred to fix gdb properly.
> The recent discussion went around how to deal with some other gdb
> limitation: debugging targets that run in x86's 16/32 bit mode vs. the
> target arch being advertised as 64 bit. Existing qemu code doesn't work
> with existing gdb in this scenario, and the question was how to deal
> with it until gdb is improved.
>
Right, that part I'm okay with. But the vCont based gdb model presumes
a unified address space which while usually true for kernel address
spaces, isn't universally true and certainly not true when PC is in
userspace. That's what I understood to be the major objection to vCont.
>> I'm not qualified to
>> appreciate the difference so I'm inclined to side with Paul. Am I
>> missing something there?
>>
>
> I interpreted [1] as that the rest is OK for Paul.
>
Paul, can you clarify?
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-10 17:04 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 23:57 Planning for the 0.11.0 release Anthony Liguori
2009-06-22 23:57 ` [Qemu-devel] " Anthony Liguori
2009-06-23 12:12 ` Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47 ` Anthony Liguori
2009-06-23 15:49 ` Avi Kivity
2009-07-09 8:27 ` Mark McLoughlin
2009-07-09 13:32 ` Anthony Liguori
2009-07-10 1:10 ` Markus Armbruster
2009-07-10 1:10 ` Markus Armbruster
2009-07-10 13:53 ` Anthony Liguori
2009-07-10 15:04 ` Jan Kiszka
2009-07-10 15:04 ` Jan Kiszka
2009-07-10 15:49 ` Anthony Liguori
2009-07-10 15:49 ` Anthony Liguori
2009-07-10 16:23 ` Jan Kiszka
2009-07-10 16:23 ` Jan Kiszka
2009-07-10 16:33 ` Anthony Liguori
2009-07-10 16:33 ` Anthony Liguori
2009-07-10 16:52 ` Jan Kiszka
2009-07-10 16:52 ` Jan Kiszka
2009-07-10 17:03 ` Anthony Liguori [this message]
2009-07-10 17:03 ` Anthony Liguori
2009-07-10 17:15 ` Jan Kiszka
2009-07-10 17:15 ` Jan Kiszka
2009-07-10 17:40 ` Paul Brook
2009-07-10 17:40 ` Paul Brook
2009-07-10 17:58 ` Anthony Liguori
2009-07-10 17:58 ` Anthony Liguori
2009-07-10 18:02 ` Jan Kiszka
2009-07-10 18:02 ` Jan Kiszka
2009-07-10 18:22 ` Paul Brook
2009-07-10 18:22 ` Paul Brook
2009-07-10 16:55 ` Kevin Wolf
2009-07-10 16:59 ` Anthony Liguori
2009-07-10 17:10 ` Kevin Wolf
2009-07-10 17:31 ` Anthony Liguori
2009-07-10 17:10 ` Christoph Hellwig
2009-07-10 17:12 ` Kevin Wolf
2009-07-10 17:12 ` Kevin Wolf
2009-07-10 18:26 ` Christoph Hellwig
2009-07-10 18:26 ` Christoph Hellwig
2009-07-10 17:29 ` Anthony Liguori
2009-07-10 18:13 ` Christoph Hellwig
2009-07-10 18:13 ` Christoph Hellwig
2009-07-10 18:29 ` Anthony Liguori
2009-07-10 17:06 ` Anthony Liguori
2009-07-12 8:31 ` Avi Kivity
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=4A577465.1050104@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=paul@codesourcery.com \
--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 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.