[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <009101cfa06d$40eae8d0$c2c0ba70$@codeaurora.org>
Date: Tue, 15 Jul 2014 13:42:11 -0700
From: "Weiming Zhao" <weimingz@...eaurora.org>
To: "'Rich Felker'" <dalias@...c.org>
Cc: <musl@...ts.openwall.com>
Subject: RE: AArch64 merge back
Hi Rich,
Thanks.
Yes, those __NR_xxx values should match with kernel defs.
But do you know where the current syscall.h originally come from?
In the beginning of aarch64/bits/syscall.h, we can see comments like:
/*
* This file contains the system call numbers, based on the
* layout of the x86-64 architecture, which embeds the
* pointer to the syscall in the table.
*
* As a basic principle, no duplication of functionality
* should be added, e.g. we don't use lseek when llseek
* is present. New architectures should use this file
* and implement the less feature-full calls in user space.
*/
It looks like it's coming from some other projects.
Could you help to confirm its source? The reason is we plan to use MUSL for
some internal projects but we need to make sure there is no legal/license
issues.
For musl-or1k, there is no aarch64 version of syscall. Are you suggesting
that we can refer to its ARM version of syscall.h?
Thanks a lot,
Weiming
-----Original Message-----
From: Rich Felker [mailto:dalias@...ifal.cx] On Behalf Of Rich Felker
Sent: Tuesday, July 15, 2014 12:07 PM
To: Weiming Zhao
Cc: musl@...ts.openwall.com
Subject: Re: [musl] AArch64 merge back
On Tue, Jul 15, 2014 at 11:58:59AM -0700, Weiming Zhao wrote:
> Hi Rich,
>
> Thanks a lot for your response.
>
> We're trying static linking of AArch64 with some simple tests.
> Some simple tests are working, but we do see some syscall issue as you
> mentioned.
> We suspect it's related with arch/aarch64/bits/syscall.h.
> Is the file written from scratch or based on some existing open source
> projects?
It should match the definitions from the kernel, but definitions for any
syscalls that do not actually exist on aarch64 need to be removed.
If the kernel is using the asm-generic values for aarch64, you can get a
matching bits/syscall.h from the or1k (openrisc) port that's in-progress,
at:
https://github.com/skristiansson/musl-or1k
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
