[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Minios-devel] About the ARM supports of Unikraft



Hi Simon,

> -----Original Message-----
> From: Simon Kuenzer [mailto:simon.kuenzer@xxxxxxxxx]
> Sent: 2018年1月26日 18:38
> To: Wei Chen <Wei.Chen@xxxxxxx>
> Cc: Felipe Huici <Felipe.Huici@xxxxxxxxx>; Florian Schmidt
> <Florian.Schmidt@xxxxxxxxx>; Shijie Huang <Shijie.Huang@xxxxxxx>; Kaly Xin
> <Kaly.Xin@xxxxxxx>; Costin Lupu <costin.lup@xxxxxxxxx>; minios-
> devel@xxxxxxxxxxxxx
> Subject: Re: About the ARM supports of Unikraft
> 
> Hi Wei,
> 
> see my ansers inline. I put the mailing list in CC. We should have
> technical discussions publicly.
> 
> On 26.01.2018 08:48, Wei Chen wrote:
> > Hi Simon,
> >
> > I am reading the Unikraft code this week. Because the differences of ARM and
> x86,
> > For example, ARM may use different boot protocol
> (Linux/Documentation/arm64/booting.txt)
> > but x86 is using multiboot. I will add some changes to Unikraft code,
> Makefile and folders.
> 
> Sure. You can use the available architectures switches on Makefile.uk in
> order to select different compilation units and flags (you can have a
> look to plat/xen/Makefile.uk).
> What is the first platform and architecture you want to implement, is it
> KVM? In case you want to port code, please make sure that you get it

Yes, I am trying to boot an ARM64 sample on KVM : )

> from projects that do not conflict with the Unikraft's BSD license
> (means, Linux is out ;-) ).
> 

Thanks for reminding, I will pay more attention to the licenses of any code
that I would port to Unikraft.

> > In this case, I think I'd better write a simple proposal before do it. I
> will send this
> > proposal in next week.
> >
> > BTW:
> > Why the x86 code in arch folder is "x86_64" but in plat/kvm and plat/xen is
> "x86"?
> 
> This is a good point. Please do not get confused, we may even change
> this. The original idea was that we only support x86_64 for now.
> However, keeping the x86 folder in the platforms was a result of the
> porting we did from Mini-OS and Solo5. Especially, Mini-OS has code for
> 32 and 64 bit guests (which differs at some minor places). Since we
> wanted to keep it open for the future to add support for 32bit x86 - we
> kept it there.
> In case we add 32bit and it also differs minimally for the architecture
> folder, we might want to merge arch/x86_32 and arch/x86_64 to arch/x86.
> 
> You might need to do similar considerations for the ARM architectures
> and platforms.
> 

That makes sense. I will consider it for ARM code.

> >
> > Regards,
> > Wei Chen
> > IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended 
> recipient,
> please notify the sender immediately and do not disclose the contents to any
> other person, use it for any purpose, or store or copy the information in any
> medium. Thank you.
> >
> 
> Thanks,
> 
> Simon
_______________________________________________
Minios-devel mailing list
Minios-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/minios-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.