From: Michael Ellerman <mpe@ellerman•id.au>
To: Anshuman Khandual <khandual@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org
Cc: aneesh.kumar@linux•vnet.ibm.com
Subject: Re: [PATCH V2] powerpc/mm: Add validation for platform reserved memory ranges
Date: Mon, 11 Apr 2016 23:31:58 +1000 [thread overview]
Message-ID: <1460381518.32475.0.camel@ellerman.id.au> (raw)
In-Reply-To: <570B4093.1010600@linux.vnet.ibm.com>
On Mon, 2016-04-11 at 11:43 +0530, Anshuman Khandual wrote:
> On 03/07/2016 03:25 PM, Anshuman Khandual wrote:
> > For partition running on PHYP, there can be a adjunct partition
> > which shares the virtual address range with the operating system.
> > Virtual address ranges which can be used by the adjunct partition
> > are communicated with virtual device node of the device tree with
> > a property known as "ibm,reserved-virtual-addresses". This patch
> > introduces a new function named 'validate_reserved_va_range' which
> > is called during initialization to validate that these reserved
> > virtual address ranges do not overlap with the address ranges used
> > by the kernel for all supported memory contexts. This helps prevent
> > the possibility of getting return codes similar to H_RESOURCE for
> > H_PROTECT hcalls for conflicting HPTE entries.
> >
> > Signed-off-by: Anshuman Khandual <khandual@linux•vnet.ibm.com>
> > ---
> > - Tested on both POWER8 LE and BE platforms
> >
> > Changes in V2:
> > - Added braces to the definition of LINUX_VA_BITS
> > - Adjusted tabs as spaces for the definition of PARTIAL_LINUX_VA_MASK
>
> mpe, any updates on this ?
I'm just starting to look at things for next. So will try and get to it this
week.
cheers
next prev parent reply other threads:[~2016-04-11 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 9:55 [PATCH V2] powerpc/mm: Add validation for platform reserved memory ranges Anshuman Khandual
2016-04-11 6:13 ` Anshuman Khandual
2016-04-11 13:31 ` Michael Ellerman [this message]
2016-07-05 1:55 ` Michael Ellerman
2016-07-14 3:29 ` Anshuman Khandual
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=1460381518.32475.0.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=aneesh.kumar@linux$(echo .)vnet.ibm.com \
--cc=khandual@linux$(echo .)vnet.ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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