From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Vijay Kilari <vijay.kilari@gmail.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
StefanoStabellini <stefano.stabellini@citrix.com>
Subject: Re: [RFC PATCH] xen/arm: Vmap allocator fails to allocate beyond 128M
Date: Tue, 24 Feb 2015 10:20:49 +0000 [thread overview]
Message-ID: <1424773249.27930.295.camel@citrix.com> (raw)
In-Reply-To: <54EC59F80200007800062FA9@mail.emea.novell.com>
On Tue, 2015-02-24 at 10:01 +0000, Jan Beulich wrote:
> >>> On 23.02.15 at 18:03, <ian.campbell@citrix.com> wrote:
> > Can we along with this fix perhaps rename to something which does
> > indicate this. MAP_NON_LEAF_PTS or something perhaps? (This is really a
> > question for Jan).
>
> Renaming wouldn't be the right thing - we'd need a second flag.
> Indeed I've been (ab)using behavior of the x86 implementation
> here that's neither documented nor necessarily obvious.
How about a new arch interface like create_mapping_pts or
populate_pt_range or some such which provides the semantics you want?
On x86 it could just be implemented using map_pages_to_xen(...,
MAP_SMALL_PAGES) and on ARM we'd figure it out somehow.
Ian.
next prev parent reply other threads:[~2015-02-24 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 6:07 [RFC PATCH] xen/arm: Vmap allocator fails to allocate beyond 128M Vijay Kilari
2015-02-17 9:53 ` Jan Beulich
2015-02-17 14:50 ` Julien Grall
2015-02-23 17:07 ` Ian Campbell
2015-02-23 21:45 ` Julien Grall
2015-02-24 8:49 ` Ian Campbell
2015-02-23 17:03 ` Ian Campbell
2015-02-23 17:10 ` Ian Campbell
2015-02-24 10:01 ` Jan Beulich
2015-02-24 10:20 ` Ian Campbell [this message]
2015-02-24 10:24 ` Jan Beulich
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=1424773249.27930.295.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=xen-devel@lists.xen.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.