All TARGET_LOONGARCH64 qapis are also available for LoongArch32 as we
are reusing the same CPU backend implemenation.

Use TARGET_LOONGARCH to identify LoongArch.

Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
---
 qapi/machine-target.json | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/qapi/machine-target.json b/qapi/machine-target.json
index 541f93eeb78f67c7eac83d8a2722000976e38a33..b00c3f59b6a5f6e3ad9d7197d462e928ffc4c152 100644
--- a/qapi/machine-target.json
+++ b/qapi/machine-target.json
@@ -260,7 +260,7 @@
   'if': { 'any': [ 'TARGET_S390X',
                    'TARGET_I386',
                    'TARGET_ARM',
-                   'TARGET_LOONGARCH64',
+                   'TARGET_LOONGARCH',
                    'TARGET_RISCV' ] } }
 
 ##
@@ -314,7 +314,7 @@
   'if': { 'any': [ 'TARGET_S390X',
                    'TARGET_I386',
                    'TARGET_ARM',
-                   'TARGET_LOONGARCH64',
+                   'TARGET_LOONGARCH',
                    'TARGET_RISCV' ] } }
 
 ##
@@ -383,7 +383,7 @@
                    'TARGET_I386',
                    'TARGET_S390X',
                    'TARGET_MIPS',
-                   'TARGET_LOONGARCH64',
+                   'TARGET_LOONGARCH',
                    'TARGET_RISCV' ] } }
 
 ##
@@ -401,7 +401,7 @@
                    'TARGET_I386',
                    'TARGET_S390X',
                    'TARGET_MIPS',
-                   'TARGET_LOONGARCH64',
+                   'TARGET_LOONGARCH',
                    'TARGET_RISCV' ] } }
 
 ##

-- 
2.43.0

Jiaxun Yang <jiaxun.yang@flygoat.com> writes:

> All TARGET_LOONGARCH64 qapis are also available for LoongArch32 as we
> are reusing the same CPU backend implemenation.

As far as I can tell this makes query-cpu-model-expansion and
query-cpu-definitions in the LoongArch32 build, too.

> Use TARGET_LOONGARCH to identify LoongArch.

Suggest to be more explicit. e.g. like this:

  The QAPI commands specific to target loongarch64 are wanted for
  loongarch32, too.  These are query-cpu-model-expansion and
  query-cpu-definitions.  They just work, since the two use the same CPU
  implementation.

  Replace TARGET_LOONGARCH64 by TARGET_LOONGARCH.

> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>

Preferably with an improved commit message
Acked-by: Markus Armbruster <armbru@redhat.com>