qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Sergey Fedorov <serge.fdrv@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Merten Sach <msach@mailbox.tu-berlin.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] GSoC Proposal: ARM Virtualization Extensions
Date: Tue, 24 Mar 2015 12:58:44 +1000	[thread overview]
Message-ID: <20150324025844.GI23658@toto> (raw)
In-Reply-To: <550ED1EF.7010108@gmail.com>

On Sun, Mar 22, 2015 at 07:30:07AM -0700, Sergey Fedorov wrote:
> On 20.03.2015 21:49, Edgar E. Iglesias wrote:
> > Hi all,
> >
> > Sergey, that's good to hear!
> >
> > Peter, Yes I have quite a bit of patch material but unfortunately a lot of
> > it is not in a state for upstreaming. I know I've promised to clean
> > it up and submit more but I have not been able to find time for it,
> > sorry about that...
> >
> > Patches that I planned to send are around hyp timers, misc bugfixes
> > here and there and maybe the GIC virt extensions.
> >
> > The 2 stage MMU code I have is shamefully ugly but it kind of works
> > so it is useful for understanding some of the problems that need to be
> > solved. (works well enough to boot XEN and KVM guests).
> >
> > Sergey and myself communicated a bit off-list a while back ago
> > and he expressed interest in AArch64 EL2 and my code. Sergey, it would be
> > very interesting to hear more details on how you are doing on that?
> >
> > Cheers,
> > Edgar
> 
> Hi Edgar,
> 
> I successfully reproduced your results with running KVM on your patches.
> Then I decided to start implementing the features without looking at
> your code so that I can get somewhat different view on how to implement
> that. Then I plan to compare my and your code and make a final version.
> 
> Now I've got patches that allows to boot Linux kernel with KVM enabled.
> So KVM initialization is happy. Basically, I added some EL2 registers
> required by KVM and adjusted page table walk to support EL2 translation
> regime. A colleague of mine has prepared a patch to support
> virtualization extensions in generic timer.
> 
> Before sending patches here, I will do my best to carefully compare my
> final code against yours and credit you appropriately in that patches
> for any derivatives found. Anyway, do not hesitate to ask questions or
> point out any misses in respect of this matter.


Thanks Sergey!

Cheers,
Edgar

  reply	other threads:[~2015-03-24  3:00 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 [this message]
2015-03-23 11:29     ` Merten Sach
2015-03-24 13:47       ` Sergey Fedorov
2015-03-25 22:09         ` Merten Sach
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=20150324025844.GI23658@toto \
    --to=edgar.iglesias@gmail.com \
    --cc=msach@mailbox.tu-berlin.de \
    --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).