From: Dave Martin <Dave.Martin@arm.com>
To: Stefan Agner <stefan@agner.ch>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
ynorov@caviumnetworks.com, will.deacon@arm.com,
linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com
Subject: Re: Detecting AArch32 support from a AArch64 process in user space
Date: Thu, 8 Aug 2019 12:28:17 +0100 [thread overview]
Message-ID: <20190808112817.GH10425@arm.com> (raw)
In-Reply-To: <09a5d28f865ef0bd034ba9acbe1b5334@agner.ch>
On Thu, Aug 08, 2019 at 12:30:03PM +0200, Stefan Agner wrote:
> On 2019-08-08 11:35, Dave Martin wrote:
> > On Thu, Aug 08, 2019 at 09:36:42AM +0200, Stefan Agner wrote:
> >> [resend this time with the correct mailing list address]
> >>
> >> Hello,
> >>
> >> I am trying to detect whether an ARMv8 system running in AArch64 state
> >> supports AArch32 state from a user space process. The arm64_features[]
> >> in
> >
> > Why? Is this just for diagnostic purposes, or some programmatic reason?
>
> The use case I currently have in mind is to decide whether to show
> 32-bit ARM Docker images in a UI (or arm32v7 images how it is nowadays
> called in Docker land).
>
> >
> > In the latter case, just try to do what ever it is you want to do that
> > depends on AArch32: if it fails, you don't have AArch32.
>
>
> Yeah one option I considered was just fetching a minimalistic arm32v7
> container, but still seems a bit excessive.
Ah, right.
So, I guess trying to set the personality or trying to exec a trivial
32-bit binary would answer that.
You could ship a trivial static binary with docker for that: trying
to run a whole container is probably overkill.
If trying to set the personality is more convenient though, that seems
an equally good approach in practice.
[...]
Cheers
---Dave
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-08 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 7:36 Detecting AArch32 support from a AArch64 process in user space Stefan Agner
2019-08-08 9:04 ` Marc Zyngier
2019-08-08 9:15 ` Will Deacon
2019-08-08 10:22 ` Stefan Agner
2019-08-08 10:41 ` Stefan Agner
2019-08-08 10:17 ` Stefan Agner
2019-08-08 11:31 ` Dave Martin
2019-08-08 9:35 ` Dave Martin
2019-08-08 10:30 ` Stefan Agner
2019-08-08 11:28 ` Dave Martin [this message]
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=20190808112817.GH10425@arm.com \
--to=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=stefan@agner.ch \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.com \
--cc=ynorov@caviumnetworks.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.
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.