From: Alistair Francis <alistair23@gmail.com>
To: LIU ZhiWei <zhiwei_liu@c-sky.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
Sagar Karandikar <sagark@eecs.berkeley.edu>,
bastian@mail.uni-paderborn.de, Palmer Dabbelt <palmer@sifive.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Alistair Francis <Alistair.Francis@wdc.com>
Subject: Re: [Qemu-devel] RISC-V: Vector && DSP Extension
Date: Sun, 11 Aug 2019 09:50:31 -0700 [thread overview]
Message-ID: <CAKmqyKM5zneojhPe57h1+h3pav5kQxFaMnhNiwWRUa=nbzS3Ag@mail.gmail.com> (raw)
In-Reply-To: <c502163b-ed8a-89d1-6437-9b0f49e88a84@c-sky.com>
On Sat, Aug 10, 2019 at 6:55 AM LIU ZhiWei <zhiwei_liu@c-sky.com> wrote:
>
>
> On 8/9/19 6:54 PM, Alistair Francis wrote:
>
> On Thu, Aug 8, 2019 at 2:52 AM liuzhiwei <zhiwei_liu@c-sky.com> wrote:
>
> Hi all,
>
> My workmate and I have been working on Vector & Dsp extension, and
> I'd like to share develop status with folks.
>
> Cool!
>
> The spec references for Vector extension is riscv-v-spec-0.7.1, and
> riscv-p-spec-0.5 for DSP extension. The code of vector extension is
> ready and under testing, the first patch will be sent about two weeks
> later. After that we will forward working on DSP extension, and send the
> first patch in middle October.
>
> What code are you talking about? Is this QEMU code?
>
> Hi Alistair,
>
> It's the QEMU code I have been working on these days, which implements Vector extension. It is under testing,
> and will be sent later.
Great! Please send it when you have it ready. We can accept draft
extensions in QEMU as long as they are disabled by default.
Alistair
>
> Could the maintainers tell me whether the specs referenced are
> appropriate? Is anyone working on these extensions? I'd like to get
> your status, and maybe discuss questions and work togather.
>
> Just use the latest (master) from the ISA spec git repo.
>
> I will follow your advice.Thanks for your attention to this matter.
>
> Best Regards,
>
> Zhiwei
>
> I don't know anyone doing vector work for QEMU. It would be very
> useful, but everyone is busy with something at the moment
> unfortunately.
>
> Alistair
>
> Best Regards
>
> LIU Zhiwei
>
>
>
next prev parent reply other threads:[~2019-08-11 16:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 9:39 [Qemu-devel] RISC-V: Vector && DSP Extension liuzhiwei
2019-08-08 11:29 ` Aleksandar Markovic
2019-08-08 13:48 ` Chih-Min Chao
2019-08-08 14:19 ` Aleksandar Markovic
2019-08-10 13:35 ` LIU ZhiWei
2019-08-10 1:54 ` Alistair Francis
2019-08-10 13:55 ` LIU ZhiWei
2019-08-11 16:50 ` Alistair Francis [this message]
2019-08-15 8:53 ` Aleksandar Markovic
2019-08-15 9:07 ` Peter Maydell
2019-08-15 10:32 ` Aleksandar Markovic
2019-08-15 21:37 ` Alistair Francis
2019-08-21 19:31 ` Palmer Dabbelt
2019-08-21 23:10 ` [Qemu-devel] [Qemu-riscv] " Jonathan Behrens
2019-08-22 1:50 ` [Qemu-devel] " liuzhiwei
2019-08-22 22:37 ` Alistair Francis
2019-08-28 0:25 ` Palmer Dabbelt
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='CAKmqyKM5zneojhPe57h1+h3pav5kQxFaMnhNiwWRUa=nbzS3Ag@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=bastian@mail.uni-paderborn.de \
--cc=palmer@sifive.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
--cc=zhiwei_liu@c-sky.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).