Re: [Embedded-pv-devel] Driver domain under Xen

[Andrii Tseglytskyi <andrii.tseglytskyi@xxxxxxxxxxxxxxx>]

Hi Julien

On Fri, Jan 23, 2015 at 4:48 PM, Julien Grall <julien.grall@xxxxxxxxxx> wrote:
> On 23/01/15 14:19, Andrii Tseglytskyi wrote:
>> Hi,
>
> Hi Andrii,
>
>> Xen related development in GlobalLogic is going with good progress, and
>> latest what we've done on our platform is *driver domain*.
>> Right now on our platform dom0 doesn't access any hardware (except SATA
>> and block device). Driver domain manages all hardware and run all
>> backend drivers.
>> This required several changes in hypervisor, toolstack, kernels,
>> filesystems, device trees etc. I would like to write an article abut our
>> experience of driver domain + backends bringup.
>>
>> Will this be interesting?
>
> It's a good blog post.
>
> OOI, what did you modify in the hypervisor and toolstack? I was able to
> create drivers domain without any modification aside my non-pci
> passthrough series.
>

Briefly - I added possibility to map driver domain memory 1 to 1,
added possibility to allocate 128/256/512 Mb of RAM in one chunk, new
XSM label, and reworked IRQ routing a bit. It's great that this is
interesting for you - I will describe this in blog with lot of
details.

Regarding passtrough - I did not use this series - we still live with
attached devtree blob. To make passtrough working for us we need to
extend it a bit. I'll come to you with summary what is needed asap. (I
think after blog post)

Thank you,
Regards,
Andrii

> Regards,
>
> --
> Julien Grall



-- 

Andrii Tseglytskyi | Lead engineer
GlobalLogic
www.globallogic.com

_______________________________________________
Embedded-pv-devel mailing list
Embedded-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/embedded-pv-devel