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

Re: [XEN v2 05/11] xen/arm: Use paddr_t instead of u64 for address/size



Hi,

On 17/01/2023 17:43, Ayan Kumar Halder wrote:
One should now be able to use 'paddr_t' to represent address and size.
Consequently, one should use 'PRIpaddr' as a format specifier for paddr_t.

Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@xxxxxxx>
---

Changes from -

v1 - 1. Rebased the patch.

  xen/arch/arm/domain_build.c        |  9 +++++----
  xen/arch/arm/gic-v3.c              |  2 +-
  xen/arch/arm/platforms/exynos5.c   | 26 +++++++++++++-------------
  xen/drivers/char/exynos4210-uart.c |  2 +-
  xen/drivers/char/ns16550.c         |  8 ++++----
  xen/drivers/char/omap-uart.c       |  2 +-
  xen/drivers/char/pl011.c           |  4 ++--
  xen/drivers/char/scif-uart.c       |  2 +-
  xen/drivers/passthrough/arm/smmu.c |  6 +++---
  9 files changed, 31 insertions(+), 30 deletions(-)

diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index 72b9afbb4c..cf8ae37a14 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -1666,7 +1666,7 @@ static int __init find_memory_holes(const struct 
kernel_info *kinfo,
      dt_for_each_device_node( dt_host, np )
      {
          unsigned int naddr;
-        u64 addr, size;
+        paddr_t addr, size;

Without the next patch, this change is incorrect because dt_device_get_address() expects a 64-bit value rather than paddr_t.

So the type change wants to be moved in the next patch. The same goes for any variable you modifed in this patch used by dt_device_get_address().

Cheers,

--
Julien Grall



 


Rackspace

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