> that seems not right. > > for x86, setup_log_buf(1) is quite early called in setup_arch() before > bootmem is there. > > bootmem should be killed after memblock is supported for arch that > current support bootmem. Hmm. x86 uses nobootmem.c, which implements bootmem in terms of memblock anyway. It is definitely working at setup_log_buf() time (or else it wouldn't be able to select a sensible buffer location). I suppose you're saying that it wouldn't work for a hypothetical architecture that *does* support bootmem and *also* supports setup_log_buf(1). Will there ever be such an architecture, or will bootmem be retired first? Thanks, Avery -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>