Date: Mon, 03 Nov 2014 13:52:44 -0500 From: John Baldwin <jhb@freebsd.org> To: Sourish Mazumder <sourish@cloudbyte.com> Cc: freebsd-amd64@freebsd.org Subject: Re: memory type e820 Message-ID: <3381641.WgZAz21Lfu@pippin.baldwin.cx> In-Reply-To: <CABv3qbHQEFZiQ4p%2BHWZNLt0MiNnHBmDW1aTFhWB7vhr4J3BGfQ@mail.gmail.com> References: <CABv3qbEuggLT=9vsHAs5Rdp8a0V-=DG7DnPO1BQk4Ghn4r_9Dw@mail.gmail.com> <201410301353.05185.jhb@freebsd.org> <CABv3qbHQEFZiQ4p%2BHWZNLt0MiNnHBmDW1aTFhWB7vhr4J3BGfQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3381641.WgZAz21Lfu>