On 26/02/2025 11:59, Luca Fancellu wrote:
>
>
>>>
>
>return fdt;
> }
> @@ -362,7 +363,7 @@ void asmlinkage __init start_xen(unsigned long
> fdt_paddr)
>if ( acpi_disabled )
>{
>printk("Booting using Device Tree\n");
> -devic
>>
>>>
return fdt;
}
@@ -362,7 +363,7 @@ void asmlinkage __init start_xen(unsigned long
fdt_paddr)
if ( acpi_disabled )
{
printk("Booting using Device Tree\n");
-device_tree_flattened = relocate_fdt(fdt_paddr, fdt_size);
On 26/02/2025 11:45, Luca Fancellu wrote:
>
>
> Hi Michal,
>
>> On 26 Feb 2025, at 10:38, Orzel, Michal wrote:
>>
>>
>>
>> On 26/02/2025 09:36, Luca Fancellu wrote:
>>>
>>>
>>> Currently the early stage of the Arm boot maps the DTB using
>>> early_fdt_map() using PAGE_HYPERVISOR_RO which is
Hi Michal,
> On 26 Feb 2025, at 10:38, Orzel, Michal wrote:
>
>
>
> On 26/02/2025 09:36, Luca Fancellu wrote:
>>
>>
>> Currently the early stage of the Arm boot maps the DTB using
>> early_fdt_map() using PAGE_HYPERVISOR_RO which is cacheable
>> read-only memory, later during DTB relocation
On 26/02/2025 09:36, Luca Fancellu wrote:
>
>
> Currently the early stage of the Arm boot maps the DTB using
> early_fdt_map() using PAGE_HYPERVISOR_RO which is cacheable
> read-only memory, later during DTB relocation the function
> copy_from_paddr() is used to map pages in the same range on
Currently the early stage of the Arm boot maps the DTB using
early_fdt_map() using PAGE_HYPERVISOR_RO which is cacheable
read-only memory, later during DTB relocation the function
copy_from_paddr() is used to map pages in the same range on
the fixmap but using PAGE_HYPERVISOR_WC which is non-cachea
