From: Andre Przywara <andre.przywara@amd.com>
To: Ashish Bijlani <ashish.bijlani@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: mmx sse emulation
Date: Wed, 5 Nov 2008 10:59:09 +0100 [thread overview]
Message-ID: <49116E6D.9080408@amd.com> (raw)
In-Reply-To: <ec55b17e0811041634n30c3fc19s5c425d8f41246776@mail.gmail.com>
Ashish Bijlani wrote:
> Hi,
>
> I want to emulate mmx/sse for hvm guests when applications inside hvm
> guests are compiled for mmx/sse but the underlying hardware doesn't
> support mmx/sse.
First: HVM guests require a virtualization capable processor. AFAIK all
these processors support at least SSE2 (if not SSE3). So why do you want
to emulate these instructions?
Second: Applications should check the CPUID bit before using instruction
set extension. So, if the host processor does not support MMX/SSE, the
guest shouldn't see this bit, too. And I doubt that you are faster with
emulating SSE compared to legacy x87-FPU executed natively.
So, what is the use-case of your proposal? Or am I missing something here?
Regards,
Andre.
> What is the best place to do this? i'm looking at
> x86_emulate but i dunno if that is the best place to put the emulation
> layer. any suggestions?? also, currently movq emulation is present in
> x86_emulate for handling mmio. however, i realized that get_fpu fails
> if the hardware doesn't have mmx capability. is it true or am i
> missing something here?
>
> Thanks,
> Ashish
--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x84917
next prev parent reply other threads:[~2008-11-05 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 0:34 mmx sse emulation Ashish Bijlani
2008-11-05 7:34 ` Keir Fraser
2008-11-05 7:52 ` Ashish Bijlani
2008-11-05 9:04 ` Keir Fraser
2008-11-05 9:59 ` Andre Przywara [this message]
2008-11-05 10:34 ` Ashish Bijlani
2008-11-05 12:25 ` Ashish Bijlani
[not found] ` <a7065af20811050710w3bf20245s95f31d0edb6e5879@mail.gmail.com>
2008-11-06 10:16 ` Ashish Bijlani
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=49116E6D.9080408@amd.com \
--to=andre.przywara@amd.com \
--cc=ashish.bijlani@gmail.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.