[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150222162708.GA4327@infradead.org>
Date: Sun, 22 Feb 2015 08:27:08 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Boaz Harrosh <boaz@...xistor.com>
Cc: Dan Williams <dan.j.williams@...el.com>,
Matthew Wilcox <willy@...ux.intel.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@...1.01.org>,
"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
On Thu, Feb 19, 2015 at 11:25:37AM +0200, Boaz Harrosh wrote:
> I do not see why you need the nvdimm_type= kernel option at all.
>
> I have here a script that auto detects any NvDIMM. It works with all
> the chips that I have access to. And Also it has support for if you have
> memmap=sss\$aaa.
> For all these detected regions it will load a pmem device.
>
> It is easy to filter for any type of memory you want. What
> will the (annoying) kernel option give you?
>
> OK I might be jumping the guns, send the patch and I'll look
> at it.
The kernel option means we can autodetect the nvdimms in kernel space
with just that option set, no need for needing userspace setup.
How does your script / patch work?
I won't be back to my nvdimm enabled hardware until after LSF/MM,
so any work from me in this area will have to wait a bit.
--
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