From: Christopher Covington <cov@codeaurora.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will.deacon@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
James Hogan <james.hogan@imgtec.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jon Masters <jcm@redhat.com>,
Jeremy Linton <jeremy.linton@arm.com>
Subject: Re: [PATCH] arm64: Expose TASK_SIZE to userspace via auxv
Date: Wed, 17 Aug 2016 07:12:06 -0400 [thread overview]
Message-ID: <CED1E802-65C5-48B9-8165-46684BE81164@codeaurora.org> (raw)
In-Reply-To: <20160817103006.GB20762@e104818-lin.cambridge.arm.com>
On August 17, 2016 6:30:06 AM EDT, Catalin Marinas <catalin.marinas@arm.com> wrote:
>On Tue, Aug 16, 2016 at 02:32:29PM -0400, Christopher Covington wrote:
>> Some userspace applications need to know the maximum virtual address
>they can
>> use (TASK_SIZE).
>
>Just curious, what are the cases needing TASK_SIZE in user space?
Checkpoint/Restore In Userspace and the Mozilla Javascript Engine https://bugzilla.mozilla.org/show_bug.cgi?id=1143022 are the specific cases I've run into. I've heard LuaJIT might have a similar situation. In general I think making allocations from the top down is a shortcut for finding a large unused region of memory.
Thanks,
Cov
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
Sent from my Snapdragon powered Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2016-08-17 11:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 18:32 Christopher Covington
2016-08-17 10:30 ` Catalin Marinas
2016-08-17 11:12 ` Christopher Covington [this message]
2016-08-18 12:00 ` Ard Biesheuvel
2016-08-18 12:42 ` Catalin Marinas
2016-08-18 13:18 ` Ard Biesheuvel
2016-08-18 12:17 ` Richard Weinberger
2016-09-09 14:14 ` Christopher Covington
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=CED1E802-65C5-48B9-8165-46684BE81164@codeaurora.org \
--to=cov@codeaurora.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=james.hogan@imgtec.com \
--cc=jcm@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.com \
/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
all inboxes | Powered by JetHome®