Globally defining phys_addr_t
Status from this message: i've applied your patchset to tip/core/resources:
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | add phys_addr_t for holding physical addressesarch/ arch/ arch/ +4 more | +15 | 0 replies | |
| 2/3 | make PFN_PHYS explicitly return phys_addr_tarch/ include/ include/ | +9 | 0 replies | |
| 3/3 | redefine resource_size_t as phys_addr_tarch/ arch/ arch/ +3 more | +13 | 2 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Globally defining phys_addr_t
Hi Ingo,
This is a repost of a little 3-patch series which Andrew has been carrying in -mm. It cleans up the definition of phys_addr_t to make it kernel-wide rather than x86-specific, and fixes up PFN_PHYS() to use it to avoid address truncation.
We currently have a few workarounds for this problem in the tree, but Alex found another bug caused by PFN_PHYS(), so it's probably better if you bring these patches into tip.git for now.
PowerPC also defines a phys_addr_t with the same meaning as x86; the powerpc arch maintainers are happy with these patches.
The third patch in the series is not necessary to fix any bug, but it removes the separate definition of resource_size_t to define it in terms of phys_addr_t. I include it for competeness.
Thanks,
J