From: wangyufen@huawei.com (wangyufen)
To: linux-arm-kernel@lists.infradead.org
Subject: arm64: dose arm64 support the sysfs system call?
Date: Fri, 21 Nov 2014 18:23:06 +0800 [thread overview]
Message-ID: <546F128A.5080705@huawei.com> (raw)
In-Reply-To: <546EEFB8.10509@hisilicon.com>
On 2014/11/21 15:54, Wei Xu wrote:
>
>
> On 2014/11/21 15:27, wangyufen wrote:
>> Hi,
>
> Hi Yufen,
>
>> I did ltp test on arm64, the sysfs testcases failed:
>>
>> sysfs01 0 TWARN : This test can only run on kernels that support the sysfs system call
>>
>> because the __NR_sysfs didn't define in aarch64
>
> Have you been enabled the *CONFIG_COMPAT* in your .config?
>
*CONFIG_COMPAT* already enabled
CONFIG_COMPAT_BRK=y
CONFIG_COMPAT_BINFMT_ELF=y
CONFIG_COMPAT=y
> The __NR_sysfs is defined at arch/arm64/include/asm/unistd32.h
> and arch/arm64/kernel/sys32.S is including it.
>
in arch/arm64/include/asm/unistd32.h defined :
__SYSCALL(135, sys_sysfs)
So I used 135 to test sysfs, I straced sysfs01,
the syscall called rt_sigprocmask not sysfs:
rt_sigprocmask(SIG_UNBLOCK, [], 0x8, 0) = -1 EINVAL (Invalid argument)
> Hope it will fix your issues.
>
> Best Regards,
> Wei
>
>> Dose anyone know what number the sysfs system call is in aarch64?
>>
>>
>> Thanks,
>> Wang
>>
>> _______________________________________________
>> linuxarm mailing list
>> linuxarm at huawei.com
>> http://rnd-openeuler.huawei.com/mailman/listinfo/linuxarm
>>
>>
>
> _______________________________________________
> linuxarm mailing list
> linuxarm at huawei.com
> http://rnd-openeuler.huawei.com/mailman/listinfo/linuxarm
>
>
next prev parent reply other threads:[~2014-11-21 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 7:27 arm64: dose arm64 support the sysfs system call? wangyufen
[not found] ` <546EEFB8.10509@hisilicon.com>
2014-11-21 10:23 ` wangyufen [this message]
2014-11-21 11:10 ` Arnd Bergmann
2014-12-05 2:07 ` wangyufen
2014-12-05 2:45 ` Chanho Park
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=546F128A.5080705@huawei.com \
--to=wangyufen@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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 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).