From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boaz Harrosh Subject: Re: another pmem variant V2 Date: Tue, 31 Mar 2015 13:31:34 +0300 Message-ID: <551A7786.3060908@plexistor.com> References: <1427358764-6126-1-git-send-email-hch@lst.de> <55143A8B.2060304@plexistor.com> <20150331092526.GA25958@lst.de> <551A762A.7090307@plexistor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, ross.zwisler@linux.intel.com, axboe@kernel.dk To: Christoph Hellwig Return-path: Received: from mail-wg0-f45.google.com ([74.125.82.45]:36656 "EHLO mail-wg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752540AbbCaKbh (ORCPT ); Tue, 31 Mar 2015 06:31:37 -0400 Received: by wgra20 with SMTP id a20so13933049wgr.3 for ; Tue, 31 Mar 2015 03:31:36 -0700 (PDT) In-Reply-To: <551A762A.7090307@plexistor.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 03/31/2015 01:25 PM, Boaz Harrosh wrote: > On 03/31/2015 12:25 PM, Christoph Hellwig wrote: <> > The problem I see is that if I state a memmap=nn!aa that crosses a NUMA > boundary then the machine will not boot. > So BTW for sure I need that "don't merge E820_PMEM ranges" patch because > otherwise I will not be able to boot if I have pmem on both NUMA nodes > and they happen to be contiguous. > BTW if you need NUMA emulated in your KVM add the below to your virsh edit .... memory= is in KiB only The sum of these must exactly match what you have for 8388608 8388608 And you probably already have say: Cheers Boaz