From: Avi Kivity <avi@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [RESEND][PATCH] x86: Enhanced dump of segment registers
Date: Thu, 12 Mar 2009 16:37:25 +0200 [thread overview]
Message-ID: <49B91E25.20102@redhat.com> (raw)
In-Reply-To: <49B7E760.2090100@siemens.com>
Jan Kiszka wrote:
>> Also I'm thinking the null descriptor doesn't need to show offset and
>> size:
>>
>> FS =0000
>>
>> is enough?
>>
>
> Yes, makes sense. IOW: stop parsing if selector == 0. Will post an update.
>
For gs and gs, base is meaningful even with null selectors (through
MSR_[FG]S_BASE or MSR_KERNEL_GS_BASE+swapgs).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-12 14:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 13:56 [Qemu-devel] [RESEND][PATCH] x86: Enhanced dump of segment registers Jan Kiszka
2009-03-11 16:10 ` Jamie Lokier
2009-03-11 16:31 ` [Qemu-devel] " Jan Kiszka
2009-03-11 16:40 ` Jamie Lokier
2009-03-11 19:18 ` malc
2009-03-11 19:24 ` Jan Kiszka
2009-03-12 14:37 ` Avi Kivity [this message]
2009-03-12 14:57 ` Jan Kiszka
2009-03-12 17:58 ` Jamie Lokier
2009-03-12 18:21 ` Jan Kiszka
2009-03-11 19:40 ` [Qemu-devel] [PATCH v2] " Jan Kiszka
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=49B91E25.20102@redhat.com \
--to=avi@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).