From: Peter Maydell <peter.maydell@linaro.org>
To: WANG Xuerui <i.qemu@xen0n.name>
Cc: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>,
Song Gao <gaosong@loongson.cn>, WANG Xuerui <git@xen0n.name>
Subject: Re: [PATCH] linux-user: Add support for LoongArch64's old world ABI
Date: Mon, 23 Jan 2023 10:47:24 +0000 [thread overview]
Message-ID: <CAFEAcA8iVrpzFnKj6Ws+F63RJSzV-atUbspFQKqsWOtptOxwPw@mail.gmail.com> (raw)
In-Reply-To: <20230123102626.4144557-1-i.qemu@xen0n.name>
On Mon, 23 Jan 2023 at 10:27, WANG Xuerui <i.qemu@xen0n.name> wrote:
>
> From: WANG Xuerui <git@xen0n.name>
>
> This patch adds a "loongarch64ow-linux-user" target and a
> corresponding "qemu-loongarch64ow" binary, for supporting user-mode
> emulation of old-world LoongArch applications in the wild.
>
> Although the old-world LoongArch is already being (slowly) phased out,
> there are already a number of deployments (mainly as a result of
> LoongArch's early commercial growth), whose migration path is something
> software developers have to care about. Support for user-mode emulation
> in addition to system-level emulation would help development of such
> migration & compatibility solutions.
Is this 'old-world' ABI supported by the upstream Linux kernel?
I can't see signs of it from a quick grep. If it isn't, then
I'm not sure if we should support it in QEMU user-mode emulation.
We've always set "upstream Linux" as our definition of what the
official ABI and featureset is for usermode emulation.
thanks
-- PMM
next prev parent reply other threads:[~2023-01-23 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 10:26 [PATCH] linux-user: Add support for LoongArch64's old world ABI WANG Xuerui
2023-01-23 10:47 ` Peter Maydell [this message]
2023-01-23 11:12 ` WANG Xuerui
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=CAFEAcA8iVrpzFnKj6Ws+F63RJSzV-atUbspFQKqsWOtptOxwPw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=gaosong@loongson.cn \
--cc=git@xen0n.name \
--cc=i.qemu@xen0n.name \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).