From: Razvan Cojocaru <rzvncj@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Is it safe to hvm_emulate_one() an MMX instruction?
Date: Wed, 17 Apr 2013 13:40:12 +0300 [thread overview]
Message-ID: <516E7C0C.3050808@gmail.com> (raw)
In-Reply-To: <516E94D902000078000CDF41@nat28.tlf.novell.com>
> So do you mean an MMX instruction, or MOVDQU (which is an XMM
> one)? In any event, 4.2 and later should be fine with this particular
> instruction (and a few more move variants), but 4.1.x and earlier
> won't be, nor does the emulator support the whole spectrum of
> MMX, XMM, and AVX instructions.
In this particular case, MOVDQ, but I'm interested in all the mentioned
types of instructions.
What happens when a HVM guest tries to execute such an unsupported
instruction, via the hypervisor calling hvm_emulate_one()? Does
hvm_emulate_one() not return X86EMUL_OKAY - is testing for that enough?
Thanks,
Razvan Cojocaru
next prev parent reply other threads:[~2013-04-17 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 9:30 Is it safe to hvm_emulate_one() an MMX instruction? Razvan Cojocaru
2013-04-17 10:26 ` Jan Beulich
2013-04-17 10:40 ` Razvan Cojocaru [this message]
2013-04-17 10:44 ` Jan Beulich
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=516E7C0C.3050808@gmail.com \
--to=rzvncj@gmail.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.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.