linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com, Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] selftests/powerpc/mm: Add a test for virtual address mapping
Date: Fri, 14 Apr 2017 18:58:44 +0530	[thread overview]
Message-ID: <fb110fed-60f0-858c-af74-9b59672262f8@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170412094112.13181-1-khandual@linux.vnet.ibm.com>

On 04/12/2017 03:11 PM, Anshuman Khandual wrote:
> This verifies virtual address mapping below and above the
> 128TB range and makes sure that address returned are within
> the expected range depending upon the hint passed from the
> user space.
> 
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
> ---
> Tested this on latest ppc-next with Aneesh's yesterday's patch
> which can be found at https://patchwork.ozlabs.org/patch/749510/

Hello Aneesh/Michael,

Does this look okay as a small singular test for below and above
the 128TB range allocations ? Or do you think some thing else needs
to be added here as well.

Regards
Anshuman

  reply	other threads:[~2017-04-14 13:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:41 [PATCH] selftests/powerpc/mm: Add a test for virtual address mapping Anshuman Khandual
2017-04-14 13:28 ` Anshuman Khandual [this message]
2017-04-14 20:18 ` Michal Suchanek
2017-04-17  3:41   ` Anshuman Khandual
2017-04-18  3:47     ` Michael Ellerman
2017-04-17  5:26 ` Aneesh Kumar K.V
2017-04-18  2:53   ` 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=fb110fed-60f0-858c-af74-9b59672262f8@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).