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:31:08 +0100 [thread overview]
Message-ID: <20190808113107.GI10425@arm.com> (raw)
In-Reply-To: <2adcb1ed626fb7829481b2b8d0ff54d1@agner.ch>
On Thu, Aug 08, 2019 at 12:17:26PM +0200, Stefan Agner wrote:
> On 2019-08-08 11:04, Marc Zyngier wrote:
[...]
> > Hey, you could create a VM, a vcpu and dump the ID registers by issuing
> > a set of KVM_GET_ONE_REG ioctls. Not necessarily recommended... ;-)
>
> I see, no no, I think I leave that exercise for somebody else to try :)
I think KVM guest AArch32 support can exist even when compat is
configured out though. So just because it works in a guest doesn't mean
that the host kernel supports it for userspace, IIUC.
Otherwise, this would be a fun hack ;)
Cheers
---Dave
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-08 11:31 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 [this message]
2019-08-08 9:35 ` Dave Martin
2019-08-08 10:30 ` Stefan Agner
2019-08-08 11:28 ` Dave Martin
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=20190808113107.GI10425@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 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).