From: Keir Fraser <keir@xen.org>
To: David Vrabel <david.vrabel@citrix.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86: emulate lea with two register operands correctly
Date: Thu, 05 Jan 2012 15:49:55 +0000 [thread overview]
Message-ID: <CB2B7723.36EB2%keir@xen.org> (raw)
In-Reply-To: <e25b7798f13ba47f5325.1325775781@qabil.uk.xensource.com>
On 05/01/2012 15:03, "David Vrabel" <david.vrabel@citrix.com> wrote:
> An lea instruction with two register operands should raise an
> undefined instruction exception.
>
> Skype does such a instruction and will crash when starting if it does
> not get the exception.
Thanks. I think it is a little nicer to check ea.type != OP_MEM, so I made
that change before committing this patch. It's now in xen-unstable staging.
It's a bit concerning that we're emulating LEA at all, perhaps. I wonder if
a pagetable page has been reused as a code page and we didn't notice yet? Or
is there some other reason that skype is getting emulated? :-)
-- Keir
> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
>
> diff -r efaa28639a71 -r e25b7798f13b xen/arch/x86/x86_emulate/x86_emulate.c
> --- a/xen/arch/x86/x86_emulate/x86_emulate.c Wed Jan 04 16:12:44 2012 +0000
> +++ b/xen/arch/x86/x86_emulate/x86_emulate.c Thu Jan 05 14:58:56 2012 +0000
> @@ -2240,6 +2240,7 @@ x86_emulate(
> }
>
> case 0x8d: /* lea */
> + generate_exception_if(modrm_mod == 3, EXC_UD, -1);
> dst.val = ea.mem.off;
> break;
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-01-05 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 15:03 [PATCH] x86: emulate lea with two register operands correctly David Vrabel
2012-01-05 15:49 ` Keir Fraser [this message]
2012-01-05 16:06 ` Tim Deegan
2012-01-05 19:03 ` Keir Fraser
2012-01-05 16:17 ` David Vrabel
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=CB2B7723.36EB2%keir@xen.org \
--to=keir@xen.org \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xensource.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 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.