[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <54EA0EAE.70708@plexistor.com>
Date: Sun, 22 Feb 2015 19:15:26 +0200
From: Boaz Harrosh <boaz@...xistor.com>
To: Christoph Hellwig <hch@...radead.org>
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 02/22/2015 07:05 PM, Boaz Harrosh wrote:
> On 02/22/2015 06:27 PM, Christoph Hellwig wrote:
<>
>> 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.
>>
<>
BTW: I have an out-of-tree patch that enables me to just emulate
an NvDIMM inside a VM, so I can develop at the comfort of my LP.
You can find it at my pmem tree.
All it does is adds a new type of memmap=. So if you specify memmap=2G\&4G on
Kernel command-line the code will insert a type-12 memory to the list, instead of "reserved"
region when a "$" is parsed.
>From here on that region will look exactly like an DDR3-NvDIMM with
supporting BIOS to the system, safe the persistence of course.
(Actually there is a trick to force the KVM-Host to reserve that memory
across VM boots, to emulate persistence)
Cheers
Boaz
--
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