From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Subject: Re: [PATCH 07/10] plugins/api: split out binary path/start/end/entry code
Date: Tue, 25 Feb 2025 10:32:19 -0800 [thread overview]
Message-ID: <5c79e077-138c-4013-bdd6-0719dfe1e26f@linaro.org> (raw)
In-Reply-To: <20250225110844.3296991-8-alex.bennee@linaro.org>
On 2/25/25 03:08, Alex Bennée wrote:
> To move the main api.c to a single build compilation object we need to
> start splitting out user and system specific code. As we need to grob
> around host headers we move these particular helpers into the *-user
> mode directories.
>
> The binary/start/end/entry helpers are all NOPs for system mode.
>
> Signed-off-by: Alex Bennée<alex.bennee@linaro.org>
> ---
> linux-user/plugin-api.c | 43 +++++++++++++++++++++++++++++++++++++++++
> plugins/api-system.c | 39 +++++++++++++++++++++++++++++++++++++
> plugins/api.c | 43 -----------------------------------------
> linux-user/meson.build | 1 +
> plugins/meson.build | 2 +-
> 5 files changed, 84 insertions(+), 44 deletions(-)
> create mode 100644 linux-user/plugin-api.c
> create mode 100644 plugins/api-system.c
Surely this breaks bsd-user.
Ideally this would go in common-user, but I think you'd need to move structures out of
{bsd,linux}-user/qemu.h into include/user/.
In the very short term you could put plugin-api.c.inc in common-user, and
#include "qemu.h"
#include "common-user/plugin-api.c.inc"
in both linux-user and bsd-user.
r~
next prev parent reply other threads:[~2025-02-25 18:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 11:08 [PATCH 00/10] plugins: reduce total number of build objects Alex Bennée
2025-02-25 11:08 ` [PATCH 01/10] plugins/api: use tcg_ctx to get TARGET_PAGE_MASK Alex Bennée
2025-02-25 14:57 ` Philippe Mathieu-Daudé
2025-02-25 16:00 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 02/10] plugins/loader: populate target_name with target_name() Alex Bennée
2025-02-25 14:58 ` Philippe Mathieu-Daudé
2025-02-25 18:04 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 03/10] include/qemu: plugin-memory.h doesn't need cpu-defs.h Alex Bennée
2025-02-25 18:10 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 04/10] plugins/api: clean-up the includes Alex Bennée
2025-02-25 18:14 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 05/10] plugins/plugin.h: include queue.h Alex Bennée
2025-02-25 18:15 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 06/10] plugins/loader: compile loader only once Alex Bennée
2025-02-25 18:18 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 07/10] plugins/api: split out binary path/start/end/entry code Alex Bennée
2025-02-25 18:32 ` Richard Henderson [this message]
2025-02-25 18:57 ` Alex Bennée
2025-02-25 11:08 ` [PATCH 08/10] plugins/api: split out the vaddr/hwaddr helpers Alex Bennée
2025-02-25 18:40 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 09/10] plugins/api: split out time control helpers Alex Bennée
2025-02-25 18:45 ` Richard Henderson
2025-02-25 11:08 ` [PATCH 10/10] plugins/api: build only once Alex Bennée
2025-02-25 18:46 ` Richard Henderson
2025-02-25 19:21 ` [PATCH 00/10] plugins: reduce total number of build objects Pierrick Bouvier
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=5c79e077-138c-4013-bdd6-0719dfe1e26f@linaro.org \
--to=richard.henderson@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).