1. 30 10月, 2012 6 次提交
  2. 24 10月, 2012 3 次提交
  3. 06 10月, 2012 1 次提交
  4. 29 9月, 2012 1 次提交
  5. 28 9月, 2012 1 次提交
  6. 17 8月, 2012 1 次提交
    • E
      Adding support for libseccomp in configure and Makefile (v8) · f794573e
      Eduardo Otubo 提交于
      Adding basic options to the configure script to use libseccomp or not.
      The default is set to 'no'. If the flag --enable-libseccomp is used, the
      script will check for its existence using pkg-config.
      Signed-off-by: NEduardo Otubo <otubo@linux.vnet.ibm.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      ---
      v1 -> v2:
       - As I removed all the code related to seccomp from vl.c, I created
         qemu-seccomp.[ch].
       - Also making the configure script to add the specific line to
         Makefile.obj in order to compile with appropriate support to seccomp.
      
      v2 -> v3:
       - Removing the line from Makefile.obj and adding it to Makefile.objs.
       - Marking libseccomp default option to 'yes' in the configure script.
      
      v3 -> v8:
       - fix configure probe if libseccomp isn't available (aliguori)
      f794573e
  7. 14 8月, 2012 1 次提交
  8. 08 8月, 2012 1 次提交
  9. 22 6月, 2012 1 次提交
  10. 12 6月, 2012 1 次提交
    • M
      consolidate qemu_iovec_memset{,_skip}() into single function and use existing iov_memset() · 3d9b4925
      Michael Tokarev 提交于
      This patch combines two functions into one, and replaces
      the implementation with already existing iov_memset() from
      iov.c.
      
      The new prototype of qemu_iovec_memset():
        size_t qemu_iovec_memset(qiov, size_t offset, int fillc, size_t bytes)
      It is different from former qemu_iovec_memset_skip(), and
      I want to make other functions to be consistent with it
      too: first how much to skip, second what, and 3rd how many
      of it.  It also returns actual number of bytes filled in,
      which may be less than the requested `bytes' if qiov is
      smaller than offset+bytes, in the same way iov_memset()
      does.
      
      While at it, use utility function iov_memset() from
      iov.h in posix-aio-compat.c, where qiov was used.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      3d9b4925
  11. 11 6月, 2012 1 次提交
  12. 07 6月, 2012 15 次提交
  13. 25 4月, 2012 1 次提交
  14. 18 4月, 2012 1 次提交
    • L
      tracetool: Rewrite infrastructure as python modules · 650ab98d
      Lluís Vilanova 提交于
      The tracetool script is written in shell and has hit several portability
      problems due to shell quirks or external tools across host platforms.
      Additionally the amount of string processing and lack of real data
      structures makes it tough to implement code generator backends for
      tracers that are more complex.
      
      This patch replaces the shell version of tracetool with a Python
      version.  The new tracetool design is:
      
        scripts/tracetool.py - top-level script
        scripts/tracetool/backend/ - tracer backends live here (simple, ust)
        scripts/tracetool/format/  - output formats live here (.c, .h)
      
      There is common code for trace-events definition parsing so that
      backends can focus on generating code rather than parsing input.
      
      Support for all existing backends (nop, stderr, simple, ust,
      and dtrace) is added back in follow-up patches.
      
      [Commit description written by Stefan Hajnoczi]
      Signed-off-by: NLluís Vilanova <vilanova@ac.upc.edu>
      Signed-off-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      650ab98d
  15. 02 4月, 2012 1 次提交
  16. 30 3月, 2012 1 次提交
    • A
      qtest: add test framework · c7f0f3b1
      Anthony Liguori 提交于
      The idea behind qtest is pretty simple.  Instead of executing a CPU via TCG or
      KVM, rely on an external process to send events to the device model that the CPU
      would normally generate.
      
      qtest presents itself as an accelerator.  In addition, a new option is added to
      establish a qtest server (-qtest) that takes a character device.  This is what
      allows the external process to send CPU events to the device model.
      
      qtest uses a simple line based protocol to send the events.  Documentation of
      that protocol is in qtest.c.
      
      I considered reusing the monitor for this job.  Adding interrupts would be a bit
      difficult.  In addition, logging would also be difficult.
      
      qtest has extensive logging support.  All protocol commands are logged with
      time stamps using a new command line option (-qtest-log).  Logging is important
      since ultimately, this is a feature for debugging.
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      c7f0f3b1
  17. 16 3月, 2012 3 次提交
    • M
      pci: add standard bridge device · 4eb812f7
      Michael S. Tsirkin 提交于
      This adds support for a standard pci to pci bridge,
      enabling support for more than 32 PCI devices in the system.
      Device hotplug is supported by means of SHPC controller.
      For guests with an SHPC driver, this allows robust hotplug
      and even hotplug of nested bridges, up to 31 devices
      per bridge.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      4eb812f7
    • M
      slotid: add slot id capability · 762833b3
      Michael S. Tsirkin 提交于
      This capability makes it possible for the guest to
      report a unique chassis identifier to the user.
      
      The spec also recommends making chassis indentifier
      persist in eeprom.
      This isn't implemented.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      762833b3
    • M
      shpc: standard hot plug controller · 1dc324d2
      Michael S. Tsirkin 提交于
      This adds support for SHPC interface, as defined by PCI Standard
      Hot-Plug Controller and Subsystem Specification, Rev 1.0
      http://www.pcisig.com/specifications/conventional/pci_hot_plug/SHPC_10
      
      Only SHPC intergrated with a PCI-to-PCI bridge is supported,
      SHPC integrated with a host bridge would need more work.
      
      All main SHPC features are supported:
      - MRL sensor
      - Attention button
      - Attention indicator
      - Power indicator
      
      Wake on hotplug and serr generation are stubbed out but unused
      as we don't have interfaces to generate these events ATM.
      
      One issue that isn't completely resolved is that qemu currently
      expects an "eject" interface, which SHPC does not provide: it merely
      removes the power to device and it's up to the user to remove the device
      from slot. This patch works around that by ejecting the device
      when power is removed and power LED goes off.
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      1dc324d2