From: Julien Grall <julien.grall@linaro.org>
To: Chen Baozi <baozich@gmail.com>,
List Developer Xen <xen-devel@lists.xen.org>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Lars Kurth <lars.kurth@xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: Initial Mini-OS port to ARM64
Date: Mon, 24 Feb 2014 14:30:51 +0000 [thread overview]
Message-ID: <530B579B.70707@linaro.org> (raw)
In-Reply-To: <53012314.2050906@linaro.org>
Somehow, my gmail account claimed it sent the mail with Karim CCed, but
it was not in the thread. Adding Karim back.
Thanks Lars for spotting it!
On 02/16/2014 08:44 PM, Julien Grall wrote:
> On 16/02/14 15:51, Chen Baozi wrote:
>> Hi all,
>
> Hello Chen,
>
>> It is much later than I used to expect. I guess it might be help
>> to publish my work, though it is still not finished (and might not
>> be finished very soon...).
>>
>> I began to try to port mini-os to ARM64 since last summer. Since
>> the 64-bit guest support is not quite well at that time, this
>> work had been stopped for a long time until two months ago.
>>
>> Though it is still at very early stage, it at least can be built,
>> setup a early page table for booting, parse the DTB passed by the
>> hypervisor, and be debugged by printk at present. So I put it
>> on github in case someone might be interested in it. Here is the
>> url: https://github.com/baozich/minios-arm64
>
> Good job!
>
>> Right now, there are some troubles to make GIC work properly,
>> as I didn’t consider mapping GIC’s interface in address space and
>> follows x86’s memory layout which make the kernel virtual address
>> starts at 0x0. I’ll fix it as soon as possible.
>
> I think you should try to sync up with Karim (in CC). He has started to
> port mini-OS on arm32. Except assembly code (which should be fairly
> small) everything can be shared between the both architecture.
>
> If I remember correctly, Karim already wrote a GIC support but without
> FDT support.
>
>> Besides, there is still lots of work to be done. So any comments
>> or patches are welcome.
>
> Regards,
>
--
Julien Grall
next prev parent reply other threads:[~2014-02-24 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 15:51 Initial Mini-OS port to ARM64 Chen Baozi
2014-02-16 20:44 ` Julien Grall
2014-02-24 14:30 ` Julien Grall [this message]
[not found] ` <CAOTdubvBf9Ce=MZJQs639sOt+718CsgDv2D+oO1_B7XXu+SgGw@mail.gmail.com>
2014-02-24 15:49 ` Julien Grall
2014-02-18 15:54 ` Ian Campbell
2014-02-23 14:41 ` Chen Baozi
2014-02-24 1:35 ` Chen Baozi
2014-02-24 11:27 ` Ian Campbell
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=530B579B.70707@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=baozich@gmail.com \
--cc=lars.kurth@xen.org \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.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.