linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Nicholas Piggin <npiggin@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 2/2] x86/selftests: Add test for mapping placement for 5-level paging
Date: Wed, 22 Nov 2017 11:11:47 +0300	[thread overview]
Message-ID: <20171122081147.5gjushlstmnnmlev@node.shutemov.name> (raw)
In-Reply-To: <87y3myzx7z.fsf@linux.vnet.ibm.com>

On Wed, Nov 22, 2017 at 11:11:36AM +0530, Aneesh Kumar K.V wrote:
> "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> writes:
> 
> > With 5-level paging, we have 56-bit virtual address space available for
> > userspace. But we don't want to expose userspace to addresses above
> > 47-bits, unless it asked specifically for it.
> >
> > We use mmap(2) hint address as a way for kernel to know if it's okay to
> > allocate virtual memory above 47-bit.
> >
> > Let's add a self-test that covers few corner cases of the interface.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> 
> Can we move this to selftest/vm/ ? I had a variant which i was using to
> test issues on ppc64. One change we did recently was to use >=128TB as
> the hint addr value to select larger address space. I also would like to
> check for exact mmap return addr in some case. Attaching below the test
> i was using. I will check whether this patch can be updated to test what
> is converted in my selftest. I also want to do the boundary check twice.
> The hash trasnslation mode in POWER require us to track addr limit and
> we had bugs around address space slection before and after updating the
> addr limit.

Feel free to move it to selftest/vm. I don't have time to test setup and
test it on Power myself, but this would be great.

-- 
 Kirill A. Shutemov

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-11-22  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 14:36 [PATCHv3 1/2] x86/mm: Prevent non-MAP_FIXED mapping across DEFAULT_MAP_WINDOW border Kirill A. Shutemov
2017-11-15 14:36 ` [PATCHv3 2/2] x86/selftests: Add test for mapping placement for 5-level paging Kirill A. Shutemov
2017-11-22  5:41   ` Aneesh Kumar K.V
2017-11-22  8:11     ` Kirill A. Shutemov [this message]
2017-11-22 11:36       ` Aneesh Kumar K.V
2017-11-22 12:40         ` Kirill A. Shutemov
2017-11-16 13:23 ` [PATCHv3 1/2] x86/mm: Prevent non-MAP_FIXED mapping across DEFAULT_MAP_WINDOW border Michal Hocko

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=20171122081147.5gjushlstmnnmlev@node.shutemov.name \
    --to=kirill@shutemov.name \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hpa@zytor.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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).