From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Taylor Simpson <tsimpson@quicinc.com>
Cc: "Alessandro Di Federico" <ale@rev.ng>,
"nizzo@rev.ng" <nizzo@rev.ng>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Niccolò Izzo" <izzoniccolo@gmail.com>
Subject: Re: QEMU for Qualcomm Hexagon - KVM Forum talk and code available
Date: Tue, 5 Nov 2019 01:05:20 +0100 [thread overview]
Message-ID: <CAL1e-=jvmJNiZR4iLDL-97qm=v+2s0cwn5YTzJQ=JZ_gwOe4tQ@mail.gmail.com> (raw)
In-Reply-To: <BYAPR02MB48863165DEE32E5C563E93F4DE650@BYAPR02MB4886.namprd02.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1892 bytes --]
On Friday, October 25, 2019, Taylor Simpson <tsimpson@quicinc.com> wrote:
> We would like inform the you that we will be doing a talk at the KVM Forum
> next week on QEMU for Qualcomm Hexagon. Alessandro Di Federico, Niccolo
> Izzo, and I have been working independently on implementations of the
> Hexagon target. We plan to merge the implementations, have a community
> review, and ultimately have Hexagon be an official target in QEMU. Our
> code is available at the links below.
>
> *https://github.com/revng/qemu-hexagon
> <https://github.com/revng/qemu-hexagon>*
>
> *https://github.com/quic/qemu <https://github.com/quic/qemu>*
>
> If anyone has any feedback on the code as it stands today or guidance on
> how best to prepare it for review, please let us know.
>
>
>
Hi, Taylor, Niccolo (and Alessandro too).
I didn't have a chance to take a look at neither the code nor the docs, but
I did attend you presentation at KVM Forum, and I found it superb and
attractive, one of the best on the conference, if not the very best.
I just have a couple of general questions:
- Regarding the code you plan to upstream, are all SIMD instructions
implemented via tcg API, or perhaps some of them remain being implemented
using helpers?
- Most of SIMD instructions can be viewed simply as several paralel
elementary operations. However, for a given SIMD instruction set, usually
not all of them fit into this pattern. For example, "horizontal add"
(addind data elements from the same SIMD register), various
"pack/unpack/interleave/merge" operations, and more general
"shuffle/permute" operations as well (here I am not sure which of these are
included in Hexagon SIMD set, but there must be some). How did you deal
with them?
- What were the most challenging Hexagon SIMD instructions you came accross
while developing your solution?
Sincerely,
Aleksandar
> Thanks,
>
> Taylor
>
[-- Attachment #2: Type: text/html, Size: 2968 bytes --]
next prev parent reply other threads:[~2019-11-05 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 16:26 QEMU for Qualcomm Hexagon - KVM Forum talk and code available Taylor Simpson
2019-11-01 18:29 ` Philippe Mathieu-Daudé
2019-11-04 2:35 ` Taylor Simpson
2019-11-05 0:05 ` Aleksandar Markovic [this message]
2019-11-05 16:32 ` Taylor Simpson
2019-11-12 22:52 ` Taylor Simpson
2019-11-13 10:31 ` Alex Bennée
2019-11-13 19:31 ` Taylor Simpson
2019-11-13 21:10 ` Richard Henderson
2019-11-15 0:54 ` Taylor Simpson
2019-12-17 18:14 ` Taylor Simpson
2019-12-17 18:19 ` Thomas Huth
2019-12-17 18:21 ` Peter Maydell
2019-12-17 18:41 ` Philippe Mathieu-Daudé
2019-12-17 18:44 ` Philippe Mathieu-Daudé
2019-12-18 23:50 ` Richard Henderson
2019-11-13 21:27 ` Peter Maydell
2019-11-19 9:12 ` Philippe Mathieu-Daudé
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='CAL1e-=jvmJNiZR4iLDL-97qm=v+2s0cwn5YTzJQ=JZ_gwOe4tQ@mail.gmail.com' \
--to=aleksandar.m.mail@gmail.com \
--cc=ale@rev.ng \
--cc=izzoniccolo@gmail.com \
--cc=nizzo@rev.ng \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.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).