From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>,
Peter Xu <peterx@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Mark Burton" <mburton@qti.qualcomm.com>
Subject: [PATCH 0/2] Make ioport.c target-independent
Date: Wed, 17 May 2023 09:42:20 +0200 [thread overview]
Message-ID: <20230517074222.766683-1-thuth@redhat.com> (raw)
Assuming that the code in ioport.c is not too performance critical,
we can move this to the target-independent source set after
reworking the ld*_p and st*_p helper functions a little bit.
This way, ioport.c has only to be compiled once and not multiple
times anymore (one time for each target), so this should help
to speed up the compilation process a little bit, and is a good
preparation for the single emulator binary project.
Thomas Huth (2):
include/exec: Make ld*_p and st*_p functions available for generic
code, too
softmmu: Move ioport.c into the target-independent source set
include/exec/cpu-all.h | 25 ----------------
include/exec/tswap.h | 66 ++++++++++++++++++++++++++++++++++++++++++
softmmu/ioport.c | 2 +-
softmmu/meson.build | 2 +-
4 files changed, 68 insertions(+), 27 deletions(-)
--
2.31.1
next reply other threads:[~2023-05-17 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 7:42 Thomas Huth [this message]
2023-05-17 7:42 ` [PATCH 1/2] include/exec: Make ld*_p and st*_p functions available for generic code, too Thomas Huth
2023-05-17 10:18 ` Philippe Mathieu-Daudé
2023-05-17 10:38 ` Thomas Huth
2023-05-17 13:20 ` Richard Henderson
2023-05-17 7:42 ` [PATCH 2/2] softmmu: Move ioport.c into the target-independent source set Thomas Huth
2023-05-17 13:23 ` 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=20230517074222.766683-1-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=mburton@qti.qualcomm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).