All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, Greg Kurz <gkurz@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH] mmap-alloc: use same backend for all mappings
Date: Tue, 01 Dec 2015 17:45:27 +0530	[thread overview]
Message-ID: <87vb8i2wm8.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <20151201125659-mutt-send-email-mst@redhat.com>

"Michael S. Tsirkin" <mst@redhat.com> writes:

> On Tue, Dec 01, 2015 at 04:23:11PM +0530, Aneesh Kumar K.V wrote:
>> "Michael S. Tsirkin" <mst@redhat.com> writes:
>> 
>> > On Mon, Nov 30, 2015 at 02:46:31PM +0100, Greg Kurz wrote:
>> >> On Mon, 30 Nov 2015 15:06:33 +0200
>> >> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>> >> 
>> 
>> 
>> ....
>> >> 
>> >> On ppc64, the address space is divided in 256MB-sized segments where all pages
>> >> have the same size. This is a hw limitation IIUC. I don't know if it can be
>> >> fixed and I'll let Ben comment on it.
>> >
>> > But it's anonymous memory with PROT_NONE.  There should be no pages there:
>> > just a chunk of virtual memory reserved.
>> >
>> 
>> ppc64 use page size (called as base page size) to find the hash slot in
>> which we find the virtual address to real address translation. All the
>> pages in a segment should have same base page size. Hugetlb pages have a
>> base page size of 16M whereas a regular linux page have 64K. mmap will
>> fail to map a hugetlb mapping in a segment that already have regular
>> pages mapped.
>> 
>> -aneesh
>
>
> I see this in kernel:
>
>        } else if (flags & MAP_HUGETLB) {
>                 struct user_struct *user = NULL;
>                 struct hstate *hs;
>
>                 hs = hstate_sizelog((flags >> MAP_HUGE_SHIFT) & SHM_HUGE_MASK);
>                 if (!hs)
>                         return -EINVAL;
>
>                 len = ALIGN(len, huge_page_size(hs));
>                 /*
>                  * VM_NORESERVE is used because the reservations will be
>                  * taken when vm_ops->mmap() is called
>                  * A dummy user value is used because we are not locking
>                  * memory so no accounting is necessary
>                  */
>                 file = hugetlb_file_setup(HUGETLB_ANON_FILE, len,
>                                 VM_NORESERVE,
>                                 &user, HUGETLB_ANONHUGE_INODE,
>                                 (flags >> MAP_HUGE_SHIFT) & MAP_HUGE_MASK);
>                 if (IS_ERR(file))
>                         return PTR_ERR(file);
>         }
>
> So maybe it's a question of passing in MAP_HUGETLB and the
> correct size mask.
>

Can you explain this more ?

If the question is do we need to pass fd and remove MAP_ANONYMOUS to map
hugetlb, we don't. A good example is
tools/testing/selftest/vm/map_hugetlb.c

If the question is whether we will loose hugepages on mmap even if the
mapping is PROT_NONE, then the answer is we do in the form of hugetlb
reservation.

-aneesh

  reply	other threads:[~2015-12-01 12:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-30 10:51 [Qemu-devel] [PATCH] mmap-alloc: use same backend for all mappings Greg Kurz
2015-11-30 10:53 ` Paolo Bonzini
2015-11-30 13:12   ` Michael S. Tsirkin
2015-12-01 10:42     ` Greg Kurz
2015-12-01 10:52       ` Michael S. Tsirkin
2015-11-30 13:06 ` Michael S. Tsirkin
2015-11-30 13:46   ` Greg Kurz
2015-11-30 16:59     ` Michael S. Tsirkin
2015-12-01 10:37       ` Greg Kurz
2015-12-01 10:53       ` Aneesh Kumar K.V
2015-12-01 10:57         ` Michael S. Tsirkin
2015-12-01 12:15           ` Aneesh Kumar K.V [this message]
2015-12-01 14:25             ` Michael S. Tsirkin
2015-12-01 13:31           ` Greg Kurz
2015-12-01 14:19             ` Michael S. Tsirkin

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=87vb8i2wm8.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gkurz@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.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 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.