From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: Artificially target-dependend compiles
Date: Mon, 8 Nov 2021 17:30:38 +0100 [thread overview]
Message-ID: <092f8664-3f19-877a-0aa2-24fac5e0ba51@redhat.com> (raw)
In-Reply-To: <b476ec65-46fd-7d8c-770d-0351c245df09@redhat.com>
On 08/11/2021 17.23, Paolo Bonzini wrote:
> On 11/8/21 16:38, Thomas Huth wrote:
>>
>> Hmm, we used to have a config-all-devices.mak file in the past (see commit
>> a98006bc798169e which removed it), maybe we could re-introduce something
>> similar again, but producing a config-all.h header file instead? So that
>> this header file contains switches like CONFIG_ANY_ACPI_VMGENID and
>> CONFIG_ANY_ROCKER that are set if any of the targets uses the device ...
>> and these switches would not get poisoned in common code... ?
>
> That would work, however the schema would still not provide any more
> information than it currently does.
Yeah, it's of limited use - you would only get a difference if none of the
targets provided a feature (say if you did not build the x86 and arm
targets, CONFIG_ANY_ACPI_VMGENID would likely not be set) ... not too
useful, I guess.
Thomas
prev parent reply other threads:[~2021-11-08 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 13:45 Artificially target-dependend compiles Markus Armbruster
2021-11-05 16:15 ` Paolo Bonzini
2021-11-06 7:40 ` Markus Armbruster
2021-11-08 8:09 ` Markus Armbruster
2021-11-08 10:27 ` Paolo Bonzini
2021-11-08 15:38 ` Thomas Huth
2021-11-08 16:23 ` Paolo Bonzini
2021-11-08 16:30 ` Thomas Huth [this message]
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=092f8664-3f19-877a-0aa2-24fac5e0ba51@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=pbonzini@redhat.com \
--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).