qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Claudio Fontana <cfontana@suse.de>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC PATCH] configure: Poison (almost) all target-specific #defines
Date: Mon, 15 Mar 2021 16:08:15 +0100	[thread overview]
Message-ID: <208fab42-d276-315b-e7df-a80b4c4004e2@redhat.com> (raw)
In-Reply-To: <db946056-f099-ac99-38c2-60c61f079676@suse.de>

On 15/03/2021 15.07, Claudio Fontana wrote:
> On 3/15/21 2:54 PM, Thomas Huth wrote:
>> We are generating a lot of target-specific defines in the *-config-devices.h
>> and *-config-target.h files. Using them in common code is wrong and leads
>> to very subtle bugs since a "#ifdef CONFIG_SOMETHING" is not working there
>> as expected. To avoid these issues, we are already poisoning some of the
>> macros in include/exec/poison.h - but maintaining this list manually is
>> cumbersome. Thus let's generate the list of poisoned macros automatically
>> instead.
>> Note that CONFIG_TCG (which is also defined in config-host.h) and
>> CONFIG_USER_ONLY are special, so we have to filter these out.
> 
> 
> 
> I have the impression that CONFIG_USER_ONLY should be poisoned too.
> 
> A lot of the
> 
> #ifndef CONFIG_USER_ONLY
> 
> end up currently doing the wrong thing in common modules includes,
> especially due to the inverted nature of the check.

Not sure about that ... do you have an example at hand?

Anyway, one thing is sure, if we want to poison CONFIG_USER_ONLY, this will 
certainly cause a lot of clean up work first, since it is used all over the 
place...

  Thomas



  reply	other threads:[~2021-03-15 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 13:54 [RFC PATCH] configure: Poison (almost) all target-specific #defines Thomas Huth
2021-03-15 14:07 ` Claudio Fontana
2021-03-15 15:08   ` Thomas Huth [this message]
2021-03-15 15:22     ` Claudio Fontana
2021-03-15 14:52 ` Philippe Mathieu-Daudé
2021-03-15 15:24   ` Thomas Huth
2021-03-15 15:37     ` Peter Maydell
2021-03-15 15:52       ` Thomas Huth
2021-03-15 18:24 ` Eric Blake
2021-03-16  5:28   ` Thomas Huth

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=208fab42-d276-315b-e7df-a80b4c4004e2@redhat.com \
    --to=thuth@redhat.com \
    --cc=cfontana@suse.de \
    --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).