From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>
Subject: [PATCH-for-10.1? 0/3] linux-user: Select default CPUs for MicroMIPS and MIPS16e ASEs
Date: Thu, 14 Aug 2025 09:06:47 +0200 [thread overview]
Message-ID: <20250814070650.78657-1-philmd@linaro.org> (raw)
We weren't parsing MIPS ASE in the ELF header, so couldn't
automatically pick an appropriate CPU.
Since we'll have a rc4, I propose these sensible patches
for 10.1, but both ASEs are available since 15 years in QEMU,
so this isn't something broken since the latest release, and
I don't mind holding it for 10.2.
Regards,
Phil.
Philippe Mathieu-Daudé (3):
elf: Add EF_MIPS_ARCH_ASE definitions
linux-user/mips: Select 74Kf CPU to run MIPS16e binaries
linux-user/mips: Select M14Kc CPU to run microMIPS binaries
include/elf.h | 7 +++++++
linux-user/mips/target_elf.h | 6 ++++++
2 files changed, 13 insertions(+)
--
2.49.0
next reply other threads:[~2025-08-14 7:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 7:06 Philippe Mathieu-Daudé [this message]
2025-08-14 7:06 ` [PATCH-for-10.1? 1/3] elf: Add EF_MIPS_ARCH_ASE definitions Philippe Mathieu-Daudé
2025-08-14 7:06 ` [PATCH-for-10.1? 2/3] linux-user/mips: Select 74Kf CPU to run MIPS16e binaries Philippe Mathieu-Daudé
2025-08-14 7:06 ` [PATCH-for-10.1? 3/3] linux-user/mips: Select M14Kc CPU to run microMIPS binaries Philippe Mathieu-Daudé
2025-08-14 9:57 ` [PATCH-for-10.1? 0/3] linux-user: Select default CPUs for MicroMIPS and MIPS16e ASEs Richard Henderson
2025-08-14 10:22 ` Philippe Mathieu-Daudé
2025-08-14 13:42 ` Peter Maydell
2025-08-17 13:31 ` Stefan Hajnoczi
2025-09-02 10:59 ` Philippe Mathieu-Daudé
2025-09-04 20:15 ` Michael Tokarev
2025-09-22 6:59 ` Philippe Mathieu-Daudé
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=20250814070650.78657-1-philmd@linaro.org \
--to=philmd@linaro.org \
--cc=jiaxun.yang@flygoat.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
/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).