qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Xin Tong <trent.tong@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Intel AVX instructions
Date: Wed, 22 Jan 2014 20:06:47 +0000	[thread overview]
Message-ID: <CAFEAcA9zUDkmjfzFCiC-T2SCsfdp+SygzOxdbrx+DBiLtqOgtQ@mail.gmail.com> (raw)
In-Reply-To: <CA+JLOivb8Q-Ym_vDxOw38pgNGoxjpYAkYnB46MLCYtM0d=-8Sg@mail.gmail.com>

On 22 January 2014 19:35, Xin Tong <trent.tong@gmail.com> wrote:
> It seems that BOCHS have AVX instructions support in interpreter. I am
> thinking an easy/reliable way to do this would be generate helper
> calls to emulate every AVX instruction and follow how BOCHS emulates
> them. Then depending on the expected frequency and difficulties, one
> can decide whether to move some of the instructions into TCG JITted
> code ?

I would recommend implementing them from scratch for QEMU
based on the Intel architecture documentation. That will produce
much nicer results.

> Also, it would be desirable to use the MMX/SSE structures and
> functions that already exist in QEMU target-i386/translate.c

It would certainly be advisable to use them where there is
commonality.

thanks
-- PMM

  reply	other threads:[~2014-01-22 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 16:27 [Qemu-devel] Intel AVX instructions Xin Tong
2014-01-22 17:35 ` Paolo Bonzini
2014-01-22 19:35   ` Xin Tong
2014-01-22 20:06     ` Peter Maydell [this message]
2014-01-22 20:19     ` Richard Henderson
2014-01-22 21:57       ` Xin Tong

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=CAFEAcA9zUDkmjfzFCiC-T2SCsfdp+SygzOxdbrx+DBiLtqOgtQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=trent.tong@gmail.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 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).