From: Claudio Fontana <cfontana@suse.de>
To: Richard Henderson <richard.henderson@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
dinechin@redhat.com, "Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH] accel: print an error message and exit if plugin not loaded
Date: Mon, 5 Sep 2022 16:36:37 +0200 [thread overview]
Message-ID: <9bb31e44-e43d-b51a-712a-87e46279a0b5@suse.de> (raw)
In-Reply-To: <5d922305-a559-bfdc-7038-ec1560ae0e00@linaro.org>
On 9/5/22 14:06, Richard Henderson wrote:
> On 9/5/22 11:13, Claudio Fontana wrote:
>> If module_load_one, module_load_file fail for any reason
>> (permissions, plugin not installed, ...), we need to provide some notification
>> to the user to understand that this is happening; otherwise the errors
>> reported on initialization will make no sense to the user.
>>
>> Signed-off-by: Claudio Fontana <cfontana@suse.de>
>> ---
>> accel/accel-softmmu.c | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/accel/accel-softmmu.c b/accel/accel-softmmu.c
>> index 67276e4f52..807708ee86 100644
>> --- a/accel/accel-softmmu.c
>> +++ b/accel/accel-softmmu.c
>> @@ -66,15 +66,21 @@ void accel_init_ops_interfaces(AccelClass *ac)
>> {
>> const char *ac_name;
>> char *ops_name;
>> + ObjectClass *oc;
>> AccelOpsClass *ops;
>>
>> ac_name = object_class_get_name(OBJECT_CLASS(ac));
>> g_assert(ac_name != NULL);
>>
>> ops_name = g_strdup_printf("%s" ACCEL_OPS_SUFFIX, ac_name);
>> - ops = ACCEL_OPS_CLASS(module_object_class_by_name(ops_name));
>> + oc = module_object_class_by_name(ops_name);
>> + if (!oc) {
>> + error_report("fatal: could not find module object of type \"%s\", "
>> + "plugin might not be loaded correctly", ops_name);
>> + exit(EXIT_FAILURE);
>> + }
>
> The change is correct, in that we certainly cannot continue without the accelerator loaded.
>
> But I'm very disappointed that the module interface does not use Error, so you have no
> choice but to use an extremely vague message here. I would much prefer to plumb down an
> error parameter so that here one could simply pass &error_fatal.
>
>
> r~
>
I agree. I see it as also connected to:
https://lists.gnu.org/archive/html/qemu-devel/2022-09/msg00578.html
module_load_file actually has the pertinent information of what it going wrong at the time it goes wrong, so I presume we should collect the Error there,
and find a way not to lose the return value along the way..
Claudio
next prev parent reply other threads:[~2022-09-05 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 10:13 [PATCH] accel: print an error message and exit if plugin not loaded Claudio Fontana
2022-09-05 12:06 ` Richard Henderson
2022-09-05 14:36 ` Claudio Fontana [this message]
2022-09-05 15:43 ` Claudio Fontana
2022-09-05 16:07 ` Richard Henderson
2022-09-06 9:53 ` Gerd Hoffmann
2022-09-06 11:59 ` Claudio Fontana
2022-09-06 12:14 ` Claudio Fontana
2022-09-07 7:46 ` Gerd Hoffmann
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=9bb31e44-e43d-b51a-712a-87e46279a0b5@suse.de \
--to=cfontana@suse.de \
--cc=berrange@redhat.com \
--cc=dinechin@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).