xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: "karim.allah.ahmed@gmail.com" <karim.allah.ahmed@gmail.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Chen Baozi <baozich@gmail.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Initial Mini-OS port to ARM64
Date: Mon, 24 Feb 2014 15:49:04 +0000	[thread overview]
Message-ID: <530B69F0.3020904@linaro.org> (raw)
In-Reply-To: <CAOTdubvBf9Ce=MZJQs639sOt+718CsgDv2D+oO1_B7XXu+SgGw@mail.gmail.com>

You forget to reply all.

On 02/24/2014 03:30 PM, karim.allah.ahmed@gmail.com wrote:
> On Sun, Feb 16, 2014 at 8:44 PM, Julien Grall <julien.grall@linaro.org> 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.
> 
> +1
> 
> I totally agree with Julien.
> 
> I don't know how far are you at the moment, but would it be easy to
> rebase your work on top of mine ( or the other way around ? ).
> Let me know what can I do to sync up with your work
> 
>>
>> If I remember correctly, Karim already wrote a GIC support but without FDT
>> support.
> 
> Yes, that's correct. All addresses ( not just for GIC ) at the moment
> are fixed, so once the memory layout changes everything will crash :)
> 
>>
>>
>>> Besides, there is still lots of work to be done. So any comments
>>> or patches are welcome.
>>
>>
>> Regards,
>>
>> --
>> Julien Grall
> 
> 
> 


-- 
Julien Grall

  parent reply	other threads:[~2014-02-24 15:49 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
     [not found]   ` <CAOTdubvBf9Ce=MZJQs639sOt+718CsgDv2D+oO1_B7XXu+SgGw@mail.gmail.com>
2014-02-24 15:49     ` Julien Grall [this message]
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=530B69F0.3020904@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=baozich@gmail.com \
    --cc=ian.campbell@citrix.com \
    --cc=karim.allah.ahmed@gmail.com \
    --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 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).