From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: [PATCH] x86_emulate adjustments
Date: Fri, 05 Jan 2007 11:25:20 +0000 [thread overview]
Message-ID: <C1C3E620.7241%keir@xensource.com> (raw)
In-Reply-To: <459E307D.76E4.0078.0@novell.com>
On 5/1/07 10:03, "Jan Beulich" <jbeulich@novell.com> wrote:
> - don't provide cmpxchg8b emulation where not needed (i.e. page table ops on
> 64-bit hv)
With the cmpxchg16b changes this probably makes sense, despite my dislike of
ifdef if it can be avoided. I'll take a look.
> - properly deal with stack operands (push/pop)
I already got the mis-emulation of x86/64 PUSH/POP with operand-size
override. The stacksz thing I would do differently -- extend the mode input
field to have an extra stack-address-size field. There's another thing
that's not right at the moment -- I think on POP we have to calculate the
operand effective address after adjusting the stack pointer? That is broken
right now which is not a good thing. :-)
> - synchronize prefix handling with hvm's instrlen determination and about to
> be committed privileged op decoder (changes coming with the 32on64 patches)
The whole lot of hvm_instrlen/mmio/privop emulators are all going to get
merged into x86_emulate(). So sync'ing is not really worthwhile, unless
there are bugs in x86_emulate()'s prefix decoder.
> - support cmpxchg16b if the CPU supports it
I'll take a look at this part. Sounds sensible.
Thanks,
Keir
next prev parent reply other threads:[~2007-01-05 11:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-05 10:03 [PATCH] x86_emulate adjustments Jan Beulich
2007-01-05 11:25 ` Keir Fraser [this message]
2007-01-05 11:57 ` Jan Beulich
2007-01-05 12:05 ` Keir Fraser
2007-01-05 14:34 ` Keir Fraser
2007-01-05 14:50 ` Jan Beulich
2007-01-05 15:04 ` Keir Fraser
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=C1C3E620.7241%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.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.