aboutsummaryrefslogtreecommitdiff
path: root/hw/block/nvme.c
diff options
context:
space:
mode:
authorMarkus Armbruster <armbru@redhat.com>2015-03-23 19:34:40 +0100
committerMarkus Armbruster <armbru@redhat.com>2015-04-02 15:30:44 +0200
commit9f9bdf43cac28251f8cb33b77fed5e19225375c4 (patch)
tree4df7cb9fdf22ebec1bc10a049efff6af25023581 /hw/block/nvme.c
parent19109131ca2701de1b4e083bd51172f376f7a5ef (diff)
downloadqemu-9f9bdf43cac28251f8cb33b77fed5e19225375c4.zip
qemu-9f9bdf43cac28251f8cb33b77fed5e19225375c4.tar.gz
qemu-9f9bdf43cac28251f8cb33b77fed5e19225375c4.tar.bz2
sysbus: Make devices picking up backends unavailable with -device
Device models aren't supposed to go on fishing expeditions for backends. They should expose suitable properties for the user to set. For onboard devices, board code sets them. A number of sysbus devices pick up block backends in their init() / instance_init() methods with drive_get_next() instead: sl-nand, milkymist-memcard, pl181, generic-sdhci. Likewise, a number of sysbus devices pick up character backends in their init() / realize() methods with qemu_char_get_next_serial(): cadence_uart, digic-uart, etraxfs,serial, lm32-juart, lm32-uart, milkymist-uart, pl011, stm32f2xx-usart, xlnx.xps-uartlite. All these mistakes are already marked FIXME. See the commit that added these FIXMEs for a more detailed explanation of what's wrong. Fortunately, only machines ppce500 and pseries-* support -device with sysbus devices, and none of the devices above is supported with these machines. Set cannot_instantiate_with_device_add_yet to preserve our luck. Cc: Andrzej Zaborowski <balrogg@gmail.com> Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com> Cc: Antony Pavlov <antonynpavlov@gmail.com> Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com> Cc: Michael Walle <michael@walle.cc> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Diffstat (limited to 'hw/block/nvme.c')
0 files changed, 0 insertions, 0 deletions