From: Ingo Molnar <mingo@kernel.org>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Matthew Wilcox <willy@linux.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@lists.01.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
Date: Thu, 19 Feb 2015 11:30:47 +0100 [thread overview]
Message-ID: <20150219103046.GB2819@gmail.com> (raw)
In-Reply-To: <54E5BA90.3010609@plexistor.com>
* Boaz Harrosh <boaz@plexistor.com> wrote:
> Do you require another redundant message who's purpose is to scare
> people off, like:
>
> e820: WARN [mem 0x0000000100000000-0x000000017fffffff] is unknown type 12
>
> Sure I'll add it
That message looks useful (and not very scary), and also
emit a warning if such a region is then claimed by a
driver.
This puts some pressure on both the firmware and the kernel
side to get their act together, without holding
functionality hostage.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Matthew Wilcox <willy@linux.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>
Subject: Re: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
Date: Thu, 19 Feb 2015 11:30:47 +0100 [thread overview]
Message-ID: <20150219103046.GB2819@gmail.com> (raw)
In-Reply-To: <54E5BA90.3010609@plexistor.com>
* Boaz Harrosh <boaz@plexistor.com> wrote:
> Do you require another redundant message who's purpose is to scare
> people off, like:
>
> e820: WARN [mem 0x0000000100000000-0x000000017fffffff] is unknown type 12
>
> Sure I'll add it
That message looks useful (and not very scary), and also
emit a warning if such a region is then claimed by a
driver.
This puts some pressure on both the firmware and the kernel
side to get their act together, without holding
functionality hostage.
Thanks,
Ingo
next prev parent reply other threads:[~2015-02-19 10:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 11:07 [PATCH 0/2] e820: Fix handling of NvDIMM chips Boaz Harrosh
2015-02-16 11:07 ` Boaz Harrosh
2015-02-16 11:13 ` [PATCH 1/2] e820: Don't let unknown DIMM type come out BUSY Boaz Harrosh
2015-02-16 11:13 ` Boaz Harrosh
2015-02-16 11:16 ` [RFC 2/2] e820: Add the NvDIMM Memory type (type-12) Boaz Harrosh
2015-02-16 11:16 ` Boaz Harrosh
2015-02-16 11:24 ` [PATCH 3/3] pmem: Allow request_mem to fail, (CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET) Boaz Harrosh
2015-02-16 11:24 ` Boaz Harrosh
2015-02-17 20:52 ` Ross Zwisler
2015-02-17 20:52 ` Ross Zwisler
2015-02-18 9:58 ` Boaz Harrosh
2015-02-18 9:58 ` Boaz Harrosh
2015-02-16 22:03 ` [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips Matthew Wilcox
2015-02-16 22:03 ` Matthew Wilcox
2015-02-17 8:42 ` Boaz Harrosh
2015-02-17 8:42 ` Boaz Harrosh
2015-02-18 18:15 ` Dan Williams
2015-02-18 18:15 ` Dan Williams
2015-02-18 18:30 ` Ingo Molnar
2015-02-18 18:30 ` Ingo Molnar
2015-02-18 18:44 ` Dan Williams
2015-02-18 18:44 ` Dan Williams
2015-02-18 18:53 ` Ingo Molnar
2015-02-18 18:53 ` Ingo Molnar
2015-02-18 19:18 ` Dan Williams
2015-02-18 19:18 ` Dan Williams
2015-02-18 19:27 ` Ingo Molnar
2015-02-18 19:27 ` Ingo Molnar
2015-02-18 19:35 ` Dan Williams
2015-02-18 19:35 ` Dan Williams
2015-02-19 10:27 ` Boaz Harrosh
2015-02-19 10:27 ` Boaz Harrosh
2015-02-19 10:30 ` Ingo Molnar [this message]
2015-02-19 10:30 ` Ingo Molnar
2015-02-19 0:47 ` Christoph Hellwig
2015-02-19 1:03 ` Dan Williams
2015-02-19 10:01 ` Ingo Molnar
2015-02-19 10:29 ` Boaz Harrosh
2015-02-19 10:31 ` Ingo Molnar
2015-02-19 10:40 ` Boaz Harrosh
2015-02-19 9:25 ` Boaz Harrosh
2015-02-22 16:27 ` Christoph Hellwig
2015-02-22 17:05 ` Boaz Harrosh
2015-02-22 17:15 ` 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=20150219103046.GB2819@gmail.com \
--to=mingo@kernel.org \
--cc=boaz@plexistor.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.