Re: [XEN v2 03/11] xen/arm: domain_build: Replace use of paddr_t in find_domU_holes()

2023-01-20 Thread Julien Grall
On 20/01/2023 09:48, Julien Grall wrote: Hi, On 19/01/2023 23:02, Stefano Stabellini wrote: On Tue, 17 Jan 2023, Ayan Kumar Halder wrote: bankbase, banksize and bankend are used to hold values of type 'unsigned long long'. This can be represented as 'uint64_t' instead of 'paddr_t'. This wil

Re: [XEN v2 03/11] xen/arm: domain_build: Replace use of paddr_t in find_domU_holes()

2023-01-20 Thread Julien Grall
Hi, On 19/01/2023 23:02, Stefano Stabellini wrote: On Tue, 17 Jan 2023, Ayan Kumar Halder wrote: bankbase, banksize and bankend are used to hold values of type 'unsigned long long'. This can be represented as 'uint64_t' instead of 'paddr_t'. This will ensure consistency with allocate_static_mem

Re: [XEN v2 03/11] xen/arm: domain_build: Replace use of paddr_t in find_domU_holes()

2023-01-19 Thread Stefano Stabellini
On Tue, 17 Jan 2023, Ayan Kumar Halder wrote: > bankbase, banksize and bankend are used to hold values of type 'unsigned > long long'. This can be represented as 'uint64_t' instead of 'paddr_t'. > This will ensure consistency with allocate_static_memory() (where we use > 'uint64_t' for rambase and

[XEN v2 03/11] xen/arm: domain_build: Replace use of paddr_t in find_domU_holes()

2023-01-17 Thread Ayan Kumar Halder
bankbase, banksize and bankend are used to hold values of type 'unsigned long long'. This can be represented as 'uint64_t' instead of 'paddr_t'. This will ensure consistency with allocate_static_memory() (where we use 'uint64_t' for rambase and ramsize). In future, paddr_t can be used for 'uin32_t