From: Magnus Kulke <magnuskulke@linux.microsoft.com>
To: Wei Liu <wei.liu@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [CFT PATCH 0/4] target/i386/emulate: cleanups
Date: Fri, 9 May 2025 14:56:10 +0200 [thread overview]
Message-ID: <aB37anHZZtdO5BVY@example.com> (raw)
In-Reply-To: <aBkEvxV3b_ilLtY3@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
Hey Paolo,
I applied your patches to the x86 emulator in our MSHV branch. They
compile cleanly (some off this we had changed on our branch already). I
also performed some manual testing and didn't spot any regressions with
the changes in the emulator.
magnus
already). I also performed some manual testing and didn't spot any regressions with
the emulator.
On Mon, May 05, 2025 at 06:34:39PM +0000, Wei Liu wrote:
> Magnus, can you test this series on MSHV?
>
> On Fri, May 02, 2025 at 11:48:37PM +0200, Paolo Bonzini wrote:
> > These are some improvements to the x86 emulator that I wrote but have no
> > way of testing (right now).
> >
> > I tried to place them in order of importance so that, if something breaks,
> > it is possible to commit a subset. I tried to compile the resulting code
> > on Linux but I have not run it.
> >
> > Patch 1 is just to fix warnings on Linux.
> >
> > Patch 2 is the most important, as it fixes some real horrors in the code.
> >
> > Patch 3 makes flags handling use algorithms somewhat similar to TCG.
> > It should fix issues with 64-bit ALU operations, but it's also the one
> > where it's more likely to have a mistake.
> >
> > Patch 4 is comparatively trivial, though I cannot exclude any screwups.
> >
> > It should be possible to test this with both HVF and Hyper-V.
> >
> > Paolo
> >
> > Paolo Bonzini (4):
> > target/i386/emulate: fix target_ulong format strings
> > target/i386/emulate: stop overloading decode->op[N].ptr
> > target/i386/emulate: mostly rewrite flags handling
> > target/i386: remove lflags
> >
> > target/i386/cpu.h | 6 -
> > target/i386/emulate/x86_decode.h | 9 +-
> > target/i386/emulate/x86_emu.h | 8 +-
> > target/i386/emulate/x86_flags.h | 12 +-
> > target/i386/emulate/x86_decode.c | 76 ++++++------
> > target/i386/emulate/x86_emu.c | 125 +++++++++----------
> > target/i386/emulate/x86_flags.c | 198 +++++++++++++------------------
> > 7 files changed, 197 insertions(+), 237 deletions(-)
> >
> > --
> > 2.49.0
> >
prev parent reply other threads:[~2025-05-09 12:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 21:48 [CFT PATCH 0/4] target/i386/emulate: cleanups Paolo Bonzini
2025-05-02 21:48 ` [PATCH 1/4] target/i386/emulate: fix target_ulong format strings Paolo Bonzini
2025-05-02 21:48 ` [PATCH 2/4] target/i386/emulate: stop overloading decode->op[N].ptr Paolo Bonzini
2025-05-03 10:46 ` BALATON Zoltan
2025-05-05 9:43 ` Philippe Mathieu-Daudé
2025-05-05 10:00 ` Paolo Bonzini
2025-05-05 10:54 ` Philippe Mathieu-Daudé
2025-05-05 12:59 ` Paolo Bonzini
2025-05-05 18:11 ` Pierrick Bouvier
2025-05-05 19:33 ` Richard Henderson
2025-05-02 21:48 ` [PATCH 3/4] target/i386/emulate: mostly rewrite flags handling Paolo Bonzini
2025-05-02 21:48 ` [PATCH 4/4] target/i386: remove lflags Paolo Bonzini
2025-05-03 5:38 ` [CFT PATCH 0/4] target/i386/emulate: cleanups Wei Liu
2025-05-03 7:01 ` Paolo Bonzini
2025-05-05 18:33 ` Wei Liu
2025-05-05 18:34 ` Wei Liu
2025-05-09 12:56 ` Magnus Kulke [this message]
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=aB37anHZZtdO5BVY@example.com \
--to=magnuskulke@linux.microsoft.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.liu@kernel.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).