qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>, qemu-devel@nongnu.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: Re: [RFC PATCH] i386/tcg: add AVX/AVX2 support (severely incomplete,  just for preliminary feedback)
Date: Wed, 16 Feb 2022 20:24:39 +1100	[thread overview]
Message-ID: <65399dfb-02bd-473f-a7b7-23131fde30be@linaro.org> (raw)
In-Reply-To: <20220215205637.36863-1-alex@linutronix.de>

On 2/16/22 07:56, Alexander Kanavin wrote:
> Lack of AVX/AVX2 support in the i386 TCG has been a significant gap
> for a long while; I've started work to close this gap.
> 
> This is of course nowhere near complete, or even buildable, I'm
> just requesting initial feedback from the qemu gurus - am I on
> the right track with this? Does something need to be done differently?
> 
> There's an enormous amount of legacy SSE instructions to adjust
> for VEX-128 and VEX-256 flavours, so I would want to know that this
> way would be acceptable.
> 
> Signed-off-by: Alexander Kanavin<alex@linutronix.de>
> ---

Have a look at updating some existing work:

https://lore.kernel.org/qemu-devel/20190821172951.15333-1-jan.bobek@gmail.com/


r~


  reply	other threads:[~2022-02-16  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 20:56 [RFC PATCH] i386/tcg: add AVX/AVX2 support (severely incomplete, just for preliminary feedback) Alexander Kanavin
2022-02-16  9:24 ` Richard Henderson [this message]
2022-02-16  9:52   ` Alexander Kanavin
  -- strict thread matches above, loose matches on Subject: below --
2022-02-15 21:00 Alexander Kanavin

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=65399dfb-02bd-473f-a7b7-23131fde30be@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=qemu-devel@nongnu.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 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).