mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [PATCH] arm asm for vfork
Date: Wed, 18 Jul 2018 12:20:00 +1000	[thread overview]
Message-ID: <CAEg67GnPaf++HTRqbp8=H9-3BwNMXtX1zeiyzWTO8JoYOHhQWw@mail.gmail.com> (raw)
In-Reply-To: <CAEg67G=gyD9qT7dKbKEDu7htxUD3br4PGuAL8Q7CN-=s5Hxisg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2088 bytes --]

Hi Rich,

I saw another thread where it was mentioned you may be doing a 1.20
release some time soon.

Is there any chance this could get merged in time? I've been running
it for months without any issues now.

Attached is an updated patch using svc rather than swi.

Thanks,

Patrick
On Mon, Apr 30, 2018 at 12:32 PM Patrick Oppenlander
<patrick.oppenlander@gmail.com> wrote:
>
> You're right, it's not particularly pleasant. I have an MIMXRT1050-EVK
> board which is what this is for -- it's a 600MHz Cortex-M7 with a
> 32MiB DRAM for about $80USD. More than enough to run my kernel and a
> few other bits and pieces for now even with the overhead of copying
> the program text.
>
> Are there plans for fdpic in musl as soon as GCC supports it?
>
> SVC is just a name change from SWI. Old habits die hard I guess. In my
> brain SWI makes more sense as it really is an interrupt and not a
> call.
>
> I won't bother resubmitting a patch for that though.
>
> Patrick
>
>
>
>
> On Mon, Apr 30, 2018 at 12:09 PM, Rich Felker <dalias@libc.org> wrote:
> > On Mon, Apr 30, 2018 at 11:36:22AM +1000, patrick.oppenlander@gmail.com wrote:
> >> From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
> >>
> >> ---
> >>  src/process/arm/vfork.s | 12 ++++++++++++
> >>  1 file changed, 12 insertions(+)
> >>  create mode 100644 src/process/arm/vfork.s
> >>
> >> diff --git a/src/process/arm/vfork.s b/src/process/arm/vfork.s
> >> new file mode 100644
> >> index 00000000..f01fe1d0
> >> --- /dev/null
> >> +++ b/src/process/arm/vfork.s
> >> @@ -0,0 +1,12 @@
> >> +.syntax unified
> >> +.global __vfork
> >> +.weak vfork
> >> +.type __vfork,%function
> >> +.type vfork,%function
> >> +__vfork:
> >> +vfork:
> >> +     mov ip, r7
> >> +     mov r7, 190
> >> +     swi 0
> >> +     mov r7, ip
> >> +     b __syscall_ret
> >> --
> >> 2.17.0
> >
> > Thanks. We'll need this for nommu users; right now that's not so
> > practical but it will be once we get fdpic added.
> >
> > I haven't tested, but the patch looks right. Elsewhere we use svc
> > instead of swi; not sure if that matters.
> >
> > Rich

[-- Attachment #2: 0001-arm-asm-for-vfork.patch --]
[-- Type: text/x-patch, Size: 690 bytes --]

From b0e59bb68cb102fa8d397628a3248a2049150d74 Mon Sep 17 00:00:00 2001
From: Patrick Oppenlander <patrick.oppenlander@gmail.com>
Date: Tue, 10 Apr 2018 11:01:25 +1000
Subject: [PATCH] arm asm for vfork

---
 src/process/arm/vfork.s | 12 ++++++++++++
 1 file changed, 12 insertions(+)
 create mode 100644 src/process/arm/vfork.s

diff --git a/src/process/arm/vfork.s b/src/process/arm/vfork.s
new file mode 100644
index 00000000..db4e7b43
--- /dev/null
+++ b/src/process/arm/vfork.s
@@ -0,0 +1,12 @@
+.syntax unified
+.global __vfork
+.weak vfork
+.type __vfork,%function
+.type vfork,%function
+__vfork:
+vfork:
+	mov ip, r7
+	mov r7, 190
+	svc 0
+	mov r7, ip
+	b __syscall_ret
-- 
2.18.0


  reply	other threads:[~2018-07-18  2:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-30  1:36 patrick.oppenlander
2018-04-30  1:36 ` patrick.oppenlander
2018-04-30  2:09   ` Rich Felker
2018-04-30  2:32     ` Patrick Oppenlander
2018-07-18  2:20       ` Patrick Oppenlander [this message]
2018-07-18  2:35         ` Rich Felker
2018-07-18  4:14           ` Patrick Oppenlander
2018-09-06 15:02             ` Patrick Oppenlander
2018-09-06 15:19               ` Rich Felker
2018-09-07  2:05                 ` Rich Felker
2018-09-07  6:29                   ` Patrick Oppenlander
2018-07-18 13:44         ` Christopher Friedt

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='CAEg67GnPaf++HTRqbp8=H9-3BwNMXtX1zeiyzWTO8JoYOHhQWw@mail.gmail.com' \
    --to=patrick.oppenlander@gmail.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).