From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] Poison some more target-specific defines
Date: Wed, 14 Jun 2017 21:21:49 +0200 [thread overview]
Message-ID: <1497468113-2874-1-git-send-email-thuth@redhat.com> (raw)
This series marks some more #defines as poisoned, which are
target-specific (declared in config-target.h) and thus must
not be used in common code.
Note that these are just the easy cases - we should later also add
CONFIG_SOFTMMU and CONFIG_USER_ONLY, but they require some other
additional clean-up first.
Thomas Huth (4):
include/exec/poison: Add missing TARGET defines
include/exec/poison: Mark some CONFIG defines as poisoned, too
include/hw/i386/pc.h: Move CONFIG_KVM related definitions to
kvm_i386.h
include/exec/poison: Mark CONFIG_KVM as poisoned, too
hw/acpi/ich9.c | 1 -
hw/i386/pc_q35.c | 1 +
include/exec/poison.h | 32 ++++++++++++++++++++++++++++++++
include/hw/i386/pc.h | 13 -------------
include/sysemu/kvm.h | 37 +++++++++++++++++++++++++++++++++++--
target/i386/kvm_i386.h | 13 +++++++++++++
6 files changed, 81 insertions(+), 16 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-06-14 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:21 Thomas Huth [this message]
2017-06-14 19:21 ` [Qemu-devel] [PATCH 1/4] include/exec/poison: Add missing TARGET defines Thomas Huth
2017-06-19 21:49 ` Richard Henderson
2017-06-20 5:18 ` Thomas Huth
2017-06-14 19:21 ` [Qemu-devel] [PATCH 2/4] include/exec/poison: Mark some CONFIG defines as poisoned, too Thomas Huth
2017-06-19 21:50 ` Richard Henderson
2017-06-14 19:21 ` [Qemu-devel] [PATCH 3/4] include/hw/i386/pc.h: Move CONFIG_KVM related definitions to kvm_i386.h Thomas Huth
2017-06-15 8:04 ` Paolo Bonzini
2017-06-14 19:21 ` [Qemu-devel] [PATCH 4/4] include/exec/poison: Mark CONFIG_KVM as poisoned, too Thomas Huth
2017-06-14 20:59 ` Paolo Bonzini
2017-06-15 8:32 ` Thomas Huth
2017-06-14 20:01 ` [Qemu-devel] [PATCH 0/4] Poison some more target-specific defines no-reply
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=1497468113-2874-1-git-send-email-thuth@redhat.com \
--to=thuth@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).