From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
qemu-arm@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [RFC PATCH-for-9.1? 2/2] hw/intc/arm_gic: Only provide query-gic-capabilities when GIC built-in
Date: Wed, 07 Aug 2024 13:10:43 +0200 [thread overview]
Message-ID: <87h6bwwpu4.fsf@pond.sub.org> (raw)
In-Reply-To: <a8eb43d8-3714-447b-ab1b-c96ff05cf14a@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Wed, 7 Aug 2024 11:03:51 +0200")
Philippe Mathieu-Daudé <philmd@linaro.org> writes:
> On 7/8/24 10:18, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé <philmd@linaro.org> writes:
>>
>>> When configuring QEMU with --without-default-devices and
>>> not including machines using a GIC, the GIC model is not
>>> built in but the 'query-gic-capabilities' command still
>>> returns false hopes about GIC:
>>>
>>> {"execute": "query-gic-capabilities"}
>>> {"return": [{"emulated": true, "version": 3, "kernel": false}, {"emulated": true, "version": 2, "kernel": false}]}
>>>
>>> Restrict the command to when the GIC is available. If it
>>> isn't we'll get:
>>>
>>> { "execute": "query-gic-capabilities" }
>>> {"error": {"class": "CommandNotFound", "desc": "The command query-gic-capabilities has not been found"}}
>>>
>>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2484
>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>>> ---
>>> qapi/misc-target.json | 4 ++--
>>> hw/intc/arm_gic_qmp.c | 2 ++
>>> hw/intc/meson.build | 2 +-
>>> 3 files changed, 5 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/qapi/misc-target.json b/qapi/misc-target.json
>>> index 8d70bd24d8..b857e44c2e 100644
>>> --- a/qapi/misc-target.json
>>> +++ b/qapi/misc-target.json
>>> @@ -316,7 +316,7 @@
>>> 'data': { 'version': 'int',
>>> 'emulated': 'bool',
>>> 'kernel': 'bool' },
>>> - 'if': 'TARGET_ARM' }
>>> + 'if': 'CONFIG_ARM_GIC' }
>>>
>>> ##
>>> # @query-gic-capabilities:
>>> @@ -335,7 +335,7 @@
>>> # { "version": 3, "emulated": false, "kernel": true } ] }
>>> ##
>>> { 'command': 'query-gic-capabilities', 'returns': ['GICCapability'],
>>> - 'if': 'TARGET_ARM' }
>>> + 'if': 'CONFIG_ARM_GIC' }
>>>
>>> ##
>>> # @SGXEPCSection:
>>> diff --git a/hw/intc/arm_gic_qmp.c b/hw/intc/arm_gic_qmp.c
>>> index 71056a0c10..1fc79c775b 100644
>>> --- a/hw/intc/arm_gic_qmp.c
>>> +++ b/hw/intc/arm_gic_qmp.c
>>> @@ -6,6 +6,8 @@
>>>
>>> #include "qemu/osdep.h"
>>> #include "qapi/util.h"
>>> +
>>> +#include CONFIG_DEVICES
>>
>> Uh, why do we need this now?
>
> Now qapi-commands-misc-target.h is generated guarded with
> '#ifdef CONFIG_ARM_GIC', and CONFIG_ARM_GIC is defined per
> target in CONFIG_DEVICES.
>
> I'll update the patch description, but does this makes
> sense to you? QAPI headers don't include headers defining
> guards, we have to include them manually where we use QAPI
> headers.
Hmm. Then the generated headers aren't self-contained anymore.
Having to manually include a configuration header like CONFIG_DEVICES
wherever you use configuration symbols strikes me as unadvisable when
uses include checking for definedness, such as #ifdef: silent miscompile
when you forget to include.
This is why Autoconf wants you to include config.h first in any .c: it
makes #ifdef & friends safe.
qemu/osdep.h does include some configuration headers:
#include "config-host.h"
#ifdef COMPILING_PER_TARGET
#include CONFIG_TARGET
#else
#include "exec/poison.h"
#endif
Why not CONFIG_DEVICES?
[...]
next prev parent reply other threads:[~2024-08-07 11:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 14:19 [RFC PATCH-for-9.1? 0/2] hw/intc/arm_gic: Only provide query-gic-capabilities when GIC built-in Philippe Mathieu-Daudé
2024-08-06 14:19 ` [RFC PATCH-for-9.1? 1/2] target/arm: Move qmp_query_gic_capabilities() to hw/intc/ Philippe Mathieu-Daudé
2024-08-07 3:46 ` Richard Henderson
2024-08-07 7:31 ` Philippe Mathieu-Daudé
2024-08-07 16:17 ` Peter Maydell
2024-08-08 4:32 ` Markus Armbruster
2024-08-08 8:44 ` Peter Maydell
2024-08-08 9:02 ` Markus Armbruster
2024-08-08 10:15 ` Peter Maydell
2024-08-08 11:05 ` Markus Armbruster
2024-08-08 11:23 ` Daniel P. Berrangé
2024-08-08 11:32 ` Peter Maydell
2024-08-08 11:48 ` Daniel P. Berrangé
2024-08-08 11:56 ` Daniel P. Berrangé
2024-08-08 12:04 ` Peter Maydell
2024-08-07 5:12 ` Markus Armbruster
2024-08-07 7:28 ` Philippe Mathieu-Daudé
2024-08-07 8:16 ` Markus Armbruster
2024-08-06 14:19 ` [RFC PATCH-for-9.1? 2/2] hw/intc/arm_gic: Only provide query-gic-capabilities when GIC built-in Philippe Mathieu-Daudé
2024-08-07 3:47 ` Richard Henderson
2024-08-07 8:18 ` Markus Armbruster
2024-08-07 9:03 ` Philippe Mathieu-Daudé
2024-08-07 11:10 ` Markus Armbruster [this message]
2024-08-07 16:30 ` Peter Maydell
2024-08-08 5:35 ` Markus Armbruster
2024-08-08 8:48 ` Peter Maydell
2025-03-11 11:39 ` [RFC PATCH-for-9.1? 0/2] " 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=87h6bwwpu4.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).