aboutsummaryrefslogtreecommitdiff
path: root/tests/functional/qemu_test/linuxkernel.py
diff options
context:
space:
mode:
authorAndrea Bolognani <abologna@redhat.com>2025-01-27 19:29:23 +0100
committerAlistair Francis <alistair.francis@wdc.com>2025-03-04 15:42:54 +1000
commit2770a46b20b7ccd23019a7b6b6631de933b53c8e (patch)
treeef64f17caf40f66d1399df9796cfc8144287bec7 /tests/functional/qemu_test/linuxkernel.py
parentc869f4129c8e35f3c234d757c0227c53134aca16 (diff)
downloadqemu-2770a46b20b7ccd23019a7b6b6631de933b53c8e.zip
qemu-2770a46b20b7ccd23019a7b6b6631de933b53c8e.tar.gz
qemu-2770a46b20b7ccd23019a7b6b6631de933b53c8e.tar.bz2
binfmt: Normalize host CPU architecture
Right now information regarding the family each CPU type belongs to is recorded in two places: the large data table at the top of the script, and the qemu_host_family() function. We can make things better by mapping host CPU architecture to QEMU target in the few cases where the two don't already match and then using the data table to look up the family, same as we're already doing for the guest CPU architecture. Being able to reason in terms of QEMU target regardless of whether we're looking at the host or guest CPU architecture will come in handy to implement upcoming changes. A couple of entries are dropped in the process: BePC and Power Macintosh. I'm quite certain neither of those have ever been reported as CPU architectures by Linux. I believe many more of the entries that are carried forward could be dropped as well, but I don't have the same level of confidence there so I decided to play it safe just in case. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Alistair Francis <alistair.francis@wdc.com> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Message-ID: <20250127182924.103510-3-abologna@redhat.com> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Diffstat (limited to 'tests/functional/qemu_test/linuxkernel.py')
0 files changed, 0 insertions, 0 deletions