From: Alexander Graf <agraf@suse.de>
To: qemu-devel Developers <qemu-devel@nongnu.org>
Cc: blauwirbel@gmail.com
Subject: [Qemu-devel] [PATCH 02/16] Compile device-hotplug on all targets
Date: Fri, 11 Nov 2011 18:49:09 +0100 [thread overview]
Message-ID: <1321033763-19881-3-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1321033763-19881-1-git-send-email-agraf@suse.de>
All guest targets could potentially implement hotplugging. With the next
patches in this set I will also reflect this in the monitor interface.
So let's always compile it in. It shouldn't hurt.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
Makefile.target | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/Makefile.target b/Makefile.target
index a111521..21eec0a 100644
--- a/Makefile.target
+++ b/Makefile.target
@@ -228,12 +228,15 @@ ifeq ($(CONFIG_KVM), y)
endif
obj-$(CONFIG_IVSHMEM) += ivshmem.o
+# Generic hotplugging
+obj-y += device-hotplug.o
+
# Hardware support
obj-i386-y += vga.o
obj-i386-y += mc146818rtc.o pc.o
obj-i386-y += cirrus_vga.o sga.o apic.o ioapic.o piix_pci.o
obj-i386-y += vmport.o
-obj-i386-y += device-hotplug.o pci-hotplug.o smbios.o wdt_ib700.o
+obj-i386-y += pci-hotplug.o smbios.o wdt_ib700.o
obj-i386-y += debugcon.o multiboot.o
obj-i386-y += pc_piix.o
obj-i386-$(CONFIG_KVM) += kvmclock.o
--
1.6.0.2
next prev parent reply other threads:[~2011-11-11 17:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 17:49 [Qemu-devel] [PULL 00/16] s390 patch queue 2011-11-11 for 1.0 Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 01/16] [S390] Add hotplug support Alexander Graf
2011-11-11 17:49 ` Alexander Graf [this message]
2011-11-11 17:49 ` [Qemu-devel] [PATCH 03/16] Add generic drive hotplugging Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 04/16] Expose drive_add on all architectures Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 05/16] s390x: add ldeb instruction Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 06/16] s390x: make ipte 31-bit aware Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 07/16] s390x: update R and C bits in storage key Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 08/16] s390x: implement rrbe instruction properly Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 09/16] s390x: implement SIGP restart and shutdown Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 10/16] s390: fix reset hypercall to reset the status Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 11/16] s390: fix short kernel command lines Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 12/16] s390: Fix cpu shutdown for KVM Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 13/16] s390x: Add shutdown for TCG s390-virtio machine Alexander Graf
2011-11-11 17:49 ` [Qemu-devel] [PATCH 14/16] tcg: Standardize on TCGReg as the enum for hard registers Alexander Graf
2011-11-11 23:27 ` Andreas Färber
2011-11-11 17:49 ` [Qemu-devel] [PATCH 15/16] tcg: Use TCGReg for standard tcg-target entry points Alexander Graf
2011-11-11 23:29 ` Andreas Färber
2011-11-11 17:49 ` [Qemu-devel] [PATCH 16/16] s390x: initialize virtio dev region Alexander Graf
2011-11-11 18:08 ` Peter Maydell
2011-11-13 10:09 ` [Qemu-devel] [PULL 00/16] s390 patch queue 2011-11-11 for 1.0 Blue Swirl
2011-11-13 13:51 ` Anthony Liguori
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=1321033763-19881-3-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=blauwirbel@gmail.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).