18.12.24 12:38, Julien Grall:
Are you sure this patch is sufficient to use the late hwdom feature?
Looking at the code, to enable the late hwdom, the user needs to
provide a domid on the command line. But AFAICT, there is no way to
provide a domain ID in the DOM0LESS case...
I append "hardware_dom=1" to xen,xen-bootargs in host's device tree
and it works.
AFAIU, the domain needs to be explicitely created. How do you do that?
Is it just describing the domain in the DT? If so, how does it work if
there are multiple domain described in the DT?
I just had a look at the code. I don't see how this change and simply
adding "hardware_dom=X" is sufficient.
In addition to what I wrote above, Dom0 will be the first domain created
and we will assign all the devices and mappings. When the hardware
domain is created later on, dom0 will still have those mappings and
devices. That's unless you list all the devices in the device-tree as
not assigned to dom0 and then assign them manually to the hardware domain.
I would also expect that the hardware domain wants to use the same
memory layout as the host. But that's not necessary for the control domain.
So surely you need something more in the device-tree?
yes, I had to assign devices to hardware domain manually.
-Sergiy
