Allow late mdesc detection, v4
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] Allow late mdesc detection, v4
Quoted 11 lines · Jeremy Kerr
Currently, we probe for a mdesc early in boot. At this early stage, the only thing we use the mdesc for is to determine the debug page mapping.
However, the debug addresses (phys and virt) need to be coded into the addruart macro anyway; the dynamic probing is only going to tell us what we already know.
These changes allow us to use the addruart macros to find the debug mapping addresses, rather than pulling them out of the mdesc. This means that the addresses are only kept in the one place, and that we don't need the mdesc nearly as early.
I fear that to merge them into my tree now will invite merge conflicts and/or code breakage when something gets merged without regard to these changes. As I said last time around, the point to merge these (as newly updated patches) is once we freeze new platform support just before the next merge window.
So I'm not merging them until the potential last week prior to the merge window opening - please keep an eye on Linus' -rc announcements and send updated patches (against my -devel tree - this is one case where we're going to have to do it this way) to the patch system at when Linus indicates that he's released the final -rc.
Thanks.