qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: Abhishek Saksena <abhishek.saksena@intel.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] gdbstub: x86: Switch 64/32 bit registers dynamically
Date: Thu, 17 Sep 2009 18:38:02 +0200	[thread overview]
Message-ID: <4AB265EA.9060109@siemens.com> (raw)
In-Reply-To: <4AB26055.2060506@siemens.com>

Jan Kiszka wrote:
> Commit 56aebc891674cd2d07b3f64183415697be200084 changed gdbstub in way
> that debugging 32 or 16-bit guest code is no longer possible with qemu
> for x86_64 guest CPUs. Since that commit, qemu only provides registers
> sets for 64-bit, forcing current and foreseeable gdb to also switch its
> architecture to 64-bit. And this breaks if the inferior is 32 or 16 bit.
> 
> No question, this is a gdb issue. But, as it was confirmed in several
> discusssions with gdb people, it is a non-trivial thing to fix. So until
> qemu finds a gdb version attach with a rework x86 support, we have to
> work around it by switching the register layout as the guest switches
> its execution mode between 16/32 and 64 bit.
> 
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> Sent to qemu-kvm for inclusion on Avi's request as this workaround is
> still disliked upstream.

Sorry, mistyped the list address.

Jan

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

  reply	other threads:[~2009-09-17 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 16:14 [Qemu-devel] [PATCH] gdbstub: x86: Switch 64/32 bit registers dynamically Jan Kiszka
2009-09-17 16:38 ` Jan Kiszka [this message]
2009-11-10 13:35 ` Paul Brook

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=4AB265EA.9060109@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=abhishek.saksena@intel.com \
    --cc=avi@redhat.com \
    --cc=mtosatti@redhat.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 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).