From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
"Roger C. Pao" <rcpao.enmotus@gmail.com>,
Dan Williams <dan.j.williams@intel.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: [PATCH 3/3] pmem: Allow request_mem to fail, (CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET)
Date: Tue, 17 Feb 2015 13:52:13 -0700 [thread overview]
Message-ID: <1424206333.12687.8.camel@theros.lm.intel.com> (raw)
In-Reply-To: <54E1D36B.4000905@plexistor.com>
On Mon, 2015-02-16 at 13:24 +0200, Boaz Harrosh wrote:
> With old Kernels there was a bug in x86 where any unknown
> memory chip type would come up BUSY when calling
> request_mem_region_exclusive().
>
> So for pmem to work with old Kernels and real NvDIMM chips
> we have a new Kconfig option CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET.
>
> People have been running with hacked up pmem that will ignore
> the return code from request_mem_region_exclusive. So here it is
> official
>
> Signed-off-by: Boaz Harrosh <boaz@plexistor.com>
I'm confused - I thought that this behavior was fixed by patch 1/3?
With that patch this memory reservation should not fail, correct?
If so, why do we need this patch?
> ---
> drivers/block/Kconfig | 12 ++++++++++++
> drivers/block/pmem.c | 11 +++++++----
> 2 files changed, 19 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
> index 3b3200f..10879b8 100644
> --- a/drivers/block/Kconfig
> +++ b/drivers/block/Kconfig
> @@ -430,6 +430,18 @@ config BLK_DEV_PMEM_USE_PAGES
> to other devices in the system, then you must say "Yes" here.
> If unsure leave as Yes.
>
> +config BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET
> + bool "Ignore the return code from request_mem_region_exclusive"
> + depends on BLK_DEV_PMEM
> + help
> + In Old Kernels type-12 Memory type which is used by NvDIMM
> + chips Comes out busy when calling request_mem_region_exclusive,
> + because of a bug.
> + If this option is set to "yes". The pmem will ignore the
> + failure, and continue as usual. If you have an old Kernel and
> + a real NvDIMM chip you must say yes here.
> + (Ignored if BLK_DEV_PMEM_USE_PAGES=y)
> +
> config CDROM_PKTCDVD
> tristate "Packet writing on CD/DVD media"
> depends on !UML
> diff --git a/drivers/block/pmem.c b/drivers/block/pmem.c
> index 9eb7ffe..f84d033 100644
> --- a/drivers/block/pmem.c
> +++ b/drivers/block/pmem.c
> @@ -197,10 +197,12 @@ int pmem_mapmem(struct pmem_device *pmem)
>
> res_mem = request_mem_region_exclusive(pmem->phys_addr, pmem->size,
> "pmem");
> - if (!res_mem) {
> + if (unlikely(!res_mem)) {
> pr_warn("pmem: request_mem_region_exclusive phys=0x%llx size=0x%zx failed\n",
> - pmem->phys_addr, pmem->size);
> - return -EINVAL;
> + pmem->phys_addr, pmem->size);
> +#ifndef CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET
> + return -EBUSY;
> +#endif
> }
>
> pmem->virt_addr = ioremap_cache(pmem->phys_addr, pmem->size);
> @@ -211,7 +213,8 @@ int pmem_mapmem(struct pmem_device *pmem)
> return 0;
>
> out_release:
> - release_mem_region(pmem->phys_addr, pmem->size);
> + if (res_mem)
> + release_mem_region(pmem->phys_addr, pmem->size);
> return err;
> }
>
next prev parent reply other threads:[~2015-02-17 20:52 UTC|newest]
Thread overview: 27+ 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:13 ` [PATCH 1/2] e820: Don't let unknown DIMM type come out BUSY Boaz Harrosh
2015-02-16 11:16 ` [RFC 2/2] e820: Add the NvDIMM Memory type (type-12) 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-17 20:52 ` Ross Zwisler [this message]
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-17 8:42 ` Boaz Harrosh
2015-02-18 18:15 ` Dan Williams
2015-02-18 18:30 ` Ingo Molnar
2015-02-18 18:44 ` Dan Williams
2015-02-18 18:53 ` Ingo Molnar
2015-02-18 19:18 ` Dan Williams
2015-02-18 19:27 ` Ingo Molnar
2015-02-18 19:35 ` Dan Williams
2015-02-19 10:27 ` Boaz Harrosh
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=1424206333.12687.8.camel@theros.lm.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=boaz@plexistor.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@redhat.com \
--cc=rcpao.enmotus@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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).