From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [PULL 00/10] x86, mtest2make changes for QEMU 10.2
Date: Thu, 20 Nov 2025 01:16:39 +0100 [thread overview]
Message-ID: <20251120001649.1085913-1-pbonzini@redhat.com> (raw)
The following changes since commit e88510fcdc13380bd4895a17d6f8a0b3a3325b85:
Merge tag 'pull-target-arm-20251114' of https://gitlab.com/pm215/qemu into staging (2025-11-14 17:59:05 +0100)
are available in the Git repository at:
https://gitlab.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to 58f88d0bf7c4c0676b54f97ba91eecccbca968c9:
replay: add tracing events (2025-11-19 09:24:01 +0100)
----------------------------------------------------------------
* i386 fixes
* mtest2make cleanups to enable per-speed dependencies
* record/replay tracepoints
----------------------------------------------------------------
Nguyen Dinh Phi (1):
target/i386: emulate: Make sure fetch_instruction exist before calling it
Paolo Bonzini (8):
ioapic: fix typo in irqfd check
target/i386/tcg: validate segment registers
target/i386: svm: fix sign extension of exit code
target/i386: fix stack size when delivering real mode interrupts
mtest2make: cleanup mtest-suites variables
mtest2make: add dependencies to the "speed-qualified" suite
mtest2make: do not repeat the same speed over and over
replay: add tracing events
Peter Maydell (1):
target/i386: Mark VPERMILPS as not valid with prefix 0
Makefile | 4 ++-
meson.build | 1 +
replay/trace.h | 1 +
target/i386/tcg/helper-tcg.h | 2 +-
hw/intc/ioapic.c | 4 +--
replay/replay-internal.c | 70 ++++++++++++++++++++++++++++---------
target/i386/emulate/x86_decode.c | 6 +++-
target/i386/tcg/seg_helper.c | 4 +--
target/i386/tcg/system/svm_helper.c | 6 ++--
target/i386/tcg/decode-new.c.inc | 9 +++--
replay/trace-events | 12 +++++++
scripts/mtest2make.py | 46 ++++++++++++------------
12 files changed, 112 insertions(+), 53 deletions(-)
create mode 100644 replay/trace.h
create mode 100644 replay/trace-events
--
2.51.1
next reply other threads:[~2025-11-20 0:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 0:16 Paolo Bonzini [this message]
2025-11-20 0:16 ` [PULL 01/10] ioapic: fix typo in irqfd check Paolo Bonzini
2025-11-20 0:16 ` [PULL 02/10] target/i386: emulate: Make sure fetch_instruction exist before calling it Paolo Bonzini
2025-11-20 0:16 ` [PULL 03/10] target/i386: Mark VPERMILPS as not valid with prefix 0 Paolo Bonzini
2025-11-20 0:16 ` [PULL 04/10] target/i386/tcg: validate segment registers Paolo Bonzini
2025-11-20 0:16 ` [PULL 05/10] target/i386: svm: fix sign extension of exit code Paolo Bonzini
2025-11-20 0:16 ` [PULL 06/10] target/i386: fix stack size when delivering real mode interrupts Paolo Bonzini
2025-11-20 0:16 ` [PULL 07/10] mtest2make: cleanup mtest-suites variables Paolo Bonzini
2025-11-20 0:16 ` [PULL 08/10] mtest2make: add dependencies to the "speed-qualified" suite Paolo Bonzini
2025-11-20 0:16 ` [PULL 09/10] mtest2make: do not repeat the same speed over and over Paolo Bonzini
2025-11-20 0:16 ` [PULL 10/10] replay: add tracing events Paolo Bonzini
2025-11-20 21:56 ` [PULL 00/10] x86, mtest2make changes for QEMU 10.2 Richard Henderson
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=20251120001649.1085913-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--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).