From: "Igor Kovalenko" <igor.v.kovalenko@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] handle multibyte NOPs
Date: Mon, 21 Aug 2006 02:47:41 +0400 [thread overview]
Message-ID: <b2fa41d60608201547w60fcc44bn8c3fa5e3fb737c11@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0608210237060.12156@home.oyster.ru>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
On 8/21/06, malc <malc@pulsesoft.com> wrote:
>
> On Mon, 21 Aug 2006, Igor Kovalenko wrote:
>
> <snip>
>
> > Right. Here is the real one with correct case labels.
>
> Sorry, forgot to mention that atop of the hex/bin problem the code also
> suffers from lack of proper 16/64 bit modrm decoding.
seems to me that 16 and 64 bit cases does not apply here
--
Kind Regards,
Igor V. Kovalenko
[-- Attachment #2: Type: text/html, Size: 696 bytes --]
next prev parent reply other threads:[~2006-08-20 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 23:40 [Qemu-devel] [PATCH] handle multibyte NOPs Igor Kovalenko
2006-08-19 0:28 ` Paul Brook
2006-08-20 21:51 ` Igor Kovalenko
2006-08-20 22:15 ` malc
2006-08-20 22:28 ` Igor Kovalenko
2006-08-20 22:39 ` malc
2006-08-20 22:47 ` Igor Kovalenko [this message]
2006-08-20 23:18 ` malc
2006-08-30 19:27 ` Igor Kovalenko
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=b2fa41d60608201547w60fcc44bn8c3fa5e3fb737c11@mail.gmail.com \
--to=igor.v.kovalenko@gmail.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).