Re: [Xen-devel] [PATCH RFC 0/5] Split off mini-os to a separate tree

[Thomas Leonard <talex5@xxxxxxxxx>]

On 26 January 2015 at 17:56, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:
> On 26 Jan 2015, at 17:42, Martin Lucina <martin@xxxxxxxxxx> wrote:
>>
>> talex5@xxxxxxxxx said:
>>> In case it's useful: for the standalone version of Mini-OS used by
>>> Mirage, I had to include these directories too:
>>>
>>> 1. xen/include/public
>>> 2. xen/common/libfdt
>>> 3. xen/include/xen/libfdt
>>> 4. config
>>>
>>> ( https://github.com/talex5/xen/tree/minios-releases )
>>
>> Ah, so that's where the Mirage fork of Mini-OS lives. I knew there was one,
>> but not where. Any other forks please speak up :-)
>>
>> Which parts of Mini-OS does Mirage actually use? I know you have an OCaml
>> implementation of netfront, for instance.
>
> Not very much of Mini-OS -- Mirage has everything from the ring protocol
> up (XenStore, NetBack/Front, BlkBack/Front, Console, etc are all in OCaml).
> So event channels and start of day boot, mainly.
>
> It is useful to have the C XenBus around for start-of-day logging though,
> since the emergency console isn't much use on public cloud services.

Actually, we don't use C XenBus either. The Mirage start_kernel is:

void start_kernel(void)
{
  init_events();
  local_irq_enable();
  setup_xen_features();
  init_mm();
  init_time();
  init_console();
  init_gnttab();
  app_main_thread(NULL);
}

We don't use the scheduler or xenbus from Mini-OS. It's mainly startup
code, malloc and printk (for debug logging before Mirage's console
driver is ready), time and gnttab.


-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel