From: Avi Kivity <avi@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Sergio Luis <eeeesti@gmail.com>, Ingo Molnar <mingo@elte.hu>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Pavel Machek <pavel@suse.cz>,
Linux-kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86: asm doubt
Date: Mon, 16 Mar 2009 16:12:30 +0200 [thread overview]
Message-ID: <49BE5E4E.1070209@redhat.com> (raw)
In-Reply-To: <49BD2FC7.5050903@goop.org>
Jeremy Fitzhardinge wrote:
> In 32-bit mode, moving to a segment register can fault if the
> underlying GDT/LDT entry is invalid. In 64-bit mode, segment
> registers are mostly decorative and have no function, and moving
> arbitrary values into them doesn't fault, making the exception
> catching unnecessary.
64-bit mode will in fact fault if an access is made outside the GDT/LDT,
or of the descriptor is invalid.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-03-16 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 14:16 x86: asm doubt Sergio Luis
2009-03-15 16:41 ` Jeremy Fitzhardinge
2009-03-16 13:12 ` Sergio Luis
2009-03-16 14:12 ` Avi Kivity [this message]
2009-03-16 16:20 ` Jeremy Fitzhardinge
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=49BE5E4E.1070209@redhat.com \
--to=avi@redhat.com \
--cc=eeeesti@gmail.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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