From: "Williams, Dan J" <dan.j.williams@intel.com>
To: "hch@infradead.org" <hch@infradead.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"luto@amacapital.net" <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: Cleaning up e820_pmem?
Date: Mon, 30 Nov 2015 18:11:12 +0000 [thread overview]
Message-ID: <1448907065.25710.0.camel@intel.com> (raw)
In-Reply-To: <CALCETrX_9WD=awMKLPoG81+W2K2gzWLSatbZr98w5m5-TujCzA@mail.gmail.com>
On Sun, 2015-11-29 at 22:26 -0800, Andy Lutomirski wrote:
> My laptop has /sys/devices/platform/e820_pmem and autoloads all the
> nvdimm infrastructure. While it would be really cool if my laptop
> had
> pmem, that's a bit of a pipe dream right now. (Even if it did have
> it, this laptop is brand new -- it should use NFIT, not e820_pmem.)
>
> Could we move the iomem_resource loop from drivers/nvdimm/e820.c to
> arch/x86/kernel/pmem.c and actually list the iomem resources the
> standard way as resources belonging to the platform device? That
> would match accepted practice, and it would keep the grossly
> x86-specific part of the driver in arch/x86. Then we could further
> tweak it to skip creating the platform device at all if there are no
> resources, and we'd avoid needlessly loading the module.
>
> I'd do this myself, except that my lovely machine that *does* support
> e820 pmem has been repurposed, so testing on a machine that actually
> supports this turd is awkward for me.
This works for me...
8<---
Subject: libnvdimm, e820: skip module loading when no type-12
From: Dan Williams <dan.j.williams@intel.com>
If there are no persistent memory ranges present then don't bother
creating the platform device. Otherwise, it loads the full libnvdimm
sub-system only to discover no resources present.
Reported-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
arch/x86/kernel/pmem.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/x86/kernel/pmem.c b/arch/x86/kernel/pmem.c
index 4f00b63d7ff3..14415aff1813 100644
--- a/arch/x86/kernel/pmem.c
+++ b/arch/x86/kernel/pmem.c
@@ -4,10 +4,22 @@
*/
#include <linux/platform_device.h>
#include <linux/module.h>
+#include <linux/ioport.h>
+
+static int found(u64 start, u64 end, void *data)
+{
+ return 1;
+}
static __init int register_e820_pmem(void)
{
+ char *pmem = "Persistent Memory (legacy)";
struct platform_device *pdev;
+ int rc;
+
+ rc = walk_iomem_res(pmem, IORESOURCE_MEM, 0, -1, NULL, found);
+ if (rc <= 0)
+ return 0;
/*
* See drivers/nvdimm/e820.c for the implementation, this is
next prev parent reply other threads:[~2015-11-30 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 6:26 Cleaning up e820_pmem? Andy Lutomirski
2015-11-30 18:11 ` Williams, Dan J [this message]
2015-11-30 19:02 ` Andy Lutomirski
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=1448907065.25710.0.camel@intel.com \
--to=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@amacapital.net \
--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