From: Bernhard Beschow <shentey@gmail.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Bernhard Beschow <shentey@gmail.com>,
Richard Henderson <richard.henderson@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH 09/11] accel/tcg/cpu-exec: Unexport dump_drift_info()
Date: Thu, 5 May 2022 18:18:03 +0200 [thread overview]
Message-ID: <20220505161805.11116-10-shentey@gmail.com> (raw)
In-Reply-To: <20220505161805.11116-1-shentey@gmail.com>
Commit 3a841ab53f165910224dc4bebabf1a8f1d04200c 'qapi: introduce
x-query-jit QMP command' basically moved the only function using
dump_drift_info() to cpu-exec.c. Therefore, dump_drift_info() doesn't
need to be exported any longer.
Signed-off-by: Bernhard Beschow <shentey@gmail.com>
---
accel/tcg/cpu-exec.c | 2 +-
include/exec/cpu-all.h | 2 --
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/accel/tcg/cpu-exec.c b/accel/tcg/cpu-exec.c
index 635aeecc0a..7cbf9996b7 100644
--- a/accel/tcg/cpu-exec.c
+++ b/accel/tcg/cpu-exec.c
@@ -1048,7 +1048,7 @@ void tcg_exec_unrealizefn(CPUState *cpu)
#ifndef CONFIG_USER_ONLY
-void dump_drift_info(GString *buf)
+static void dump_drift_info(GString *buf)
{
if (!icount_enabled()) {
return;
diff --git a/include/exec/cpu-all.h b/include/exec/cpu-all.h
index 5d5290deb5..9a716be80d 100644
--- a/include/exec/cpu-all.h
+++ b/include/exec/cpu-all.h
@@ -419,8 +419,6 @@ static inline bool tlb_hit(target_ulong tlb_addr, target_ulong addr)
}
#ifdef CONFIG_TCG
-/* accel/tcg/cpu-exec.c */
-void dump_drift_info(GString *buf);
/* accel/tcg/translate-all.c */
void dump_exec_info(GString *buf);
void dump_opcount_info(GString *buf);
--
2.36.0
next prev parent reply other threads:[~2022-05-05 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 16:17 [PATCH 00/11] Random cleanup patches Bernhard Beschow
2022-05-05 16:17 ` [PATCH 01/11] hw/rtc/mc146818rtc: Inline isa_connect_gpio_out() and remove it Bernhard Beschow
2022-05-09 12:09 ` Philippe Mathieu-Daudé
2022-05-11 10:24 ` Mark Cave-Ayland
2022-05-13 10:34 ` Bernhard Beschow
2022-05-05 16:17 ` [PATCH 02/11] hw: Reuse TYPE_I8042 define Bernhard Beschow
2022-05-09 12:12 ` Philippe Mathieu-Daudé via
2022-05-05 16:17 ` [PATCH 03/11] hw/audio/cs4231a: Const'ify global tables Bernhard Beschow
2022-05-09 12:13 ` Philippe Mathieu-Daudé via
2022-05-05 16:17 ` [PATCH 04/11] hw/i386/pc: Unexport PC_CPU_MODEL_IDS macro Bernhard Beschow
2022-05-05 16:17 ` [PATCH 05/11] hw/i386/pc: Unexport functions used only internally Bernhard Beschow
2022-05-09 12:14 ` Philippe Mathieu-Daudé via
2022-05-05 16:18 ` [PATCH 06/11] hw/i386/pc: Remove orphan declarations Bernhard Beschow
2022-05-05 16:18 ` [PATCH 07/11] hw/ppc/e500: Remove unused BINARY_DEVICE_TREE_FILE Bernhard Beschow
2022-05-05 16:59 ` Daniel Henrique Barboza
2022-05-05 16:18 ` [PATCH 08/11] hw/net/fsl_etsec/etsec: Remove obsolete and unused etsec_create() Bernhard Beschow
2022-05-09 12:15 ` Philippe Mathieu-Daudé via
2022-05-05 16:18 ` Bernhard Beschow [this message]
2022-05-05 16:18 ` [PATCH 10/11] accel/tcg: Inline dump_opcount_info() and remove it Bernhard Beschow
2022-05-05 16:18 ` [PATCH 11/11] docs/devel: Fix link to developer mailing lists Bernhard Beschow
2022-05-13 11:27 ` [PATCH 00/11] Random cleanup patches Michael S. Tsirkin
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=20220505161805.11116-10-shentey@gmail.com \
--to=shentey@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).