Re: [RFC PATCH 2/3] support for broken memory modules (BadRAM)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> You're right, logging every page marked would be too verbose. That's why
> I wrapped that logging into pr_debug.

pr_debug still floods the kernel log buffer. On large systems
it often already overflows.

> However I kept the printk in the case of early allocated pages. The user
> should be notified of the attempt to mark a page that's already been
> allocated by the kernel itself.

That's ok, although if you're unlucky (e.g. hit a large mem_map area)
it can be also very nosiy.

It would be better if you fixed the printks to output ranges.

-Andi

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx  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>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]