Re: [Xen-devel] [RFC PATCH 5/7] cpufreq: cpufreq-cpu0: change cpus data path in devtree for Dom0 kernel

[Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>]

On Tue, Oct 7, 2014 at 6:49 PM, Julien Grall <julien.grall@xxxxxxxxxx> wrote:
> Hi Oleksandr,
>
> On 10/07/2014 03:20 PM, Oleksandr Dmytryshyn wrote:
>> Xen hypervisor creates standard cpus nodes for virtual cpus.
>> All information needed for this driver about physical cpus
>> now located in /cpus/cpu@0/private_data node instead of the
>> /cpus node.
>>
>> Signed-off-by: Oleksandr Dmytryshyn <oleksandr.dmytryshyn@xxxxxxxxxxxxxxx>
>> ---
>>  drivers/cpufreq/cpufreq-cpu0.c | 4 ++++
>>  1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
>> index ef4fbc4..3c4474a 100644
>> --- a/drivers/cpufreq/cpufreq-cpu0.c
>> +++ b/drivers/cpufreq/cpufreq-cpu0.c
>> @@ -182,7 +182,11 @@ static int cpu0_cpufreq_probe(struct platform_device 
>> *pdev)
>>       struct device_node *np;
>>       int ret;
>>
>> +#ifdef CONFIG_XEN_DOM0
>> +     np = of_find_node_by_path("/cpus/cpu@0/private_data/cpu@0");
>> +#else
>>       np = of_find_node_by_path("/cpus/cpu@0");
>> +#endif
>
> A same kernel should be able to run on bare metal and within Xen.
> Furthermore, this path should only be check for DOM0 and not any guest.
I'll do it in the next patch-set.

> Regards,
>
>
> --
> Julien Grall

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