All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Vijay Kilari <vijay.kilari@gmail.com>, Jan Beulich <JBeulich@suse.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Prasun Kapoor <Prasun.Kapoor@caviumnetworks.com>,
	manish.jaggi@caviumnetworks.com, Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: Vmap allocator fails to allocate beyond 128MB
Date: Mon, 16 Feb 2015 10:28:41 +0000	[thread overview]
Message-ID: <54E1C659.5000006@linaro.org> (raw)
In-Reply-To: <CALicx6sn2f1XV6LrFzYAT1Xv6c37SXV8jCN6jN3bnHKcSaNsrw@mail.gmail.com>

On 16/02/15 10:17, Vijay Kilari wrote:

Hello Vijay,

>   For ThunderX/arm64 this issue needs to be fixed.
> Could you please comment on this?

AFAICS, x86 is also using a 1G area for the vmap. Does it mean that x86
never use vmap for more than 128M?

> I could think of below
> 
>         1) Add new call for ARM under CONFIG_ARM_32/CONFIG_ARM_64
> in vm_init() and manage map_pages_to_xen(va, 0, vm_low - nr, MAP_SMALL_PAGES);
> with different function call for arm that would not make any pte
> entries for vm_bitmap pages.
> This avoids change to x86
> 
>         2) Remove map_pages_to_xen(va, 0, vm_low - nr,
> MAP_SMALL_PAGES) from vm_init
> and add new architecture specific for initializing vm_bitmap pages.
> But this touches
> x86 code.

I don't know which approach is the best, and I though you already talked
about it with Jan... But in general a generic approach is better than a
per-architecture solution.

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-02-16 10:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-26 12:17 Vmap allocator fails to allocate beyond 128MB Vijay Kilari
2014-09-26 12:46 ` Jan Beulich
2014-09-26 15:23   ` Vijay Kilari
2014-09-26 15:51     ` Jan Beulich
2014-09-29  5:42       ` Vijay Kilari
2014-09-29  6:41         ` Jan Beulich
2014-09-29  7:10           ` Vijay Kilari
2014-09-29  7:26             ` Jan Beulich
2015-02-16 10:17               ` Vijay Kilari
2015-02-16 10:28                 ` Julien Grall [this message]
2015-02-16 10:50                   ` Vijay Kilari
2015-02-16 10:57                     ` Julien Grall
2015-02-16 11:32                       ` Julien Grall

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=54E1C659.5000006@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Prasun.Kapoor@caviumnetworks.com \
    --cc=manish.jaggi@caviumnetworks.com \
    --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.