From: Nick Renieris <makren67@gmail.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] AVX support for TCG
Date: Fri, 28 Dec 2018 15:43:59 +0200 [thread overview]
Message-ID: <CAObpvQmejWBh+RNz2vhk16-kcY_QveM_pSmM5ZeWqWv1d8AJzQ@mail.gmail.com> (raw)
In-Reply-To: <b4cdc06a-8114-48d2-2c0a-9fea876fee4a@linaro.org>
>> Do you think this could work as a GSoC project? I'm potentially
>> interested in working on it this summer.
>Could be. My first guess is something like 4 months work for this.
Four months full-time? If so I would say it's not viable for a GSoC
project (it's 3 months), I've done the 12-hours-a-day-crunch thing for
a week or so in GSoC 2017 and it was _not_ fun.
Also, I hope you meant four months for me, not for you - I'm
completely new to the QEMU codebase. I expect it will take me weeks
just to understand x86's 'translate.c' (who thought it'd be a good
idea to put all this stuff in _one_ file?).
Another question, are there existing discussions about this
refactoring effort or specifically AVX? I asked a similar question on
IRC a few days ago and got no answers.
Στις Τετ, 26 Δεκ 2018 στις 4:12 π.μ., ο/η Richard Henderson
<richard.henderson@linaro.org> έγραψε:
>
> On 12/26/18 12:28 PM, Nick Renieris wrote:
> > Hi Richard,
> >
> > I did know about https://github.com/andikleen/qemu-avx but didn't
> > mention it as it seems abandoned and quite old (also it doesn't use
> > `TCGv_vec`).
>
> Yep. Mine pre-dates tcg-op-gvec.h as well.
>
> > Do you think this could work as a GSoC project? I'm potentially
> > interested in working on it this summer.
>
> Could be. My first guess is something like 4 months work for this.
>
>
> r~
next prev parent reply other threads:[~2018-12-28 13:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-25 23:43 [Qemu-devel] AVX support for TCG Nick Renieris
2018-12-26 1:07 ` Richard Henderson
2018-12-26 1:28 ` Nick Renieris
2018-12-26 2:12 ` Richard Henderson
2018-12-28 13:43 ` Nick Renieris [this message]
2018-12-28 14:13 ` Peter Maydell
2018-12-28 14:28 ` Nick Renieris
2018-12-28 14:38 ` Peter Maydell
2018-12-28 17:19 ` Nick Renieris
2018-12-28 21:15 ` Alex Bennée
2018-12-29 20:24 ` Richard Henderson
2018-12-30 20:51 ` Nick Renieris
2018-12-31 1:58 ` Richard Henderson
2019-01-04 21:43 ` Nick Renieris
2019-01-04 21:51 ` Richard Henderson
2019-01-04 22:09 ` Nick Renieris
2019-01-04 22:14 ` Richard Henderson
2019-01-04 22:33 ` Nick Renieris
2019-01-04 22:38 ` Richard Henderson
2019-01-04 22:42 ` Nick Renieris
2019-01-17 9:29 ` Stefan Hajnoczi
2019-01-17 13:57 ` Nick Renieris
2019-01-18 9:57 ` 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=CAObpvQmejWBh+RNz2vhk16-kcY_QveM_pSmM5ZeWqWv1d8AJzQ@mail.gmail.com \
--to=makren67@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.