From: Ingo Molnar <mingo@kernel.org>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
x86@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
"Roger C. Pao" <rcpao.enmotus@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-nvdimm <linux-nvdimm@ml01.01.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Matthew Wilcox <willy@linux.intel.com>,
Andy Lutomirski <luto@amacapital.net>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 1/3] e820: Don't let unknown DIMM type come out BUSY
Date: Tue, 24 Feb 2015 09:34:32 +0100 [thread overview]
Message-ID: <20150224083432.GB19398@gmail.com> (raw)
In-Reply-To: <54EC2F4E.1080606@plexistor.com>
* Boaz Harrosh <boaz@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.
Later on, if it turns out to be benign, we can remove the
warning.
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-24 8:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 12:29 [PATCH 0/3 v2] e820: Fix handling of NvDIMM chips Boaz Harrosh
2015-02-23 12:33 ` [PATCH 1/3] e820: Don't let unknown DIMM type come out BUSY Boaz Harrosh
2015-02-24 4:22 ` Dan Williams
2015-02-24 7:59 ` Boaz Harrosh
2015-02-24 8:34 ` Ingo Molnar [this message]
2015-02-24 8:51 ` Boaz Harrosh
2015-02-26 2:09 ` Dan Williams
2015-02-23 12:43 ` [PATCH 2/3] resource: Add new flag IORESOURCE_WARN (64bit) Boaz Harrosh
2015-02-23 15:46 ` Andy Lutomirski
2015-02-24 7:20 ` Boaz Harrosh
2015-02-24 19:58 ` Andy Lutomirski
2015-02-24 8:39 ` [PATCH 2/3 v3] resource: Add new flag IORESOURCE_MEM_WARN Boaz Harrosh
2015-02-24 8:44 ` Boaz Harrosh
2015-02-24 9:06 ` Ingo Molnar
2015-02-24 9:08 ` Boaz Harrosh
2015-02-24 9:07 ` Ingo Molnar
2015-02-24 9:09 ` Boaz Harrosh
2015-02-24 15:00 ` [PATCH 2/3 v4] " Boaz Harrosh
2015-02-24 17:04 ` Dan Williams
2015-02-25 6:36 ` Boaz Harrosh
2015-02-23 12:46 ` [PATCH 3A/3 good] e820: Add the unknown-12 Memory type (DDR3-NvDIMM) Boaz Harrosh
2015-02-23 15:48 ` Andy Lutomirski
2015-02-23 12:48 ` [PATCH 3B/3 fat] e820: dynamic unknown-xxx names (for DDR3-NvDIMM) Boaz Harrosh
2015-02-23 15:49 ` Andy Lutomirski
2015-02-24 7:38 ` Boaz Harrosh
2015-02-25 10:22 ` [PATCH 0/3 v2] e820: Fix handling of NvDIMM chips Ingo Molnar
2015-02-25 14:42 ` Boaz Harrosh
-- strict thread matches above, loose matches on Subject: below --
2015-03-05 10:16 [PATCH 0/3 v5] " Boaz Harrosh
2015-03-05 10:20 ` [PATCH 1/3] e820: Don't let unknown DIMM type come out BUSY Boaz Harrosh
2015-03-05 20:41 ` Dan Williams
2015-03-09 10:54 ` Boaz Harrosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150224083432.GB19398@gmail.com \
--to=mingo@kernel.org \
--cc=boaz@plexistor.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--cc=mingo@redhat.com \
--cc=rcpao.enmotus@gmail.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=willy@linux.intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).