From: Richard Henderson <richard.henderson@linaro.org>
To: Jiajie Chen <c@jia.je>, qemu-devel@nongnu.org
Cc: "Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Song Gao" <gaosong@loongson.cn>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 1/3] target/loongarch: Introduce loongarch32-softmmu target
Date: Sun, 6 Aug 2023 07:41:34 -0700 [thread overview]
Message-ID: <c5c5f247-6b2d-36e1-c144-53c4a99ad5cc@linaro.org> (raw)
In-Reply-To: <20230806141357.1756714-1-c@jia.je>
On 8/6/23 07:13, Jiajie Chen wrote:
> This commit introduces new loongarch32-softmmu target. Compared to
> loongarch64-softmmu, the new target is different at least in:
>
> - GPRs and CSRs are 32-bits wide, but FPRs are still 64-bits wide
> - LA32 lacks some 64-bit-only instructions
> - CSR.DMW0-3 introduces PSEG
Let us not create a new executable if we can avoid it.
We can run 32-bit cpus from qemu-system-{x86_64,ppc64,aarch64}.
In any case, the patch is much too large and must be split.
r~
next prev parent reply other threads:[~2023-08-06 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 14:13 [PATCH 1/3] target/loongarch: Introduce loongarch32-softmmu target Jiajie Chen
2023-08-06 14:13 ` [PATCH 2/3] target/loongarch: Support LoongArch32 TLB entry Jiajie Chen
2023-08-06 14:13 ` [PATCH 3/3] target/loongarch: Mark CSR.PWCH as LoongArch64-only Jiajie Chen
2023-08-06 14:41 ` Richard Henderson [this message]
2023-08-07 2:31 ` [PATCH 1/3] target/loongarch: Introduce loongarch32-softmmu target gaosong
2023-08-07 2:51 ` gaosong
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=c5c5f247-6b2d-36e1-c144-53c4a99ad5cc@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=c@jia.je \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=gaosong@loongson.cn \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=yangxiaojuan@loongson.cn \
/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).