1. 04 6月, 2015 2 次提交
  2. 02 4月, 2015 2 次提交
    • M
      hw: Mark devices picking up char backends actively FIXME · d71b22bb
      Markus Armbruster 提交于
      Character devices defined with -serial and -parallel are for board
      initialization to wire up.  Board code examines serial_hds[] and
      parallel_hds[] to find them, and creates devices with their qdev
      chardev properties set accordingly.
      
      Except a few devices go on a fishing expedition for a suitable backend
      instead of exposing a chardev property for board code to set: they use
      serial_hds[] (often via qemu_char_get_next_serial()) or parallel_hds[]
      in their realize() or init() method to connect to a backend.
      
      Picking up backends that way works when the devices are created by
      board code.  But it's inappropriate for -device or device_add.  Not
      only is it inconsistent with how the other characrer device models
      work (they connect to a backend explicitly identified by a "chardev"
      property), it breaks when the backend has been picked up by the board
      or a previous -device / device_add already.
      
      Example:
      
          $ qemu-system-ppc64 -M bamboo -S -device i82378 -device pc87312 -device pc87312
          qemu-system-ppc64: -device pc87312: Property 'isa-parallel.chardev' can't take value 'parallel0', it's in use
      
      Mark them with suitable FIXME comments.
      
      Cc: Li Guang <lig.fnst@cn.fujitsu.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>
      Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
      Cc: "Andreas Färber" <andreas.faerber@web.de>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      d71b22bb
    • M
      hw: Mark devices picking up block backends actively FIXME · af9e40aa
      Markus Armbruster 提交于
      Drives defined with if!=none are for board initialization to wire up.
      Board code calls drive_get() or similar to find them, and creates
      devices with their qdev drive properties set accordingly.
      
      Except a few devices go on a fishing expedition for a suitable backend
      instead of exposing a drive property for board code to set: they call
      driver_get() or drive_get_next() in their realize() or init() method
      to implicitly connect to the "next" backend with a certain interface
      type.
      
      Picking up backends that way works when the devices are created by
      board code.  But it's inappropriate for -device or device_add.  Not
      only is this inconsistent with how the other block device models work
      (they connect to a backend explicitly identified by a "drive"
      property), it breaks when the "next" backend has been picked up by the
      board already.
      
      Example:
      
          $ qemu-system-arm -S -M connex -pflash flash.img -device ssi-sd
          Aborted (core dumped)
      
      Mark them with suitable FIXME comments.
      
      Cc: Andrzej Zaborowski <balrogg@gmail.com>
      Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
      Cc: "Andreas Färber" <andreas.faerber@web.de>
      Cc: Michael Walle <michael@walle.cc>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      af9e40aa
  3. 26 2月, 2015 3 次提交
  4. 13 2月, 2015 3 次提交
  5. 26 1月, 2015 1 次提交
  6. 15 1月, 2015 1 次提交
  7. 10 12月, 2014 1 次提交
  8. 20 10月, 2014 2 次提交
  9. 15 10月, 2014 1 次提交
  10. 03 9月, 2014 1 次提交
    • G
      Fix debug print warning · c5539cb4
      Gonglei 提交于
      Steps:
      
      1.enable qemu debug print, using simply scprit as below:
       grep "//#define DEBUG" * -rl | xargs sed -i "s/\/\/#define DEBUG/#define DEBUG/g"
      2. make -j
      3. get some warning:
      hw/i2c/pm_smbus.c: In function 'smb_ioport_writeb':
      hw/i2c/pm_smbus.c:142: warning: format '%04x' expects type 'unsigned int', but argument 2 has type 'hwaddr'
      hw/i2c/pm_smbus.c:142: warning: format '%02x' expects type 'unsigned int', but argument 3 has type 'uint64_t'
      hw/i2c/pm_smbus.c: In function 'smb_ioport_readb':
      hw/i2c/pm_smbus.c:209: warning: format '%04x' expects type 'unsigned int', but argument 2 has type 'hwaddr'
      hw/intc/i8259.c: In function 'pic_ioport_read':
      hw/intc/i8259.c:373: warning: format '%02x' expects type 'unsigned int', but argument 2 has type 'hwaddr'
      hw/input/pckbd.c: In function 'kbd_write_command':
      hw/input/pckbd.c:232: warning: format '%02x' expects type 'unsigned int', but argument 2 has type 'uint64_t'
      hw/input/pckbd.c: In function 'kbd_write_data':
      hw/input/pckbd.c:333: warning: format '%02x' expects type 'unsigned int', but argument 2 has type 'uint64_t'
      hw/isa/apm.c: In function 'apm_ioport_writeb':
      hw/isa/apm.c:44: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'hwaddr'
      hw/isa/apm.c:44: warning: format '%02x' expects type 'unsigned int', but argument 3 has type 'uint64_t'
      hw/isa/apm.c: In function 'apm_ioport_readb':
      hw/isa/apm.c:67: warning: format '%x' expects type 'unsigned int', but argument 2 has type 'hwaddr'
      hw/timer/mc146818rtc.c: In function 'cmos_ioport_write':
      hw/timer/mc146818rtc.c:394: warning: format '%02x' expects type 'unsigned int', but argument 3 has type 'uint64_t'
      hw/i386/pc.c: In function 'port92_write':
      hw/i386/pc.c:479: warning: format '%02x' expects type 'unsigned int', but argument 2 has type 'uint64_t'
      
      Fix them.
      
      Cc: qemu-trivial@nongnu.org
      Signed-off-by: NGonglei <arei.gonglei@huawei.com>
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      c5539cb4
  11. 15 8月, 2014 2 次提交
  12. 19 6月, 2014 4 次提交
  13. 16 6月, 2014 1 次提交
  14. 10 6月, 2014 1 次提交
  15. 06 5月, 2014 1 次提交
    • K
      PortioList: Store PortioList in device state · 848696bf
      Kirill Batuzov 提交于
      PortioList is an abstraction used for construction of MemoryRegionPortioList
      from MemoryRegionPortio. It can be used later to unmap created memory regions.
      It also requires proper cleanup because some of the memory inside is allocated
      dynamically.
      
      By moving PortioList ot device state we make it possible to cleanup later and
      avoid leaking memory.
      
      This change spans several target platforms.  The following testcases cover all
      changed lines:
        qemu-system-ppc -M prep
        qemu-system-i386 -vga qxl
        qemu-system-i386 -M isapc -soundhw adlib -device ib700,id=watchdog0,bus=isa.0
      Signed-off-by: NKirill Batuzov <batuzovk@ispras.ru>
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAndreas Färber <afaerber@suse.de>
      848696bf
  16. 15 2月, 2014 1 次提交
  17. 14 2月, 2014 1 次提交
  18. 10 2月, 2014 1 次提交
  19. 23 12月, 2013 5 次提交
  20. 14 10月, 2013 2 次提交
  21. 01 8月, 2013 2 次提交
  22. 29 7月, 2013 1 次提交
  23. 25 7月, 2013 1 次提交