From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: 32bit compat mode for arm64
Date: Fri, 28 Feb 2020 17:11:31 -0500 [thread overview]
Message-ID: <20200228221131.hvtpjrjm42ocbxjo@csclub.uwaterloo.ca> (raw)
In-Reply-To: <CAFLxGvyr7f8bUxaEVpEwSGYEvX4FrkpGBV6qa2sR3SHq3wi_Yw@mail.gmail.com>
On Fri, Feb 28, 2020 at 10:01:04PM +0100, Richard Weinberger via Xenomai wrote:
> I noticed that running 32bit arm EABI xenomai userspace is currently
> not possible
> on arm64 kernels.
>
> From a quick look I see the following tasks to make it happen:
> - syscall gate adaptations for cobalt arm32 syscalls (they are
> different from regular arm EABI)
> - teach ipipe_root_nr_syscalls() on arm64 about __NR_compat_syscalls
> - Don't use XENOMAI_ABI_REV for compat userspace on arm64
> - Implement a syscall32-table.h (for COBALT_SYSCALL32emu_DECL() and friends)
>
> Is this something which will be supported sooner or later?
> ...or is there a massive show-stopper I didn't notice so far?
Even x86 doesn't allow 32 bit userspace xenomai to run on a 64 bit kernel.
I suspect the use case is just so insignificant that noone wants to
bother working on such support.
--
Len Sorensen
next prev parent reply other threads:[~2020-02-28 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 21:01 32bit compat mode for arm64 Richard Weinberger
2020-02-28 22:11 ` Lennart Sorensen [this message]
2020-02-28 22:16 ` Richard Weinberger
2020-03-02 20:25 ` Lennart Sorensen
2020-03-02 20:33 ` Jan Kiszka
2020-03-02 20:42 ` Lennart Sorensen
2020-02-29 11:46 ` Richard Weinberger
2020-03-02 12:21 ` Jan Kiszka
2020-03-02 12:34 ` Richard Weinberger
2020-03-02 12:39 ` Jan Kiszka
2020-03-02 12:16 ` Jan Kiszka
2020-03-02 12:52 ` Richard Weinberger
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=20200228221131.hvtpjrjm42ocbxjo@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=richard.weinberger@gmail.com \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.