From owner-freebsd-amd64@FreeBSD.ORG  Mon Nov  3 21:53:12 2014
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5AB19E81
 for <freebsd-amd64@freebsd.org>; Mon,  3 Nov 2014 21:53:12 +0000 (UTC)
Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 32E98F6D
 for <freebsd-amd64@freebsd.org>; Mon,  3 Nov 2014 21:53:12 +0000 (UTC)
Received: from pippin.baldwin.cx (unknown [129.253.54.225])
 by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4066DB945;
 Mon,  3 Nov 2014 16:53:11 -0500 (EST)
From: John Baldwin <jhb@freebsd.org>
To: Sourish Mazumder <sourish@cloudbyte.com>
Subject: Re: memory type e820
Date: Mon, 03 Nov 2014 13:52:44 -0500
Message-ID: <3381641.WgZAz21Lfu@pippin.baldwin.cx>
User-Agent: KMail/4.14.2 (FreeBSD/11.0-CURRENT; KDE/4.14.2; amd64; ; )
In-Reply-To: <CABv3qbHQEFZiQ4p+HWZNLt0MiNnHBmDW1aTFhWB7vhr4J3BGfQ@mail.gmail.com>
References: <CABv3qbEuggLT=9vsHAs5Rdp8a0V-=DG7DnPO1BQk4Ghn4r_9Dw@mail.gmail.com>
 <201410301353.05185.jhb@freebsd.org>
 <CABv3qbHQEFZiQ4p+HWZNLt0MiNnHBmDW1aTFhWB7vhr4J3BGfQ@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7
 (bigwig.baldwin.cx); Mon, 03 Nov 2014 16:53:11 -0500 (EST)
Cc: freebsd-amd64@freebsd.org
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Nov 2014 21:53:12 -0000

On Saturday 01 November 2014 18:55:53 Sourish Mazumder wrote:
> Hi John,
> 
> I tried the pmap_mapdev() as suggested by you. Works perfectly. Thanks for
> the information.

Sure.

> What is required, If I want to add this nvram memory to VM pages?

Hmm.  If this is device memory you generally don't want that.  I'm not 
actually sure how to do this at runtime.  If you don't mind having a local
hack you can add a change in the MD startup code (e.g. in hammer_time()
in sys/amd64/amd64/machdep.c) to adjust the ranges added to
phys_avail[] and dump_avail[].

-- 
John Baldwin