[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150224083432.GB19398@gmail.com>
Date: Tue, 24 Feb 2015 09:34:32 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Boaz Harrosh <boaz@...xistor.com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Ingo Molnar <mingo@...hat.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>, x86@...nel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
"Roger C. Pao" <rcpao.enmotus@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-nvdimm <linux-nvdimm@...ts.01.org>,
"H. Peter Anvin" <hpa@...or.com>,
Matthew Wilcox <willy@...ux.intel.com>,
Andy Lutomirski <luto@...capital.net>,
Christoph Hellwig <hch@...radead.org>
Subject: Re: [PATCH 1/3] e820: Don't let unknown DIMM type come out BUSY
* Boaz Harrosh <boaz@...xistor.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.
Later on, if it turns out to be benign, we can remove the
warning.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists