From: Richard Henderson <richard.henderson@linaro.org>
To: Jiajie Chen <c@jia.je>, qemu-devel@nongnu.org
Cc: yijun@loongson.cn, shenjinyang@loongson.cn, gaosong@loongson.cn,
i.qemu@xen0n.name
Subject: Re: [PATCH v4 02/11] target/loongarch: Add new object class for loongarch32 cpus
Date: Tue, 8 Aug 2023 11:19:32 -0700 [thread overview]
Message-ID: <aec747e6-e780-d9b4-5bbd-74d830dd714e@linaro.org> (raw)
In-Reply-To: <20230808015506.1705140-3-c@jia.je>
On 8/7/23 18:54, Jiajie Chen wrote:
> Add object class for future loongarch32 cpus. It is derived from the
> loongarch64 object class.
>
> Signed-off-by: Jiajie Chen <c@jia.je>
> ---
> target/loongarch/cpu.c | 24 ++++++++++++++++++++++++
> target/loongarch/cpu.h | 11 +++++++++++
> 2 files changed, 35 insertions(+)
>
> diff --git a/target/loongarch/cpu.c b/target/loongarch/cpu.c
> index ad93ecac92..3bd293d00a 100644
> --- a/target/loongarch/cpu.c
> +++ b/target/loongarch/cpu.c
> @@ -732,6 +732,10 @@ static void loongarch_cpu_class_init(ObjectClass *c, void *data)
> #endif
> }
>
> +static void loongarch32_cpu_class_init(ObjectClass *c, void *data)
> +{
> +}
> +
> #define DEFINE_LOONGARCH_CPU_TYPE(model, initfn) \
> { \
> .parent = TYPE_LOONGARCH_CPU, \
> @@ -754,3 +758,23 @@ static const TypeInfo loongarch_cpu_type_infos[] = {
> };
>
> DEFINE_TYPES(loongarch_cpu_type_infos)
> +
> +#define DEFINE_LOONGARCH32_CPU_TYPE(model, initfn) \
> + { \
> + .parent = TYPE_LOONGARCH32_CPU, \
> + .instance_init = initfn, \
> + .name = LOONGARCH_CPU_TYPE_NAME(model), \
> + }
> +
> +static const TypeInfo loongarch32_cpu_type_infos[] = {
> + {
> + .name = TYPE_LOONGARCH32_CPU,
> + .parent = TYPE_LOONGARCH_CPU,
> + .instance_size = sizeof(LoongArchCPU),
> +
> + .abstract = true,
> + .class_size = sizeof(LoongArchCPUClass),
> + .class_init = loongarch32_cpu_class_init,
> + },
> +};
You don't need to create a new array, you can put these into the existing
loongarch_cpu_type_infos[] like so:
static const TypeInfo loongarch_cpu_type_infos[] = {
{
.name = TYPE_LOONGARCH_CPU,
...
},
{
.name = TYPE_LOONGARCH32_CPU,
...
},
DEFINE_LOONGARCH_CPU_TYPE("la464", loongarch_la464_initfn),
DEFINE_LOONGARCH32_CPU_TYPE("la132", loongarch_la132_initfn),
};
> +#define TYPE_LOONGARCH32_CPU "loongarch32-cpu"
> +typedef struct LoongArch32CPUClass LoongArch32CPUClass;
> +DECLARE_CLASS_CHECKERS(LoongArch32CPUClass, LOONGARCH32_CPU,
> + TYPE_LOONGARCH32_CPU)
> +
> +struct LoongArch32CPUClass {
> + /*< private >*/
> + LoongArchCPUClass parent_class;
> + /*< public >*/
> +};
You don't need to declare another struct if it's just a wrapper.
If you do declare another struct, then you must actually use it in the .class_size
initializer.
Also, I've noticed two existing bugs:
(1) Missing alignment on fprs, which is required by tcg_gen_gvec_*:
typedef struct CPUArchState {
uint64_t gpr[32];
uint64_t pc;
- fpr_t fpr[32];
+ fpr_t fpr[32] QEMU_ALIGNED(16);
(2) Missing instance_align on the class:
.instance_align = __alignof(LoongArchCPU),
r~
next prev parent reply other threads:[~2023-08-08 18:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 1:54 [PATCH v4 00/11] Add la32 & va32 mode for loongarch64-softmmu Jiajie Chen
2023-08-08 1:54 ` [PATCH v4 01/11] target/loongarch: Add macro to check current arch Jiajie Chen
2023-08-08 17:01 ` Richard Henderson
2023-08-08 17:13 ` Jiajie Chen
2023-08-10 11:08 ` Philippe Mathieu-Daudé
2023-08-10 11:06 ` Philippe Mathieu-Daudé
2023-08-08 1:54 ` [PATCH v4 02/11] target/loongarch: Add new object class for loongarch32 cpus Jiajie Chen
2023-08-08 18:19 ` Richard Henderson [this message]
2023-08-08 1:54 ` [PATCH v4 03/11] target/loongarch: Add GDB support for loongarch32 mode Jiajie Chen
2023-08-08 18:34 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 04/11] target/loongarch: Support LoongArch32 TLB entry Jiajie Chen
2023-08-08 18:37 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 05/11] target/loongarch: Support LoongArch32 DMW Jiajie Chen
2023-08-08 18:37 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 06/11] target/loongarch: Support LoongArch32 VPPN Jiajie Chen
2023-08-08 18:38 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 07/11] target/loongarch: Add LA32 & VA32 to DisasContext Jiajie Chen
2023-08-08 18:40 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 08/11] target/loongarch: Reject la64-only instructions in la32 mode Jiajie Chen
2023-08-08 18:48 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 09/11] target/loongarch: Truncate high 32 bits of address in VA32 mode Jiajie Chen
2023-08-08 19:08 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 10/11] target/loongarch: Sign extend results " Jiajie Chen
2023-08-08 19:12 ` Richard Henderson
2023-08-08 1:54 ` [PATCH v4 11/11] target/loongarch: Add loongarch32 cpu la132 Jiajie Chen
2023-08-08 1:59 ` Jiajie Chen
2023-08-08 19:26 ` Richard Henderson
2023-08-09 7:31 ` Jiajie Chen
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=aec747e6-e780-d9b4-5bbd-74d830dd714e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=c@jia.je \
--cc=gaosong@loongson.cn \
--cc=i.qemu@xen0n.name \
--cc=qemu-devel@nongnu.org \
--cc=shenjinyang@loongson.cn \
--cc=yijun@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).