From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 1/3] arm64: Add __NR_* definitions for compat syscalls
Date: Wed, 28 Jan 2015 22:35:01 +0100 [thread overview]
Message-ID: <12610204.3KbMJUth1j@wuerfel> (raw)
In-Reply-To: <CAOZdJXUhpmi0SM5izDYQnx8SHjWjqOFVduV0+boPw6+YCKP5+g@mail.gmail.com>
On Wednesday 28 January 2015 15:31:49 Timur Tabi wrote:
> On Fri, Jul 4, 2014 at 2:28 AM, AKASHI Takahiro
> <takahiro.akashi@linaro.org> wrote:
> > +#define __ARM_NR_COMPAT_BASE 0x0f0000
> > +#define __ARM_NR_compat_cacheflush (__ARM_NR_COMPAT_BASE+2)
> > +#define __ARM_NR_compat_set_tls (__ARM_NR_COMPAT_BASE+5)
>
> I know this patch is six months old, but I was wondering if anyone
> knows of any plans to make these syscalls available to 64-bit apps?
> We have a 32-bit app that uses __ARM_NR_compat_cacheflush, and we'd
> like to port that app to 64-bit. I'm just not sure how to start doing
> that, since there don't appear to be any 64-bit ARM-specific syscalls.
>
You can add architecture specific syscalls by using the 16 numbers following
__NR_arch_specific_syscall. Whether it makes sense to have a cacheflush
syscall on arm64, I have no idea.
I believe that we should not need a set_tls syscall though.
Arnd
next prev parent reply other threads:[~2015-01-28 21:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 7:28 [PATCH v10 0/3] arm64: Add audit support AKASHI Takahiro
2014-07-04 7:28 ` [PATCH v10 1/3] arm64: Add __NR_* definitions for compat syscalls AKASHI Takahiro
2014-07-04 10:06 ` Arnd Bergmann
2014-07-04 10:57 ` Catalin Marinas
2014-07-04 11:05 ` AKASHI Takahiro
2014-07-04 11:17 ` Arnd Bergmann
2015-01-28 21:31 ` Timur Tabi
2015-01-28 21:35 ` Arnd Bergmann [this message]
2015-01-29 9:57 ` Will Deacon
2014-07-04 7:28 ` [PATCH v10 2/3] arm64: Add audit support AKASHI Takahiro
2014-07-04 7:28 ` [PATCH v10 3/3] arm64: audit: Add audit hook in syscall_trace_enter/exit() AKASHI Takahiro
2014-07-10 10:08 ` [PATCH v10 0/3] arm64: Add audit support Catalin Marinas
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=12610204.3KbMJUth1j@wuerfel \
--to=arnd@arndb.de \
--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