On 02/24/2015 10:34 AM, Ingo Molnar wrote: > > * Boaz Harrosh <b...@plexistor.com> wrote: > >> On 02/24/2015 06:22 AM, Dan Williams wrote: >> <> >>>> By Popular demand An Extra WARNING message is printed if >>>> an "UNKNOWN" is found. It will look like this: >>>> e820: WARNING [mem 0x100000000-0x1ffffffff] is unknown type 12 >>> >>> I don't think we need to warn that an unknown range was >>> published, just warn if it is consumed. >> >> I did not have it at first, Ingo asked for it. I don't >> mind having it and I don't mind not. I'd say it is Ingo's >> call. > > So at least initially I really would like system operators > to be informed when the BIOS does something unexpected to > the kernel, especially when it comes to memory mappings. >
OK, yes makes sense. > Later on, if it turns out to be benign, we can remove the > warning. > OK So here it is, with this one patch we are back to business. If we want the warning on lock than we have the 2nd patch, Any version you like. And please, please lets also put in the 3A/3 patch so we can positively scan for specifically these chips in /proc/iomem instead of blindly try any "reserved-unknown" types. > Thanks, > > Ingo Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
