|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 1/3] xen/arm: fix nr_pdxs calculation
Hi Stefano, On 5/8/19 11:47 PM, Stefano Stabellini wrote: pfn_to_pdx expects an address, not a size, as a parameter. It expects the end address, and the masks calculations compensate for any holesbetween start and end. Pass the end address to pfn_to_pdx. The wording is a bit difficult to read. Don't you miss a "So" or "Therefore" somewhere? Also remove s/remove/substract/? from the result pfn_to_pdx(start_address) because we know that we don't need to cover any memory in the range 0-start in the frametable. The only reason we can substract pfn_to_pdx(start_address) here is because we store the initial PDX in frametable_base_pdx. Without that, the frametable would need to cover the range 0 - start. The code looks good to me. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |