All of lore.kernel.org
 help / color / mirror / Atom feed
From: getarunks@gmail.com (Arun Sudhilal)
To: kernelnewbies@lists.kernelnewbies.org
Subject: memblock_reserve or memblock_remove to reserve a page
Date: Tue, 27 Sep 2016 16:14:45 +0530	[thread overview]
Message-ID: <CABOM9ZrsnTQU693eYp4Kr+Gz=iLtpw_EorXcA8viRLWmf3MwNw@mail.gmail.com> (raw)
In-Reply-To: <CAGNWmJXjAJpO_VX5ipdxijFOJk6dCCXXk0o1-bgk3M+ghzswfQ@mail.gmail.com>

Hello Nikhil,

On Fri, Sep 9, 2016 at 7:01 AM, Nikhil Utane
<nikhil.subscribed@gmail.com> wrote:
> I want to reserve a physical memory page with a fixed PFN. I do not want
> this page to be used by anyone else. I am calling memblock_reserve() to
> supposedly reserve the page. I am writing some content into this page. What
> I see is that during some runs the content of this page is modified (either
> fully or sometimes partially). In few runs, I see it as intact. Is it
> expected that even after calling memblock_reserve() the kernel can allocate
> this physical page for any other purpose? How is memblock_remove() different
> from memblock_reserve? I tried reading up but didn't see any useful
> information. What I understood is memblock_remove will completely remove
> from kernel's allocation mechanism. Should I then be using remove instead of
> reserve?

when a DT entry is added to  #reserved-memory node, what
drivers/of/fdt.c does is to call memblock_remove() and
memblock_reserve().
This happens after the memblock driver is initialized but before buddy
allocator up. Did you try this approach? This should work for you.

Only option once the kernel boot is complete is to try out the
technique what mm/memory_hotplug.c does while offline memory.
isolate_page_range and then migrate.

Regards,
Arun


>
> -Thanks
> Nikhil
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>

  parent reply	other threads:[~2016-09-27 10:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-09  1:31 memblock_reserve or memblock_remove to reserve a page Nikhil Utane
2016-09-09  9:29 ` Nikhil Utane
2016-09-11  0:38   ` Min-Hua Chen
2016-09-14  7:17     ` Nikhil Utane
2016-09-15  0:05       ` Min-Hua Chen
2016-09-15  8:23         ` Nikhil Utane
2016-09-15 23:22           ` Min-Hua Chen
2016-09-16 10:08             ` Nikhil Utane
2016-09-27 10:44 ` Arun Sudhilal [this message]
2016-09-28  9:11   ` Nikhil Utane
2016-09-28  9:42     ` Arun Sudhilal
2016-09-28 13:25       ` Nikhil Utane
2016-09-29  5:55         ` Nikhil Utane
2016-10-03 12:32         ` Arun Sudhilal
2016-10-03 12:45           ` Arun Sudhilal
2016-10-04  5:40             ` Nikhil Utane

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABOM9ZrsnTQU693eYp4Kr+Gz=iLtpw_EorXcA8viRLWmf3MwNw@mail.gmail.com' \
    --to=getarunks@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.