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

[Xen-devel] Question about arm passthrough and power related



Hi,

I am trying to passthrough a platform device to domU, but as we know
clk dts property and related code are handled in dom0. If passthrough the
platform device to domU, then how the clock for the device.

I came across this documentation "How to passthrough your integrated device to a
VM on ARM" at  
https://events.linuxfoundation.org/sites/events/files/slides/talk_5.pdf.
And follow the steps, and I can assign machine io memory space to domU on my
platform without smmu support. But domU driver probe function will fail,
because there is no clk property in the domU partial dts.

For example, without the clocks property, domU driver probe will fail.
uart2: serial@30890000 {
    compatible = "fsl,imx7d-uart", "fsl,imx6q-uart", "fsl,imx21-uart";
    reg = <0x30870000 0x10000>;
    interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
    clocks = <&clks IMX7D_UART2_ROOT_CLK>,
    <&clks IMX7D_UART2_ROOT_CLK>;
    clock-names = "ipg", "per";
    xxxxxx
    };


I have another question which is about power related. Without xen, linux can
runs into suspend state, ddr into self-refresh state, arm core powered off, and
clocks for some devices are off and power off;
If with xen, should the power related stuff implemented in xen hypervisorr
or still in dom0 linux?

Thanks,
Peng.

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


 


Rackspace

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