From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matteo Croce <matteo@openwrt.org>,
Thomas Backlund <tmb@mandriva.org>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Natale Vinto <ebballon@gmail.com>
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2
Date: Sun, 29 Aug 2010 15:52:49 +0300 [thread overview]
Message-ID: <4C7A5821.3010007@redhat.com> (raw)
In-Reply-To: <4C784544.2010305@zytor.com>
On 08/28/2010 02:07 AM, H. Peter Anvin wrote:
> On 08/27/2010 02:32 PM, Matteo Croce wrote:
>> can I ignore the return value when I expect val to be non zero?
>> the doc says: "On error, the variable @x is set to zero."
> No. You need to deliver a page fault to the application in this case.
>
> The *real* test for this kind of crap is correct page fault behavior,
> and so forth.
>
> Also, at the very least you need to check for:
>
> - CS == USER_CS
Is that mandated by the ABI? Is it illegal for an application to load a
segment with a nonzero base into the LDT and use it for CS?
What about vm86?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-29 12:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 18:07 AMD Geode NOPL emulation for kernel 2.6.36-rc2 Matteo Croce
2010-08-27 18:48 ` H. Peter Anvin
2010-08-27 20:15 ` Matteo Croce
2010-08-27 20:49 ` Thomas Backlund
2010-08-27 21:32 ` Matteo Croce
2010-08-27 22:16 ` Matteo Croce
2010-08-27 22:19 ` Matteo Croce
2010-08-27 23:07 ` H. Peter Anvin
2010-08-29 12:52 ` Avi Kivity [this message]
2010-08-29 13:39 ` Matteo Croce
2010-09-08 20:59 ` H. Peter Anvin
2010-08-27 20:54 ` H. Peter Anvin
[not found] <fmbxh-5N8-41@gated-at.bofh.it>
2010-09-07 15:57 ` Nick Lowe
2010-09-08 9:15 ` Hans-Peter Jansen
2010-09-08 11:34 ` Nick Lowe
2010-09-08 11:55 ` Nick Lowe
2010-09-08 17:56 ` Alan Cox
2010-09-08 17:51 ` Nick Lowe
2010-09-08 19:07 ` Alan Cox
2010-09-08 19:44 ` Nick Lowe
2010-09-08 21:11 ` Alan Cox
2010-09-08 21:05 ` H. Peter Anvin
2010-09-08 21:07 ` Nick Lowe
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=4C7A5821.3010007@redhat.com \
--to=avi@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ebballon@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo@openwrt.org \
--cc=tmb@mandriva.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.