1. 22 11月, 2011 2 次提交
    • M
      configure: check for EFD_NONBLOCK | EFD_CLOEXEC flags · 3439eec3
      Max Filippov 提交于
      Add check for the EFD_NONBLOCK and EFD_CLOEXEC flags to the
      CONFIG_EVENTFD test.
      This fixes the following build failure on Fedora 9:
      
            CC    event_notifier.o
          event_notifier.c: In function `event_notifier_init':
          event_notifier.c:21: error: `EFD_NONBLOCK' undeclared (first use in this function)
          event_notifier.c:21: error: (Each undeclared identifier is reported only once
          event_notifier.c:21: error: for each function it appears in.)
          event_notifier.c:21: error: `EFD_CLOEXEC' undeclared (first use in this function)
          make: *** [event_notifier.o] Error 1
      Reviewed-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: NMax Filippov <jcmvbkbc@gmail.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      3439eec3
    • A
      configure: build position independent executables on x86-Linux hosts · 40d6444e
      Avi Kivity 提交于
      Change the default on x86 Linux hosts to building PIE (position
      independent executables); instead of restricting the option to
      user-only targets, apply it to all targets.
      
      In addition, set the relocation sections to read-only (relro) when
      available; this reduces the attack surface by disallowing changes to
      relocation tables at runtime.
      
      While PIE reduces performance and relro increases load time, it
      greatly improves security, with the potential to reduce a code
      execution vulnerability to a self denial of service.
      
      Non-x86 are not changed, as they require TCG changes; neither are
      non-Linux, due to lack of test coverage.
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      40d6444e
  2. 12 11月, 2011 1 次提交
  3. 10 11月, 2011 2 次提交
  4. 02 11月, 2011 5 次提交
  5. 01 11月, 2011 1 次提交
  6. 31 10月, 2011 3 次提交
  7. 29 10月, 2011 1 次提交
    • R
      iSCSI block driver · c589b249
      Ronnie Sahlberg 提交于
      This provides built-in support for iSCSI to QEMU.
      
      This has the advantage that the iSCSI devices need not be made visible to the host, which is useful if you have very many virtual machines and very many iscsi devices.
      It also has the benefit that non-root users of QEMU can access iSCSI devices across the network without requiring root privilege on the host.
      
      This driver interfaces with the multiplatform posix library for iscsi initiator/client access to iscsi devices hosted at
          git://github.com/sahlberg/libiscsi.git
      
      The patch adds the driver to interface with the iscsi library.
      It also updated the configure script to
      * by default, probe is libiscsi is available and if so, build
        qemu against libiscsi.
      * --enable-libiscsi
        Force a build against libiscsi. If libiscsi is not available
        the build will fail.
      * --disable-libiscsi
        Do not link against libiscsi, even if it is available.
      
      When linked with libiscsi, qemu gains support to access iscsi resources such as disks and cdrom directly, without having to make the devices visible to the host.
      
      You can specify devices using a iscsi url of the form :
      iscsi://[<username>[:<password>@]]<host>[:<port]/<target-iqn-name>/<lun>
      When using authentication, the password can optionally be set with
      LIBISCSI_CHAP_PASSWORD="password" to avoid it showing up in the process list
      Signed-off-by: NRonnie Sahlberg <ronniesahlberg@gmail.com>
      Reviewed-by: NStefan Hajnoczi <stefanha@linux.vnet.ibm.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      c589b249
  8. 15 10月, 2011 2 次提交
  9. 08 10月, 2011 1 次提交
  10. 06 10月, 2011 1 次提交
  11. 01 10月, 2011 1 次提交
  12. 24 9月, 2011 1 次提交
  13. 23 9月, 2011 1 次提交
  14. 21 9月, 2011 2 次提交
  15. 16 9月, 2011 1 次提交
  16. 11 9月, 2011 1 次提交
  17. 09 9月, 2011 2 次提交
  18. 06 9月, 2011 1 次提交
  19. 04 9月, 2011 1 次提交
  20. 02 9月, 2011 3 次提交
  21. 01 9月, 2011 3 次提交
  22. 22 8月, 2011 3 次提交
  23. 21 8月, 2011 1 次提交