From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Riku Voipio" <riku.voipio@iki.fi>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [PATCH 1/3] linux-user: Only include 'exec/tb-flush.h' header when necessary
Date: Tue, 21 Jan 2025 16:41:20 -0800 [thread overview]
Message-ID: <6e577f6b-00bc-4482-b3cf-b0106edfe6e3@linaro.org> (raw)
In-Reply-To: <20250102182521.65428-2-philmd@linaro.org>
On 1/2/25 10:25, Philippe Mathieu-Daudé wrote:
> Very few source files require to access "exec/tb-flush.h"
> declarations, and except a pair, they all include it
> explicitly. No need to overload the generic "user-internals.h".
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> linux-user/user-internals.h | 1 -
> linux-user/mmap.c | 1 +
> linux-user/syscall.c | 1 +
> 3 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/linux-user/user-internals.h b/linux-user/user-internals.h
> index b9b05c1d11f..4aa253b5663 100644
> --- a/linux-user/user-internals.h
> +++ b/linux-user/user-internals.h
> @@ -20,7 +20,6 @@
>
> #include "user/thunk.h"
> #include "exec/exec-all.h"
> -#include "exec/tb-flush.h"
> #include "qemu/log.h"
>
> extern char *exec_path;
> diff --git a/linux-user/mmap.c b/linux-user/mmap.c
> index 6828b17a63f..d1f36e6f16b 100644
> --- a/linux-user/mmap.c
> +++ b/linux-user/mmap.c
> @@ -21,6 +21,7 @@
> #include "trace.h"
> #include "exec/log.h"
> #include "exec/page-protection.h"
> +#include "exec/tb-flush.h"
> #include "exec/translation-block.h"
> #include "qemu.h"
> #include "user/page-protection.h"
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 78c7c0b34ef..cbbfcf10d28 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -26,6 +26,7 @@
> #include "tcg/startup.h"
> #include "target_mman.h"
> #include "exec/page-protection.h"
> +#include "exec/tb-flush.h"
> #include "exec/translation-block.h"
> #include <elf.h>
> #include <endian.h>
Reviewed-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
next prev parent reply other threads:[~2025-01-22 0:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 18:25 [PATCH 0/3] linux-user: Call tcg_flush_jmp_cache() before re-using threads Philippe Mathieu-Daudé
2025-01-02 18:25 ` [PATCH 1/3] linux-user: Only include 'exec/tb-flush.h' header when necessary Philippe Mathieu-Daudé
2025-01-09 22:13 ` Ilya Leoshkevich
2025-01-22 0:41 ` Pierrick Bouvier [this message]
2025-01-02 18:25 ` [PATCH 2/3] accel/tcg: Factor out common tcg_exec_reset() helper Philippe Mathieu-Daudé
2025-01-09 22:16 ` Ilya Leoshkevich
2025-01-22 0:41 ` Pierrick Bouvier
2025-01-02 18:25 ` [PATCH 3/3] accel/tcg: Implement cpu_exec_reset_hold() on user emulation Philippe Mathieu-Daudé
2025-01-09 23:43 ` Ilya Leoshkevich
2025-01-14 20:52 ` Ilya Leoshkevich
2025-01-22 0:46 ` Pierrick Bouvier
2025-01-09 10:59 ` [PATCH 0/3] linux-user: Call tcg_flush_jmp_cache() before re-using threads Philippe Mathieu-Daudé
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=6e577f6b-00bc-4482-b3cf-b0106edfe6e3@linaro.org \
--to=pierrick.bouvier@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=riku.voipio@iki.fi \
/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).