[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] ARM Xen Bug #45: Is there a solution?
Subject: Re: ARM Xen Bug #45: Is there a solution? Date: Tue, 31 May 2016 11:44:23 +0100 From: Julien Grall <julien.grall@xxxxxxx> To: Dirk Behme <dirk.behme@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxx <xen-devel@xxxxxxxxxxxxx> CC: Stefano Stabellini <sstabellini@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Hello Dirk, On 27/05/16 13:34, Dirk Behme wrote:On 26.05.2016 11:00, Julien Grall wrote:On 25/05/2016 16:10, Dirk Behme wrote:On 24.05.2016 22:05, Julien Grall wrote:On 24/05/2016 14:39, Dirk Behme wrote:On 23.05.2016 22:15, Julien Grall wrote:All the devices (UART included) used by Xen will return DOMID_XEN when dt_device_used_by is called to the node. You could use it to collect the clocks of all those devices and gather the value in a single property to be created in the hypervisor node.Anything like below (untested) [1]?Yes.I'm unhappy about the global variables and the max clocks, though.How about moving those variables in the structure kernel_info? Just for the logs to finish this thread: https://lists.xen.org/archives/html/xen-devel/2016-06/msg02607.html http://lists.infradead.org/pipermail/linux-arm-kernel/2016-June/438067.html Best regards Dirk _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |