qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Walid Ghandour <waleedjghandour@gmail.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <richard.henderson@linaro.org>,
	Eduardo Habkost <eduardo@habkost.net>
Subject: Re: AVX-512 instruction set
Date: Wed, 12 Apr 2023 13:13:25 +0100	[thread overview]
Message-ID: <87y1mxnvlo.fsf@linaro.org> (raw)
In-Reply-To: <CAEQMSUtx73GosLwzMLERTMkJ=eLiU5NbwZY1K0eOmFbJ-M=4Kw@mail.gmail.com>


Walid Ghandour <waleedjghandour@gmail.com> writes:

> Hello,
>
> I am interested in adding AVX512 to qemu.

(add x86 TCG maintainers to CC)

> Is anyone currently working on this ?
>
> If yes, when is it expected to be done ?

I don't think there is currently any active effort to add AVX512
support. There have been various GSoC projects to improve the x86 SIMD
emulation but I don't think they got merged.

There has been some updates to improve the SSE emulation in the last few
releases and make the instruction decoder a little easier to work wit.

>
> I was trying to run a C program and failed with the following error at this instruction:
>
> 62 f2 7d 48 18 0d fa 0c 00 00 vbroadcastss 0xcfa(%rip),%zmm1
>
> qemu: uncaught target signal 4 (Illegal instruction) - core dumped
>
> I like to add support for broadcast and fmadd avx 512 instructions such as the following one: 
>
> 62 e2 7d 48 b8 c9     vfmadd231ps %zmm1,%zmm0,%zmm17
>
> Thanks,
> Walid


-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro


  reply	other threads:[~2023-04-12 12:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12  9:41 AVX-512 instruction set Walid Ghandour
2023-04-12 12:13 ` Alex Bennée [this message]
2023-04-12 13:30   ` Paolo Bonzini
2023-04-12 13:41     ` Walid Ghandour
2023-04-12 13:55       ` Paolo Bonzini

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=87y1mxnvlo.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=waleedjghandour@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).