From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4757 Path: news.gmane.org!not-for-mail From: =?KOI8-R?B?98zBxMnNydIg883J0s7P1w==?= Newsgroups: gmane.linux.lib.musl.general Subject: Re: Any plans on MMU-less support? Date: Mon, 31 Mar 2014 15:44:23 +0900 Message-ID: References: <5337BE64.2010504@gmail.com> <20140330150139.GJ27448@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01182544c3eaf504f5e161c1 X-Trace: ger.gmane.org 1396248285 14262 80.91.229.3 (31 Mar 2014 06:44:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 31 Mar 2014 06:44:45 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4761-gllmg-musl=m.gmane.org@lists.openwall.com Mon Mar 31 08:44:41 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WUVxV-0000zm-BR for gllmg-musl@plane.gmane.org; Mon, 31 Mar 2014 08:44:37 +0200 Original-Received: (qmail 22329 invoked by uid 550); 31 Mar 2014 06:44:36 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 22320 invoked from network); 31 Mar 2014 06:44:36 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=8LpDGptnR3uNoY8nkC2oBm/ibeZzfrR0PdkQMwx+d8I=; b=FHOXoaE4cj7kc40VxVuOswPnKKlNt6JJmzVYZz+1smMZe5VEr/QkBZe2yIodcggEeB 2faLz1PdvG0ENfLQfNCv6yayruQyR9ivZrsz09UYf8s+FMOqW/jdG+dYBJ1PfZJWOL2z uemuzGhAsSyx037Ih8e3FZI1z3pVDTNSB/XKDG80Y12rgd68JkuKzFD2wZ4D9NBQq/kb Q0fs9llH8DJIZaC/rynTVGpFVozepkgihMnAsOEZnPW5xBPpFofDCPB3EkZLXFVqvbJw FGQnDNPIBxKbU/Vkk6eGznGF9YDi3ffuM5G732zZUyqss8nSq2GHpgKtwClGhDsxG3zd ZU4Q== X-Received: by 10.60.173.233 with SMTP id bn9mr20754814oec.9.1396248263517; Sun, 30 Mar 2014 23:44:23 -0700 (PDT) In-Reply-To: <20140330150139.GJ27448@port70.net> Xref: news.gmane.org gmane.linux.lib.musl.general:4757 Archived-At: --089e01182544c3eaf504f5e161c1 Content-Type: text/plain; charset=ISO-8859-1 I already using uClibc so i know that i hardly ever have fork or dynamic linkage. It's all suitable for me. So whats up with mmap and startup code? I wonder on minimal working set of that all :-) 2014-03-31 0:01 GMT+09:00 Szabolcs Nagy : > * Smirnov Vladimir [2014-03-30 15:49:08 +0900]: > > I wonder if MUSL have such roadmap or there is any hackish way to > > add that support (may be some unoffitial patches). > > My problem that i've stucked with old gcc toolchain and uClibc > > supporting one widely used ARMv4 MMUless chip. > > looking at uClibc the main differences in a no-mmu system: > > fork is not available so related functions have to be changed/disabled > (vfork, daemon, wordexp, forkpty, pthread_atfork) > > brk is not available so malloc needs to change > > mmap may need MAP_UNINITIALIZED flag for performance > (and MAP_FIXED flag will fail) > > memory management related things may need to be changed/disabled > (mprotect?,mlock,msync,..) > > for dynamic linking ldso and libc startup code may need some change > (some targets (not arm) need fdpic or dsbt elf support) > (others can use a shared flat binary format) > > pthread may need smaller default stack and more careful stack usage > > arm startup code needs a change according to > http://git.uclibc.org/uClibc/tree/libc/sysdeps/linux/arm/crt1.S#n179 > > and you may need to fix various toolchain issues.. > --089e01182544c3eaf504f5e161c1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I already using uClibc so i know that i hardly e= ver have fork or dynamic linkage. It's all suitable for me.
So= whats up with mmap and startup code?
I wonder on minimal working = set of that all :-)


2014-03= -31 0:01 GMT+09:00 Szabolcs Nagy <nsz@port70.net>:
* Smirnov Vladimir <mapron1@gmail.c= om> [2014-03-30 15:49:08 +0900]:
> I wonder if MUSL have such roadmap or there is = any hackish way to
> add that support (may be some unoffitial patches).
> My problem that i've stucked with old gcc toolchain and uClibc
> supporting one widely used ARMv4 MMUless chip.

looking at uClibc the main differences in a no-mmu system:

fork is not available so related functions have to be changed/disabled
(vfork, daemon, wordexp, forkpty, pthread_atfork)

brk is not available so malloc needs to change

mmap may need MAP_UNINITIALIZED flag for performance
(and MAP_FIXED flag will fail)

memory management related things may need to be changed/disabled
(mprotect?,mlock,msync,..)

for dynamic linking ldso and libc startup code may need some change
(some targets (not arm) need fdpic or dsbt elf support)
(others can use a shared flat binary format)

pthread may need smaller default stack and more careful stack usage

arm startup code needs a change according to
http://git.uclibc.org/uClibc/tree/libc/sysdeps/linu= x/arm/crt1.S#n179

and you may need to fix various toolchain issues..

--089e01182544c3eaf504f5e161c1--