7bb77ea74f
- Introduce the SM4 cipher algorithms (OSCCA GB/T 32907-2016).
- intel_iommu: Add missed sanity check for 256-bit invalidation queue
- linux-user: use 'max' instead of 'qemu32' / 'qemu64' by default
- chardev/baum: Use definitions to avoid dynamic stack allocation
- ui/console: Get tab completion working again in the SDL monitor vc
- s390x/tcg: Fix opcode for lzrf
- virtiofsd: use g_date_time_get_microsecond to get subsecond
- ui/curses: Avoid dynamic stack allocation
- target/m68k: always call gen_exit_tb() after writes to SR
- target/m68k: Perform writback before modifying SR
- target/m68k: Fix MACSR to CCR
- target/m68k: Implement atomic test-and-set
- block/nvme: nvme_process_completion() fix bound for cid
- hw/pci-host: pnv_phb{3, 4}: Fix heap out-of-bound access failure
- target/ppc: Zero second doubleword of VSR registers for FPR insns
- target/ppc: Set OV32 when OV is set
- target/ppc: Zero second doubleword for VSX madd instructions
- target/ppc: Set result to QNaN for DENBCD when VXCVI occurs
- hw/pci: Add parenthesis to PCI_BUILD_BDF macro
- intel_iommu: Send IQE event when setting reserved bit in IQT_TAIL
- acpi: cpuhp: fix guest-visible maximum access size to the legacy reg block
- acpi: ged: Add macro for acpi sleep control register
- hw/pci-bridge: Add a Kconfig switch for the normal PCI bridge
- ui/vnc: fix handling of VNC_FEATURE_XVP
- s390/sclp: fix SCLP facility map
- docs/tools/qemu-img.rst: fix typo (sumarizes)
- chardev/char: fix qemu_chr_is_busy() check
- edu: fix DMA range upper bound check
- platform-bus: fix refcount leak
- hw/net/virtio-net: fix qemu set used ring flag even vhost started
- hw/net/can/sja1000: fix bug for single acceptance filter and standard frame
- tests/avocado: fix typo in replay_linux
- util/userfaultfd: Remove unused uffd_poll_events
- hw/core/ptimer: fix timer zero period condition for freq > 1GHz
- hcd-ohci: Drop ohci_service_iso_td() if ed->head & OHCI_DPTR_MASK is zero
- tests/unit/test-vmstate: Avoid dynamic stack allocation
- hw/usb/hcd-ohci: Use definition to avoid dynamic stack allocation
- hw/i386/multiboot: Avoid dynamic stack allocation
- hw/ppc/spapr: Fix code style problems reported by checkpatch
- chardev/baum: Replace magic values by X_MAX / Y_MAX definitions
- hw/intc/xics: Avoid dynamic stack allocation
- hw/net/e1000e_core: Use definition to avoid dynamic stack allocation
- intel_iommu: Fix invalidation descriptor type field
- configs: Fix typo in the sh4-softmmu devices config file
Signed-off-by: Jiabo Feng <fengjiabo1@huawei.com>
(cherry picked from commit 9813ed21ec2499c50cb58ac5fb114a1641708eb2)
83 lines
3.1 KiB
Diff
83 lines
3.1 KiB
Diff
From 9a09bf2b463cb0b98a71e335c6814143b23b3319 Mon Sep 17 00:00:00 2001
|
|
From: Liu Jing <liujing_yewu@cmss.chinamobile.com>
|
|
Date: Tue, 22 Oct 2024 04:52:33 +0800
|
|
Subject: [PATCH] linux-user: use 'max' instead of 'qemu32' / 'qemu64' by
|
|
default
|
|
MIME-Version: 1.0
|
|
Content-Type: text/plain; charset=UTF-8
|
|
Content-Transfer-Encoding: 8bit
|
|
|
|
The 'qemu64' CPU model implements the least featureful x86_64 CPU that's
|
|
possible. Historically this hasn't been an issue since it was rare for
|
|
OS distros to build with a higher mandatory CPU baseline.
|
|
|
|
With RHEL-9, however, the entire distro is built for the x86_64-v2 ABI
|
|
baseline:
|
|
|
|
https://developers.redhat.com/blog/2021/01/05/building-red-hat-enterprise-linux-9-for-the-x86-64-v2-microarchitecture-level
|
|
|
|
It is likely that other distros may take similar steps in the not too
|
|
distant future. For example, it has been suggested for Fedora on a
|
|
number of occasions.
|
|
|
|
This new baseline is not compatible with the qemu64 CPU model though.
|
|
While it is possible to pass a '-cpu xxx' flag to qemu-x86_64, the
|
|
usage of QEMU doesn't always allow for this. For example, the args
|
|
are typically controlled via binfmt rules that the user has no ability
|
|
to change. This impacts users who are trying to use podman on aarch64
|
|
platforms, to run containers with x86_64 content. There's no arg to
|
|
podman that can be used to change the qemu-x86_64 args, and a non-root
|
|
user of podman can not change binfmt rules without elevating privileges:
|
|
|
|
https://github.com/containers/podman/issues/15456#issuecomment-1228210973
|
|
|
|
Changing to the 'max' CPU model gives 'qemu-x86_64' maximum
|
|
compatibility with binaries it is likely to encounter in the wild,
|
|
and not likely to have a significant downside for existing usage.
|
|
|
|
Most other architectures already use an 'any' CPU model, which is
|
|
often mapped to 'max' (or similar) already, rather than the oldest
|
|
possible CPU model.
|
|
|
|
For the sake of consistency the 'i386' architecture is also changed
|
|
from using 'qemu32' to 'max'.
|
|
|
|
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
|
|
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
|
|
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
|
|
Message-Id: <20220923110413.70593-1-berrange@redhat.com>
|
|
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
|
|
Signed-off-by: Liu Jing <liujing_yewu@cmss.chinamobile.com>
|
|
---
|
|
linux-user/i386/target_elf.h | 2 +-
|
|
linux-user/x86_64/target_elf.h | 2 +-
|
|
2 files changed, 2 insertions(+), 2 deletions(-)
|
|
|
|
diff --git a/linux-user/i386/target_elf.h b/linux-user/i386/target_elf.h
|
|
index 1c6142e7da..238a9aba73 100644
|
|
--- a/linux-user/i386/target_elf.h
|
|
+++ b/linux-user/i386/target_elf.h
|
|
@@ -9,6 +9,6 @@
|
|
#define I386_TARGET_ELF_H
|
|
static inline const char *cpu_get_model(uint32_t eflags)
|
|
{
|
|
- return "qemu32";
|
|
+ return "max";
|
|
}
|
|
#endif
|
|
diff --git a/linux-user/x86_64/target_elf.h b/linux-user/x86_64/target_elf.h
|
|
index 7b76a90de8..3f628f8d66 100644
|
|
--- a/linux-user/x86_64/target_elf.h
|
|
+++ b/linux-user/x86_64/target_elf.h
|
|
@@ -9,6 +9,6 @@
|
|
#define X86_64_TARGET_ELF_H
|
|
static inline const char *cpu_get_model(uint32_t eflags)
|
|
{
|
|
- return "qemu64";
|
|
+ return "max";
|
|
}
|
|
#endif
|
|
--
|
|
2.41.0.windows.1
|
|
|