From: Thomas Huth <thuth@redhat.com>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH v3 0/8] Poison some more target-specific defines
Date: Tue, 20 Jun 2017 07:51:59 +0200 [thread overview]
Message-ID: <1497937927-19738-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.
v3:
- Mark some more TARGET_xxx and CONFIG_xxx defines as poisoned in
the first two patches (as requested by Richard)
- Added the final patch to move the edu device to common-obj-y
v2:
- First two patches are the same as in v1
- Reworked the CONFIG_KVM patches according to Paolo's review feedback
- Added two new patches to finally poison CONFIG_SOFTMMU, too
- Added a final patch to move bootdevice.o to common-obj now
(based on an earlier patch where I also tried to move numa.o and
balloon.o, too - but these files are indirectly target-dependent as
I now know, so they can't be moved)
Thomas Huth (8):
include/exec/poison: Add missing TARGET defines
include/exec/poison: Mark some CONFIG defines as poisoned, too
Move CONFIG_KVM related definitions to kvm_i386.h
include/exec/poison: Mark CONFIG_KVM as poisoned, too
cpu: Introduce a wrapper for tlb_flush() that can be used in common
code
include/exec/poison: Mark CONFIG_SOFTMMU as poisoned
Makefile: Move bootdevice.o to common-obj-y
hw/misc/edu: Compile the edu device as common object
Makefile.objs | 2 +-
Makefile.target | 2 +-
bootdevice.c | 2 +-
hw/acpi/ich9.c | 1 -
hw/i386/pc_q35.c | 1 +
hw/misc/Makefile.objs | 2 +-
include/exec/cpu-common.h | 2 ++
include/exec/poison.h | 39 +++++++++++++++++++++++++++++++++++++++
include/hw/i386/pc.h | 13 -------------
include/qom/cpu.h | 8 ++++++++
include/sysemu/kvm.h | 31 ++++++++++++-------------------
qom/cpu.c | 5 ++---
target/i386/kvm_i386.h | 23 +++++++++++++++++++++++
translate-all.c | 8 ++++++++
14 files changed, 99 insertions(+), 40 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-06-20 5:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 5:51 Thomas Huth [this message]
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 1/8] include/exec/poison: Add missing TARGET defines Thomas Huth
2017-06-20 18:05 ` Richard Henderson
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 2/8] include/exec/poison: Mark some CONFIG defines as poisoned, too Thomas Huth
2017-06-20 18:05 ` Richard Henderson
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 3/8] Move CONFIG_KVM related definitions to kvm_i386.h Thomas Huth
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 4/8] include/exec/poison: Mark CONFIG_KVM as poisoned, too Thomas Huth
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 5/8] cpu: Introduce a wrapper for tlb_flush() that can be used in common code Thomas Huth
2017-06-20 18:08 ` Richard Henderson
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 6/8] include/exec/poison: Mark CONFIG_SOFTMMU as poisoned Thomas Huth
2017-06-20 18:10 ` Richard Henderson
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 7/8] Makefile: Move bootdevice.o to common-obj-y Thomas Huth
2017-06-20 5:52 ` [Qemu-devel] [PATCH v3 8/8] hw/misc/edu: Compile the edu device as common object Thomas Huth
2017-06-20 18:14 ` Richard Henderson
2017-06-21 1:40 ` Thomas Huth
2017-06-22 7:59 ` Paolo Bonzini
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=1497937927-19738-1-git-send-email-thuth@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).