All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
	Mark McLoughlin <markmc@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 20:02:03 +0200	[thread overview]
Message-ID: <4A57821B.9010706@siemens.com> (raw)
In-Reply-To: <200907101840.55859.paul@codesourcery.com>

Paul Brook wrote:
> The 32/64-bit switching is just plain wrong, and makes it absolutely 
> impossible for a client debugger to work correctly.

As pointed out before, it doesn't break anything but adds a workaround
for scenarios which are _now_ broken (16/32 bit target code exported as
64 bit is widely useless for gdb today). Sorry, but you never explained
to me how user are _currently_ supposed to debug under that conditions,
namely 16/32 bit code executed by qemu-system-x86_64.

> If you really can't be bothered fixing gdb (and you *really* should), then it 

I do bother, but it's nothing for a long rainy afternoon.

> should be some form of user switch that tells qemu to always report a 32-bit 
> register set.

I could offer to add a monitor command so that one can additionally
set/override the register representation during runtime that way. I do
not see a use case for it based on all the scenarios I'm aware of or
personally ran through the last year, but if it helps acceptance.
However, only a command line switch locking down the mode would solve
just half of the real-world problems.

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: Paul Brook <paul@codesourcery.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 20:02:03 +0200	[thread overview]
Message-ID: <4A57821B.9010706@siemens.com> (raw)
In-Reply-To: <200907101840.55859.paul@codesourcery.com>

Paul Brook wrote:
> The 32/64-bit switching is just plain wrong, and makes it absolutely 
> impossible for a client debugger to work correctly.

As pointed out before, it doesn't break anything but adds a workaround
for scenarios which are _now_ broken (16/32 bit target code exported as
64 bit is widely useless for gdb today). Sorry, but you never explained
to me how user are _currently_ supposed to debug under that conditions,
namely 16/32 bit code executed by qemu-system-x86_64.

> If you really can't be bothered fixing gdb (and you *really* should), then it 

I do bother, but it's nothing for a long rainy afternoon.

> should be some form of user switch that tells qemu to always report a 32-bit 
> register set.

I could offer to add a monitor command so that one can additionally
set/override the register representation during runtime that way. I do
not see a use case for it based on all the scenarios I'm aware of or
personally ran through the last year, but if it helps acceptance.
However, only a command line switch locking down the mode would solve
just half of the real-world problems.

Jan

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

  parent reply	other threads:[~2009-07-10 18:02 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
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 [this message]
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=4A57821B.9010706@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.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.