From: Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
To: David kiarie <davidkiarie4@gmail.com>, Jan Kiszka <jan.kiszka@web.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Rita Sinha <rita.sinha89@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Aspirant for AMD IOMMU emulation project for Outreachy
Date: Wed, 9 Sep 2015 11:47:07 +0500 [thread overview]
Message-ID: <55EFD5EB.9090700@gmail.com> (raw)
In-Reply-To: <CABdVeAC7m7baF9A55+h2DqDCm9OW4dKA2JK88n75q4T_TxKRAA@mail.gmail.com>
Hi all,
On 09.09.2015 09:23, David kiarie wrote:
> On Wed, Sep 9, 2015 at 12:35 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
>> [thanks for forwarding, Peter]
>>
>> Hi Rita,
>>
>> On 2015-09-08 10:11, Peter Maydell wrote:
>>> On 7 September 2015 at 22:31, Rita Sinha <rita.sinha89@gmail.com> wrote:
>>>> Hi Jan,
>>>>
>>>> I am interested in participating in next round of Outreachy program
>>>> with AMD IOMMU emulation project.
>>>>
>>>>
>>>> I have worked on BIOS projects which includes coreboot SeaBios etc and
>>>> bootloaders like u-boot and grub. I have experience of working with
>>>> qemu and feel that this project is the right match for my skillset.
>>>> Kindly guide me how to go ahead with this.
>>
>> The particular AMD IOMMU project moved on since we listed it. I'm CC'ing
>> David, who is currently working on it and just recently posted related
>> patches, and Valentine who probably oversees the status better than I
>> (due to my lacking involvement recently). David, maybe you can briefly
>> comment on status and plans of your work.
>
> Hi all,
>
> Most recent work is here
> http://lists.nongnu.org/archive/html/qemu-devel/2015-08/msg02759.html
> . Most the code is Qemu device boilerplate(so there are a ton of
> things to add but I wanted to have the existing work merged first).
> The IOMMU just offers basic translation. From Valentine's previous
> comments, I only have a few minor issues to fix in the code.
This is a bit of off-topic here, but I'd argue they are minor. There are
some inaccuracies in emulation, and IOMMU itself is rather
feature-limited, just as you said. I doubt I'd be able to run current
Jailhouse implementation on it, for instance, albeit I haven't tried.
So, your patches are good start, but I feel there's a somewhat long way
before they actually get merged.
So, in short: there are still tasks to be done in AMD IOMMU emulation
project. I also feel it's possible to parallelize them so David and Rita
can continue without stepping at each other toe, if the program permits it.
> I obviously do other things alongside :-D this project but given some
> time I could get the code merged and continue to add other features.
>
>>
>> For the Outreachy program, just like for GSoC, we need to find a good
>> topic that is sufficiently clear defined on program start and not worked
>> on in parallel during the runtime. There are still a number of open
>> topics in this area, e.g. around the older Intel IOMMU model (error
>> handling and reporting, interrupt remapping), or maybe we find something
>> different - depends on your interests and experiences. Do you have any
>> public references to your previous work?
>>
>> Then I'd suggest to schedule an irc meeting to discuss your interests
>> and background a bit further and consider available options.
>>
>> Jan
>>
Regards,
Valentine
next prev parent reply other threads:[~2015-09-09 6:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 21:31 [Qemu-devel] Aspirant for AMD IOMMU emulation project for Outreachy Rita Sinha
2015-09-08 8:11 ` Peter Maydell
2015-09-08 21:35 ` Jan Kiszka
2015-09-09 4:23 ` David kiarie
2015-09-09 5:01 ` Rita Sinha
2015-09-09 6:34 ` David kiarie
2015-09-09 17:41 ` Rita Sinha
2015-09-11 6:50 ` Jan Kiszka
2015-09-11 6:58 ` Jan Kiszka
2015-09-09 6:47 ` Valentine Sinitsyn [this message]
2015-09-09 6:54 ` David kiarie
2015-09-09 7:07 ` Valentine Sinitsyn
2015-09-09 4:57 ` Rita Sinha
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=55EFD5EB.9090700@gmail.com \
--to=valentine.sinitsyn@gmail.com \
--cc=davidkiarie4@gmail.com \
--cc=jan.kiszka@web.de \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rita.sinha89@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 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.