From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Nick Lowe <nick.lowe@gmail.com>,
Hans-Peter Jansen <hpj@urpla.net>,
linux-kernel@vger.kernel.org
Subject: Re: AMD Geode NOPL emulation for kernel 2.6.36-rc2
Date: Wed, 08 Sep 2010 14:05:04 -0700 [thread overview]
Message-ID: <4C87FA80.9080100@zytor.com> (raw)
In-Reply-To: <20100908221144.73066e2d@lxorguk.ukuu.org.uk>
On 09/08/2010 02:11 PM, Alan Cox wrote:
>
> Getting the stuff right in the current kernel makes it easier to backport
> and fix and do tidily. It's not as if NOPL is complicated to emulate.
The execution phase is easy ;) The parsing phase is rather hard. This
is part of why I would much rather see a single x86 interpreter in the
kernel, and the one single interpreter that we need anyway is the one in
KVM.
I haven't looked at what it would take to generalize it to also support
trap and emulate of arbitrary instructions (not just NOPL and CMOV and
so on), but x86 is subtle and quick to anger, and doing it wrong can
trivially introduce security holes.
-hpa
next prev parent reply other threads:[~2010-09-08 21:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fmbxh-5N8-41@gated-at.bofh.it>
2010-09-07 15:57 ` AMD Geode NOPL emulation for kernel 2.6.36-rc2 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 [this message]
2010-09-08 21:07 ` Nick Lowe
2010-08-27 18:07 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
2010-08-29 13:39 ` Matteo Croce
2010-09-08 20:59 ` H. Peter Anvin
2010-08-27 20:54 ` H. Peter Anvin
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=4C87FA80.9080100@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hpj@urpla.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.lowe@gmail.com \
/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).