Fix a bug and cleanup NUMA boot-time code
Get series with b4
b4 am 20081209182130.DB2150A2@kernelVersions newest first
- v1 Latest8 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/8 | fix bootmem reservation on uninitialized nodearch/ | +9 | 3 replies | |
| 2/8 | Add better comment on careful_allocation()arch/ | +10 | 0 replies | |
| 3/8 | cleanup careful_allocation(): bootmem already panicsarch/ | +1 | 0 replies | |
| 4/8 | make careful_allocation() return vaddrsarch/ | +20 | 0 replies | |
| 5/8 | cleanup careful_allocation(): consolidate memset()arch/ | +5 | 0 replies | |
| 6/8 | cleanup do_init_bootmem()arch/ | +55 | 2 replies | |
| 7/8 | less use of NODE_DATA()arch/ | +31 | 1 reply | |
| 8/8 | make free_bootmem_with_active_regions() take pgdatarch/ arch/ arch/ +8 more | +18 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/8] Fix a bug and cleanup NUMA boot-time code
The first patch in this series is a genuine bug fix. The rest are really just an RFC.
Jon introduced a bug a while ago. I introduced another when trying to fix Jon's bug. I refuse to accept personal blame for this and, instead, blame the code. :)
The reset of the series are "cleanups" that I think will help clarify the code in numa.c and work to ensure that the next bonehead like me is not as able to easily muck up the code. :)
The cleanups increase in impact and intrusiveness as the series goes along, so please consider them an RFC. But, what I really want to figure out is a safer way to initialize NODE_DATA() and start using it as we bring up bootmem on all the nodes.