From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Gavin Shan <gshan@redhat.com>,
linux-kernel@vger.kernel.org, Julien Grall <julien.grall@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Will Deacon <will@kernel.org>, Qais Yousef <qais.yousef@arm.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Marc Zyngier <maz@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Andrey Ignatov <rdna@fb.com>, Steven Price <steven.price@arm.com>,
Sami Tolvanen <samitolvanen@google.com>,
David Brazdil <dbrazdil@google.com>,
Dave Martin <Dave.Martin@arm.com>,
Kees Cook <keescook@chromium.org>,
sonicadvance1@gmail.com,
Frederic Weisbecker <frederic@kernel.org>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Al Viro <viro@zeniv.linux.org.uk>,
amanieu@gmail.com, Peter Collingbourne <pcc@google.com>,
linux-arm-kernel@lists.infradead.org,
Jens Axboe <axboe@kernel.dk>, Kevin Hao <haokexin@gmail.com>,
Jason Yan <yanaijie@huawei.com>, Oleg Nesterov <oleg@redhat.com>,
Tian Tao <tiantao6@hisilicon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [RESEND RFC PATCH v2] arm64: Exposes support for 32-bit syscalls
Date: Fri, 12 Feb 2021 13:28:08 +0000 [thread overview]
Message-ID: <20210212132807.GC7718@arm.com> (raw)
In-Reply-To: <20210212123515.GC6057@sirena.org.uk>
On Fri, Feb 12, 2021 at 12:35:15PM +0000, Mark Brown wrote:
> On Fri, Feb 12, 2021 at 11:30:41AM +0000, Steven Price wrote:
> > On 11/02/2021 20:21, sonicadvance1@gmail.com wrote:
> > > Why do we need compatibility layers?
> > > There are ARMv8 CPUs that only support AArch64 but still need to run
> > > AArch32 applications.
> > > Cortex-A34/R82 and other cores are prime examples of this.
> > > Additionally if a user is needing to run legacy 32-bit x86 software, it
> > > needs the same compatibility layer.
>
> > Unless I'm much mistaken QEMU's user mode already does this - admittedly I
> > don't tend to run "legacy 32-bit x86 software".
>
> Yes, this has been deployed on Debian for a long time - you can install
> any combination of Debian architectures on a single system and it will
> use qemu to run binaries that can't be supported natively by the
> hardware.
The only downside I think is that for some syscalls it's not that
efficient. Those using struct iovec come to mind, qemu probably
duplicates the user structures, having to copy them in both directions
(well, the kernel compat layer does something similar).
Anyway, I'm not in favour of this patch. Those binary translation tools
need to explore the user-only options first and come up with some perf
numbers to justify the proposal.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Steven Price <steven.price@arm.com>,
sonicadvance1@gmail.com, amanieu@gmail.com,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Oleg Nesterov <oleg@redhat.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Dave Martin <Dave.Martin@arm.com>,
Amit Daniel Kachhap <amit.kachhap@arm.com>,
Marc Zyngier <maz@kernel.org>,
David Brazdil <dbrazdil@google.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Gavin Shan <gshan@redhat.com>, Mike Rapoport <rppt@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Kristina Martsenko <kristina.martsenko@arm.com>,
Kees Cook <keescook@chromium.org>,
Sami Tolvanen <samitolvanen@google.com>,
Frederic Weisbecker <frederic@kernel.org>,
Kevin Hao <haokexin@gmail.com>, Jason Yan <yanaijie@huawei.com>,
Andrey Ignatov <rdna@fb.com>,
Peter Collingbourne <pcc@google.com>,
Julien Grall <julien.grall@arm.com>,
Tian Tao <tiantao6@hisilicon.com>,
Qais Yousef <qais.yousef@arm.com>, Jens Axboe <axboe@kernel.dk>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RESEND RFC PATCH v2] arm64: Exposes support for 32-bit syscalls
Date: Fri, 12 Feb 2021 13:28:08 +0000 [thread overview]
Message-ID: <20210212132807.GC7718@arm.com> (raw)
In-Reply-To: <20210212123515.GC6057@sirena.org.uk>
On Fri, Feb 12, 2021 at 12:35:15PM +0000, Mark Brown wrote:
> On Fri, Feb 12, 2021 at 11:30:41AM +0000, Steven Price wrote:
> > On 11/02/2021 20:21, sonicadvance1@gmail.com wrote:
> > > Why do we need compatibility layers?
> > > There are ARMv8 CPUs that only support AArch64 but still need to run
> > > AArch32 applications.
> > > Cortex-A34/R82 and other cores are prime examples of this.
> > > Additionally if a user is needing to run legacy 32-bit x86 software, it
> > > needs the same compatibility layer.
>
> > Unless I'm much mistaken QEMU's user mode already does this - admittedly I
> > don't tend to run "legacy 32-bit x86 software".
>
> Yes, this has been deployed on Debian for a long time - you can install
> any combination of Debian architectures on a single system and it will
> use qemu to run binaries that can't be supported natively by the
> hardware.
The only downside I think is that for some syscalls it's not that
efficient. Those using struct iovec come to mind, qemu probably
duplicates the user structures, having to copy them in both directions
(well, the kernel compat layer does something similar).
Anyway, I'm not in favour of this patch. Those binary translation tools
need to explore the user-only options first and come up with some perf
numbers to justify the proposal.
--
Catalin
next prev parent reply other threads:[~2021-02-12 13:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 20:21 [RESEND RFC PATCH v2] arm64: Exposes support for 32-bit syscalls sonicadvance1
2021-02-11 20:21 ` sonicadvance1
2021-02-12 11:30 ` Steven Price
2021-02-12 11:30 ` Steven Price
2021-02-12 12:35 ` Mark Brown
2021-02-12 12:35 ` Mark Brown
2021-02-12 13:28 ` Catalin Marinas [this message]
2021-02-12 13:28 ` Catalin Marinas
2021-02-12 14:12 ` David Laight
2021-02-12 14:12 ` David Laight
2021-02-12 14:44 ` Catalin Marinas
2021-02-12 14:44 ` Catalin Marinas
2021-02-12 15:06 ` David Laight
2021-02-12 15:06 ` David Laight
2021-02-12 16:24 ` Amanieu d'Antras
2021-02-12 16:24 ` Amanieu d'Antras
2021-02-12 18:04 ` Mark Rutland
2021-02-12 18:04 ` Mark Rutland
2021-02-12 19:06 ` Amanieu d'Antras
2021-02-12 19:06 ` Amanieu d'Antras
2021-02-12 13:59 ` Arnd Bergmann
2021-02-12 13:59 ` Arnd Bergmann
2021-02-12 14:13 ` Mark Rutland
2021-02-12 14:13 ` Mark Rutland
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=20210212132807.GC7718@arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=amanieu@gmail.com \
--cc=amit.kachhap@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=dbrazdil@google.com \
--cc=frederic@kernel.org \
--cc=gshan@redhat.com \
--cc=haokexin@gmail.com \
--cc=jean-philippe@linaro.org \
--cc=julien.grall@arm.com \
--cc=keescook@chromium.org \
--cc=kristina.martsenko@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oleg@redhat.com \
--cc=pcc@google.com \
--cc=qais.yousef@arm.com \
--cc=rdna@fb.com \
--cc=rppt@kernel.org \
--cc=samitolvanen@google.com \
--cc=sonicadvance1@gmail.com \
--cc=steven.price@arm.com \
--cc=tiantao6@hisilicon.com \
--cc=vincenzo.frascino@arm.com \
--cc=viro@zeniv.linux.org.uk \
--cc=will@kernel.org \
--cc=yanaijie@huawei.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.