From: nikhil.subscribed@gmail.com (Nikhil Utane)
To: kernelnewbies@lists.kernelnewbies.org
Subject: memblock_reserve or memblock_remove to reserve a page
Date: Fri, 9 Sep 2016 14:59:14 +0530 [thread overview]
Message-ID: <CAGNWmJWNADXXgVesEOWw7xs1p9J241ZCD9VKoHWucDRRT4aa1w@mail.gmail.com> (raw)
In-Reply-To: <CAGNWmJXjAJpO_VX5ipdxijFOJk6dCCXXk0o1-bgk3M+ghzswfQ@mail.gmail.com>
Hi,
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?
-Thanks
Nikhil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160909/cabefec7/attachment-0001.html
next prev parent reply other threads:[~2016-09-09 9:29 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 [this message]
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
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=CAGNWmJWNADXXgVesEOWw7xs1p9J241ZCD9VKoHWucDRRT4aa1w@mail.gmail.com \
--to=nikhil.subscribed@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).