From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PATCH 0/9] Host-specific includes, begin cpuinfo.h
Date: Wed, 17 May 2023 21:40:49 -0700 [thread overview]
Message-ID: <20230518044058.2777467-1-richard.henderson@linaro.org> (raw)
Hiya.
This is looking toward cleaning up a couple of things:
(1) There are 5 bits of x86 host detection, 3 of them for xbzrle.
Unify this down to one, with additional cleanups for xbzrle.
(2) Provides a host-specific include path for splitting atomic128.h
and probably other stuff so as to avoid host-specific ifdefs.
Actually splitting atomic128.h is so far left for further work.
r~
Richard Henderson (9):
util: Introduce host-specific cpuinfo.h
util: Add cpuinfo-i386.c
util: Add i386 CPUINFO_ATOMIC_VMOVDQU
tcg/i386: Use cpuinfo.h
util/bufferiszero: Use i386 cpuinfo.h
migration/xbzrle: Shuffle function order
migration/xbzrle: Use i386 cacheinfo.h
migration: Build migration_files once
util: Add cpuinfo-aarch64.c
include/host/aarch64/cpuinfo.h | 22 ++
include/host/generic/cpuinfo.h | 4 +
include/host/i386/cpuinfo.h | 39 +++
include/host/x86_64/cpuinfo.h | 1 +
migration/xbzrle.h | 5 +-
tcg/aarch64/tcg-target.h | 4 +-
tcg/i386/tcg-target.h | 28 +-
migration/ram.c | 34 +--
migration/xbzrle.c | 268 ++++++++++---------
tests/bench/xbzrle-bench.c | 469 ---------------------------------
tests/unit/test-xbzrle.c | 49 +---
util/bufferiszero.c | 126 ++++-----
util/cpuinfo-aarch64.c | 67 +++++
util/cpuinfo-i386.c | 99 +++++++
meson.build | 8 +
migration/meson.build | 1 -
tcg/aarch64/tcg-target.c.inc | 41 +--
tcg/i386/tcg-target.c.inc | 123 +--------
tests/bench/meson.build | 6 -
util/meson.build | 6 +
20 files changed, 476 insertions(+), 924 deletions(-)
create mode 100644 include/host/aarch64/cpuinfo.h
create mode 100644 include/host/generic/cpuinfo.h
create mode 100644 include/host/i386/cpuinfo.h
create mode 100644 include/host/x86_64/cpuinfo.h
delete mode 100644 tests/bench/xbzrle-bench.c
create mode 100644 util/cpuinfo-aarch64.c
create mode 100644 util/cpuinfo-i386.c
--
2.34.1
next reply other threads:[~2023-05-18 4:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 4:40 Richard Henderson [this message]
2023-05-18 4:40 ` [PATCH 1/9] util: Introduce host-specific cpuinfo.h Richard Henderson
2023-05-18 9:30 ` Juan Quintela
2023-05-18 4:40 ` [PATCH 2/9] util: Add cpuinfo-i386.c Richard Henderson
2023-05-18 9:35 ` Juan Quintela
2023-05-18 12:45 ` Richard Henderson
2023-05-18 4:40 ` [PATCH 3/9] util: Add i386 CPUINFO_ATOMIC_VMOVDQU Richard Henderson
2023-05-18 15:52 ` Peter Maydell
2023-05-18 4:40 ` [PATCH 4/9] tcg/i386: Use cpuinfo.h Richard Henderson
2023-05-18 15:53 ` Peter Maydell
2023-05-18 4:40 ` [PATCH 5/9] util/bufferiszero: Use i386 cpuinfo.h Richard Henderson
2023-05-18 9:49 ` Juan Quintela
2023-05-18 12:48 ` Richard Henderson
2023-05-18 4:40 ` [PATCH 6/9] migration/xbzrle: Shuffle function order Richard Henderson
2023-05-18 9:19 ` Juan Quintela
2023-05-18 4:40 ` [PATCH 7/9] migration/xbzrle: Use i386 cacheinfo.h Richard Henderson
2023-05-18 9:44 ` Juan Quintela
2023-05-18 4:40 ` [PATCH 8/9] migration: Build migration_files once Richard Henderson
2023-05-18 9:20 ` Juan Quintela
2023-05-18 4:40 ` [PATCH 9/9] util: Add cpuinfo-aarch64.c Richard Henderson
2023-05-18 15:55 ` Peter Maydell
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=20230518044058.2777467-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=peter.maydell@linaro.org \
--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).