Hi Peter, On Fri, Feb 19, 2021 at 9:11 PM Peter Maydell <[email protected]> wrote: > > On Fri, 19 Feb 2021 at 12:52, Bin Meng <[email protected]> wrote: > > > > From: Bin Meng <[email protected]> > > > > Currently machine->ram_size is a ram_addr_t, whose size is 64 bits > > if either (a) the host is 64 bits or (b) CONFIG_XEN_BACKEND is > > enabled, so it's effectively only 32 bits on 32-bit-not-x86. > > > > commit 4be403c8158e ("Make target_phys_addr_t 64 bits unconditionally") > > did the change for target_phys_addr_t which is now hwaddr to be 64 bits > > unconditionally. Let's do the same to ram_addr_t. > > > > Suggested-by: Peter Maydell <[email protected]> > > Signed-off-by: Bin Meng <[email protected]> > > -- > > As noted on the other thread, I like this in principle, > but I think it would be interesting to check whether it > has a measurable perf impact on the non-x86-32-bit hosts > that it affects.
What measures should we take to move this on? I don't have any access to non-x86 32-bit hosts. Regards, Bin
