From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Pierrick Bouvier <pierrick.bouvier@linaro.org>, qemu-devel@nongnu.org
Cc: Warner Losh <imp@bsdimp.com>,
richard.henderson@linaro.org, alex.bennee@linaro.org,
Kyle Evans <kevans@freebsd.org>
Subject: Re: [PATCH] bsd-user: add option to enable plugins
Date: Tue, 1 Apr 2025 20:50:40 +0200 [thread overview]
Message-ID: <44720e82-808c-4749-917b-bcc0d1c92d1d@linaro.org> (raw)
In-Reply-To: <0c042bd1-7ff9-4ac9-8c75-0f0c63d43132@linaro.org>
On 1/4/25 16:59, Pierrick Bouvier wrote:
> On 4/1/25 07:44, Philippe Mathieu-Daudé wrote:
>> On 1/4/25 16:33, Pierrick Bouvier wrote:
>>> On 3/31/25 23:15, Philippe Mathieu-Daudé wrote:
>>>> Hi Pierrick,
>>>>
>>>> On 1/4/25 01:42, Pierrick Bouvier wrote:
>>>>> Nothing prevent plugins to be enabled on this platform for user
>>>>> binaries, only the option in the driver is missing.
>>>>
>>>> Per commit 903e870f245 ("plugins/api: split out binary
>>>> path/start/end/entry code") this is deliberate:
>>>>
>>>> The BSD user-mode command line is still missing -plugin.
>>>> This can be enabled once we have reliable check-tcg tests
>>>> working for the BSDs.
>>>>
>>>> Should we enable this without test harnessing?
>>>>
>>>
>>> Thanks for pointing this.
>>>
>>> However, I don't get the argument, as the same could be said about
>>> system mode, which runs on BSD also, and already has plugins enabled.
>>> The coupling between user related code and plugins is very low (just
>>> options parsing and init code), so I don't see why we could have a bug
>>> related to a specific platform only for user binaries.
>>>
>>> So either we deactivate plugins completely for bsd binaries, or we take
>>> a leap of faith that it works for them.
>>>
>>> @Alex, any further insight on this?
>>>
>>>>> Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
>>>>> ---
>>>>> bsd-user/main.c | 12 ++++++++++++
>>>>> 1 file changed, 12 insertions(+)
>>>>
>>>> Ideally we'd have helpers for common user code in common-user/...
>>>>
>>>
>>> Everything is already common for plugins, except adding the call to
>>> plugin command line option parsing function.
>>
>> Yeah, I mean the rest of main() ;)
>>
>
> It's not a priority at the moment, and not blocking anything on our
> path, but yes, it would be nice to share more ideally.
Just to be clear, I was not asking you to do that suggestion.
>>>> Anyway, since this patch does what it says:
>>>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>>>
>>>
>>> Thanks,
>>> Pierrick
>>>
>>
>
next prev parent reply other threads:[~2025-04-01 18:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 23:42 [PATCH] bsd-user: add option to enable plugins Pierrick Bouvier
2025-03-31 23:50 ` Pierrick Bouvier
2025-04-01 6:15 ` Philippe Mathieu-Daudé
2025-04-01 14:33 ` Pierrick Bouvier
2025-04-01 14:44 ` Philippe Mathieu-Daudé
2025-04-01 14:59 ` Pierrick Bouvier
2025-04-01 18:50 ` Philippe Mathieu-Daudé [this message]
2025-04-28 19:36 ` Pierrick Bouvier
2025-04-28 22:57 ` Kyle Evans
2025-04-28 23:03 ` Pierrick Bouvier
2025-05-05 18:38 ` Pierrick Bouvier
2025-05-06 0:25 ` Warner Losh
2025-05-06 8:24 ` Philippe Mathieu-Daudé
2025-05-08 12:18 ` 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=44720e82-808c-4749-917b-bcc0d1c92d1d@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=pierrick.bouvier@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).