All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
	Michal Suchanek <msuchanek@suse.de>,
	linuxppc-dev@lists.ozlabs.org
Cc: "'Kirill A. Shutemov'" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] selftests/powerpc/mm: Add a test for virtual address mapping
Date: Tue, 18 Apr 2017 13:47:54 +1000	[thread overview]
Message-ID: <87y3uy74wl.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <adcab8f9-8c11-0678-a87f-8adb80d58a67@linux.vnet.ibm.com>

Anshuman Khandual <khandual@linux.vnet.ibm.com> writes:

> On 04/15/2017 01:48 AM, Michal Suchanek wrote:
>> Hello,
>> 
>> On Wed, 12 Apr 2017 15:11:12 +0530
>> Anshuman Khandual <khandual@linux.vnet.ibm.com> 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.
>> 
>> This description does not mention anything PPC specific. Can this be
>> generalized to work with Intel L5 enabled kernel as well?
>
> Hmm, I am not completely aware about the proposed mmap interface
> for 128TB and beyond till 512TB by Kirill on x86. If both powerpc
> and x86 will have the same semantics, then this test is generic
> enough to cover both the architectures and will move it into
> selftests/vm/ instead of current selftests/powerpc/mm.

I think it can be made generic, maybe it needs a few #ifdefs, but that's
fine for a selftest.

So yeah if you can move it to selftests/vm I think that would be better.

cheers

  reply	other threads:[~2017-04-18  3:47 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
2017-04-14 20:18 ` Michal Suchanek
2017-04-17  3:41   ` Anshuman Khandual
2017-04-18  3:47     ` Michael Ellerman [this message]
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=87y3uy74wl.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    /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.