From: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Jeremy Kerr <jeremy.kerr@au1.ibm.com>
Subject: Re: [PATCH] powerpc/powernv: Fix vma page prot flags in opal-prd driver
Date: Thu, 25 Jun 2015 13:13:37 +0530 [thread overview]
Message-ID: <20150625074303.GB4233@dirshya.in.ibm.com> (raw)
In-Reply-To: <20150625061546.GA4233@dirshya.in.ibm.com>
* Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> [2015-06-25 11:45:46]:
[snip]
> Hi Ben,
>
> remap_pfn_range() is the correct method to map the firmware pages
> because we will not have struct page associated with this RAM area.
>
> We do a memblock_reserve() in early boot and take out this memory from
> kernel and avoid struct page allocation/init for these.
Kindly ignore the this comment. memblock_reserve() does not
prevent/avoid struct page allocation. We do have valid struct page
which can be used for mapping.
--Vaidy
prev parent reply other threads:[~2015-06-25 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 18:26 [PATCH] powerpc/powernv: Fix vma page prot flags in opal-prd driver Vaidyanathan Srinivasan
2015-06-25 6:15 ` Vaidyanathan Srinivasan
2015-06-25 7:43 ` Vaidyanathan Srinivasan [this message]
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=20150625074303.GB4233@dirshya.in.ibm.com \
--to=svaidy@linux.vnet.ibm.com \
--cc=jeremy.kerr@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.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).