qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andreas Schultz <aschultz@warp10.net>,
	Paul Brook <paul@codesourcery.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long
Date: Sun, 04 Jan 2009 14:50:18 +0100	[thread overview]
Message-ID: <4960BE9A.3010603@web.de> (raw)
In-Reply-To: <20090103015307.GA1927@shareable.org>

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

Jamie Lokier wrote:
> Jan Kiszka wrote:
>> You need CR0.PE to detect if you are in real or protected mode. And then
>> you need GDTR/LDTR to find the descriptor CS is pointing at, parsing it
>> to detect if you are running 16, 32 or 64 bit code (by default). Those
>> extensions would also be useful in order to decode memory addresses in
>> case descriptor.base != 0 (or if it's CS >> 4, ie. you are in real
>> mode).
> 
> If you're going to decode segment descriptors (great idea, btw, and
> helpful for threaded code), it might be better to supply the CPU's
> internal segment state, if that's possible, instead of looking at the
> LDT/GDT in memory, since the CPU's state can differ from the memory
> version when the latter is written to.

Good point. I included this in an initial suggestion of an extended
register set, see [1]. Providing this information will likely remain
VM-business, but that doesn't mean we shouldn't use it when available.

Jan

[1] http://sourceware.org/ml/gdb/2009-01/msg00008.html


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-01-04 13:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1229776952.22890.2.camel@ws-aschultz>
2008-12-20 15:49 ` [Qemu-devel] Re: gdbstub: packet reply is too long Jan Kiszka
2008-12-20 20:35   ` Paul Brook
2008-12-20 21:00     ` Jan Kiszka
2008-12-20 21:03       ` Paul Brook
2008-12-20 21:22         ` Jan Kiszka
2008-12-20 21:34           ` Paul Brook
2008-12-20 21:55             ` Jan Kiszka
2008-12-20 22:08               ` Paul Brook
2008-12-20 22:34                 ` Jan Kiszka
2008-12-20 22:46                   ` Paul Brook
2008-12-20 23:44                     ` Jan Kiszka
2008-12-26 23:30                       ` Daniel Jacobowitz
2008-12-29 14:58                         ` Jan Kiszka
2008-12-30 22:43                           ` Daniel Jacobowitz
2009-01-02 12:53                             ` Jan Kiszka
2009-01-03  1:53                               ` Jamie Lokier
2009-01-04 13:50                                 ` Jan Kiszka [this message]

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=4960BE9A.3010603@web.de \
    --to=jan.kiszka@web.de \
    --cc=aschultz@warp10.net \
    --cc=jamie@shareable.org \
    --cc=kvm@vger.kernel.org \
    --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 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).