From: Peter Maydell <peter.maydell@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Eric Blake" <eblake@redhat.com>,
qemu-arm@nongnu.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, 7 Aug 2024 17:30:50 +0100 [thread overview]
Message-ID: <CAFEAcA_2pJA47K72qJQX9bc8sBcA+0wJGaf3KAaYJaRurjQD7w@mail.gmail.com> (raw)
In-Reply-To: <87h6bwwpu4.fsf@pond.sub.org>
On Wed, 7 Aug 2024 at 12:10, Markus Armbruster <armbru@redhat.com> wrote:
> 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?
The stuff in CONFIG_DEVICES is target-specific, so wanting
to include it should be rare (currently we include it in
only about 25 files). Any file that includes it has to be
a compile-per-target file, and generally we'd rather avoid that.
Plus it's a bit odd to need to change code based on whether
some other device was configured into the system, so I think
that's something worth restricting to only files that effectively
opt in to it.
thanks
-- PMM
next prev parent reply other threads:[~2024-08-07 16:31 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
2024-08-07 16:30 ` Peter Maydell [this message]
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=CAFEAcA_2pJA47K72qJQX9bc8sBcA+0wJGaf3KAaYJaRurjQD7w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--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).