[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Embedded-pv-devel] [Xen-devel] [PATCH RFC 13/18] xen: introduce and use 'dom0_rambase_pfn' setting for kernel Dom0
On Thu, May 19, 2016 at 5:36 PM, Jan Beulich <JBeulich@xxxxxxxx> wrote: >>>> On 19.05.16 at 15:58, <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx> wrote: >> Case 1: Dom0 is driver domain: >> There is a Ducati firmware which runs on dedicated M4 core and decodes >> video. This firmware uses hardcoded physical addresses for graphics >> buffers. Those addresses should be inside address-space of the driver >> domain (Dom0). Ducati firmware is proprietary and we have no ability >> to rework it. So Dom0 kernel should be placed to the configured >> address (to the DOM0 RAM bank with specific address). >> >> Case 2: Dom0 is Thin and DomD is driver domain. >> All is the same: Ducati firmware requires special (hardcoded) addresses. > > For both of these cases I would then wonder whether such > environments are actually suitable for doing virtualization on. Currently we use Jacinto 6 evaluation board with DRA74X processor. We have both configurations (Thin Dom0 and Thich Dom0). > Jan > _______________________________________________ Embedded-pv-devel mailing list Embedded-pv-devel@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/embedded-pv-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |