From: Merten Sach <msach@mailbox.tu-berlin.de>
To: Sergey Fedorov <serge.fdrv@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC Proposal: ARM Virtualization Extensions
Date: Wed, 25 Mar 2015 23:09:29 +0100 [thread overview]
Message-ID: <55133219.2010902@mailbox.tu-berlin.de> (raw)
In-Reply-To: <55116AD6.3050305@gmail.com>
On 24/03/15 14:47, Sergey Fedorov wrote:
> On 23.03.2015 04:29, Merten Sach wrote:
>> On 21/03/15 04:16, Sergey Fedorov wrote:
>>> Hi!
>>>
>>> I am currently working on AArch64 EL2 support. There is a plan to submit
>>> the changes to the community. Merten, IIUYC, you are going to support
>>> only AArch32 EL2?
>>>
>>> Best regards,
>>> Sergey
>> Hi
>>
>> Yes, my intention is to focus on AArch32 as I'm more familiar with that
>> architecture.
>>
>> Thanks for the insight into the current state. As I understand, some parts of
>> AArch64 and AArch32 EL2 modes share a some functionality. For example,
>> * VGIC - compatible
>> * Exception Routing - different interface but same function
>> * Pagetable format - implemented with LPAE
>> * Generic Timer - different interface but same function
>>
>> Are these assumptions correct? I hope I didn't simplify it to much.
>>
>> And also: does it make sense to work with your code? Are you planing to commit
>> the changes before May?
>>
>> Would someone mentor this project?
>>
>> Best regards,
>> Merten
>>
>
> Hi,
>
> I didn't investigate the difference between AArch64 and AArch32. But I
> believe that AArch64 should be better structured. As of GIC and Generic
> Timer, I think you are right.
>
> I plan to start committing it in coherent chunks as soon as I can. And
> yes, I hope I finish it before May.
>
> Best regards,
> Sergey
>
>
Hi,
thanks for all your answers.
Sorry that I ask the same question again: would someone mentor this project? I
guess if not it makes no sense to hand in the proposal. :-(
After reading the answers by Sergey and Edgar, I'm unsure if the amount of work
is adequate for 12 weeks. Many AArch32 registers just map flat to their AArch64
counterpart and the function are mostly the same. I got the impression that
mostly fixing interfaces is not enough for GSoC.
Best regards
Merten
next prev parent reply other threads:[~2015-03-25 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 17:25 [Qemu-devel] GSoC Proposal: ARM Virtualization Extensions Merten Sach
2015-03-20 17:44 ` Peter Maydell
2015-03-21 3:16 ` Sergey Fedorov
2015-03-21 4:49 ` Edgar E. Iglesias
2015-03-22 14:30 ` Sergey Fedorov
2015-03-24 2:58 ` Edgar E. Iglesias
2015-03-23 11:29 ` Merten Sach
2015-03-24 13:47 ` Sergey Fedorov
2015-03-25 22:09 ` Merten Sach [this message]
2015-03-23 11:29 ` Merten Sach
2015-03-23 11:51 ` Peter Maydell
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=55133219.2010902@mailbox.tu-berlin.de \
--to=msach@mailbox.tu-berlin.de \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=serge.fdrv@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 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).