From: Stefan Hajnoczi <stefanha@gmail.com>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Alistair Francis <Alistair.Francis@wdc.com>,
dbarboza@ventanamicro.com, qemu-devel@nongnu.org,
kvm@vger.kernel.org, afaria@redhat.com, alex.bennee@linaro.org,
eperezma@redhat.com, gmaglione@redhat.com,
marcandre.lureau@redhat.com, rjones@redhat.com,
sgarzare@redhat.com, imp@bsdimp.com, philmd@linaro.org,
pbonzini@redhat.com, thuth@redhat.com, danielhb413@gmail.com,
gaosong@loongson.cn, akihiko.odaki@daynix.com,
shentey@gmail.com, npiggin@gmail.com, seanjc@google.com,
Marc Zyngier <maz@kernel.org>
Subject: Re: Call for GSoC/Outreachy internship project ideas
Date: Wed, 31 Jan 2024 09:39:25 -0500 [thread overview]
Message-ID: <CAJSP0QWE8P-GTNmFPbHvvDLstBZgTZA7sFg0qz4u28kUFiCAHg@mail.gmail.com> (raw)
In-Reply-To: <mhng-bcb98ddd-c9a7-4bb9-b180-bf310a289eeb@palmer-ri-x1c9a>
On Tue, 30 Jan 2024 at 14:40, Palmer Dabbelt <palmer@dabbelt.com> wrote:
> On Mon, 15 Jan 2024 08:32:59 PST (-0800), stefanha@gmail.com wrote:
> I'm not 100% sure this is a sane GSoC idea, as it's a bit open ended and
> might have some tricky parts. That said it's tripping some people up
> and as far as I know nobody's started looking at it, so I figrued I'd
> write something up.
Hi Palmer,
Your idea has been added:
https://wiki.qemu.org/Google_Summer_of_Code_2024#RISC-V_Vector_TCG_Frontend_Optimization
I added links to the vector extension specification and the RISC-V TCG
frontend source code.
Please add concrete tasks (e.g. specific optimizations the intern
should implement and benchmark) by Feb 21st. Thank you!
Stefan
next prev parent reply other threads:[~2024-01-31 14:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 16:32 Call for GSoC/Outreachy internship project ideas Stefan Hajnoczi
[not found] ` <CAAfnVBn0+627rLGXeLdsvUge0_VegcbTVuQf8rQwtjuJ3hcJnA@mail.gmail.com>
2024-01-24 12:51 ` Stefan Hajnoczi
2024-01-31 23:55 ` Gurchetan Singh
2024-02-01 0:11 ` Stefan Hajnoczi
2024-01-29 18:53 ` Eugenio Perez Martin
2024-01-29 19:39 ` Stefan Hajnoczi
2024-01-30 12:08 ` Eugenio Perez Martin
2024-01-30 19:34 ` Stefan Hajnoczi
2024-01-31 10:37 ` Eugenio Perez Martin
2024-01-30 19:16 ` Alexander Graf
2024-01-30 20:15 ` Stefan Hajnoczi
2024-01-30 19:40 ` Palmer Dabbelt
2024-01-30 20:28 ` Stefan Hajnoczi
2024-01-31 0:29 ` Palmer Dabbelt
2024-01-31 1:26 ` Alistair Francis
2024-01-31 1:50 ` Palmer Dabbelt
2024-02-01 17:39 ` Alex Bennée
2024-02-01 18:01 ` Palmer Dabbelt
2024-02-01 18:57 ` Alex Bennée
2024-02-01 19:06 ` Palmer Dabbelt
2024-01-31 14:39 ` Stefan Hajnoczi [this message]
2024-01-31 15:59 ` Palmer Dabbelt
2024-01-31 18:20 ` Stefan Hajnoczi
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=CAJSP0QWE8P-GTNmFPbHvvDLstBZgTZA7sFg0qz4u28kUFiCAHg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=Alistair.Francis@wdc.com \
--cc=afaria@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--cc=danielhb413@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=eperezma@redhat.com \
--cc=gaosong@loongson.cn \
--cc=gmaglione@redhat.com \
--cc=imp@bsdimp.com \
--cc=kvm@vger.kernel.org \
--cc=marcandre.lureau@redhat.com \
--cc=maz@kernel.org \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=seanjc@google.com \
--cc=sgarzare@redhat.com \
--cc=shentey@gmail.com \
--cc=thuth@redhat.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).