1. 30 6月, 2009 1 次提交
  2. 24 6月, 2009 3 次提交
  3. 22 6月, 2009 4 次提交
  4. 17 6月, 2009 1 次提交
  5. 11 6月, 2009 1 次提交
  6. 10 6月, 2009 1 次提交
  7. 23 5月, 2009 1 次提交
    • P
      Add common BusState · 02e2da45
      Paul Brook 提交于
      Implement and use a common device bus state.  The main side-effect is
      that creating a bus and attaching it to a parent device are no longer
      separate operations.  For legacy code we allow a NULL parent, but that
      should go away eventually.
      
      Also tweak creation code to veriry theat a device in on the right bus.
      Signed-off-by: NPaul Brook <paul@codesourcery.com>
      02e2da45
  8. 19 5月, 2009 1 次提交
  9. 15 5月, 2009 3 次提交
  10. 04 5月, 2009 2 次提交
  11. 11 4月, 2009 1 次提交
  12. 06 3月, 2009 1 次提交
    • A
      monitor: Rework API (Jan Kiszka) · 376253ec
      aliguori 提交于
      Refactor the monitor API and prepare it for decoupled terminals:
      term_print functions are renamed to monitor_* and all monitor services
      gain a new parameter (mon) that will once refer to the monitor instance
      the output is supposed to appear on. However, the argument remains
      unused for now. All monitor command callbacks are also extended by a mon
      parameter so that command handlers are able to pass an appropriate
      reference to monitor output services.
      
      For the case that monitor outputs so far happen without clearly
      identifiable context, the global variable cur_mon is introduced that
      shall once provide a pointer either to the current active monitor (while
      processing commands) or to the default one. On the mid or long term,
      those use case will be obsoleted so that this variable can be removed
      again.
      
      Due to the broad usage of the monitor interface, this patch mostly deals
      with converting users of the monitor API. A few of them are already
      extended to pass 'mon' from the command handler further down to internal
      functions that invoke monitor_printf.
      
      At this chance, monitor-related prototypes are moved from console.h to
      a new monitor.h. The same is done for the readline API.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6711 c046a42c-6fe2-441c-8c8c-71466251a162
      376253ec
  13. 11 2月, 2009 5 次提交
  14. 06 2月, 2009 1 次提交
  15. 02 2月, 2009 1 次提交
  16. 28 1月, 2009 1 次提交
  17. 14 1月, 2009 1 次提交
  18. 19 12月, 2008 2 次提交
  19. 18 12月, 2008 1 次提交
  20. 12 12月, 2008 1 次提交
    • A
      pci: add default pci subsystem id for all devices (Gerd Hoffman) · d350d97d
      aliguori 提交于
      This sets a default PCI subsystem ID for all emulated PCI devices.  PCI
      specs require this, so do it.
      
      In many cases it is enougth to know the PCI ID to handle a device
      correctly.  Sometimes a device driver must identify the exact piece of
      hardware (via PCI Subsystem ID) though.
      
      What does this patch to qemu devices:
      
      Right now the emulated PCI devices have no PCI subsystem ID, only the
      PCI ID.  The discussed patch sets a default PCI subsystem ID for all
      emulated devices.  Which will make the qemu devices look pretty much
      like in the laptop case: all PCI subsystem IDs will point to qemu by
      default.
      
      If a driver emulates a very specific piece of hardware where it has to
      emulate more than just the PCI chip, it can overwrite the PCI subsystem
      ID without problems.  The es1370 driver does that for example.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5986 c046a42c-6fe2-441c-8c8c-71466251a162
      d350d97d
  21. 10 12月, 2008 1 次提交
    • A
      KVM: Coalesced MMIO support · f65ed4c1
      aliguori 提交于
      MMIO exits are more expensive in KVM or Xen than in QEMU because they 
      involve, at least, privilege transitions.  However, MMIO write 
      operations can be effectively batched if those writes do not have side 
      effects.
      
      Good examples of this include VGA pixel operations when in a planar 
      mode.  As it turns out, we can get a nice boost in other areas too.  
      Laurent mentioned a 9.7% performance boost in iperf with the coalesced 
      MMIO changes for the e1000 when he originally posted this work for KVM.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      
      
      
      git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5961 c046a42c-6fe2-441c-8c8c-71466251a162
      f65ed4c1
  22. 03 10月, 2008 1 次提交
  23. 03 2月, 2008 1 次提交
  24. 10 12月, 2007 1 次提交
  25. 18 11月, 2007 2 次提交
  26. 17 9月, 2007 1 次提交