1. 01 7月, 2014 1 次提交
  2. 28 6月, 2014 1 次提交
  3. 25 6月, 2014 1 次提交
  4. 23 6月, 2014 2 次提交
  5. 19 6月, 2014 3 次提交
  6. 18 6月, 2014 1 次提交
  7. 16 6月, 2014 3 次提交
  8. 11 6月, 2014 2 次提交
  9. 10 6月, 2014 2 次提交
  10. 09 6月, 2014 1 次提交
    • L
      trace: Multi-backend tracing · 5b808275
      Lluís Vilanova 提交于
      Adds support to compile QEMU with multiple tracing backends at the same time.
      
      For example, you can compile QEMU with:
      
        $ ./configure --enable-trace-backends=ftrace,dtrace
      
      Where 'ftrace' can be handy for having an in-flight record of events, and 'dtrace' can be later used to extract more information from the system.
      
      This patch allows having both available without recompiling QEMU.
      Signed-off-by: NLluís Vilanova <vilanova@ac.upc.edu>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      5b808275
  11. 24 5月, 2014 3 次提交
    • R
      tcg-mips: Layout executable and code_gen_buffer · 479eb121
      Richard Henderson 提交于
      Choosing good addresses for them means we can use JAL for helper calls.
      Reviewed-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NRichard Henderson <rth@twiddle.net>
      479eb121
    • P
      configure: Put tempfiles in a subdir of the build directory · 8cd05ab6
      Peter Maydell 提交于
      When libtool support was added to configure, the new temporary files
      were left out of the list of files cleaned up on exit; this results
      in a lot of stale .lo files being left around in /tmp. Worse, libtool
      creates a /tmp/.libs directory which we can't easily clean up.
      
      Put all our temporary files in a single temporary directory created
      as a subdirectory of the build directory, so we can easily clean it up,
      and don't need fragile or complicated code for creation to avoid it
      clashing with temporary directories from other instances of QEMU
      configure or being subject to attack from adversaries who can write
      to /tmp.
      
      Since the temporaries now live in the build tree, we have no
      need to jump through hoops with a trap handler to try to remove
      them when configure exits; this fixes some weird bugs where hitting
      ^C during a configure run wouldn't actually make it stop, because
      we would run the trap handler but then not stop. (It is possible
      to get the trap handler semantics right but it is convoluted largely
      because of bugs in dash, so it is simpler to just avoid it.)
      
      Note that "temporary files go in the build directory, not /tmp" is
      the way autoconf behaves.
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      Reviewed-by: NEric Blake <eblake@redhat.com>
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      8cd05ab6
    • S
      configure: Automatically select GTK+ 3.0 if GTK+ 2.0 is unavailable · 9e04c683
      Stefan Weil 提交于
      The configure option --with-gtkabi=3.0 is still supported, but no longer
      needed when GTK+-2.0 is missing. When no GTK+ ABI is selected by the
      user, configure first tries 2.0, then 3.0.
      
      For some platforms (e.g. Windows) newer binaries of GTK+ are only
      available for GTK+ 3.0. Now building on these platforms is a little bit
      easier.
      Signed-off-by: NStefan Weil <sw@weilnetz.de>
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      9e04c683
  12. 16 5月, 2014 1 次提交
  13. 15 5月, 2014 1 次提交
  14. 10 5月, 2014 1 次提交
    • M
      libcacard: remove libcacard-specific CFLAGS and LIBS from global vars · 9d171bd9
      Michael Tokarev 提交于
      Currently all what's needed for single file libcacard/vcard_emul_nss.c
      (libnss cflags) and hw/usb/ccid-card-emulated.c (libcacard includes)
      together with the libs is added to global QEMU_CFLAGS and libs_softmmu.
      
      Use the cflags only where really used (for two mentioned files), and
      libs only where needed.
      
      While at it, rename variables to better reflect reality: libcacard_*
      is really nss_*.
      
      This needs a bit more tweaking: $(NSS_LIBS) should not contain $glib_libs
      (ditto for _cflags).  But in order to fix it, some more preparations
      should be made first.  So add a FIXME comment.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      9d171bd9
  15. 09 5月, 2014 1 次提交
  16. 08 5月, 2014 3 次提交
    • S
      configure: Show trace output file conditionally · e00e36fb
      Stefan Weil 提交于
      It is only used with the simple trace backend.
      Signed-off-by: NStefan Weil <sw@weilnetz.de>
      Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
      e00e36fb
    • M
      configure: remove bashism · 4fc00556
      Michael Tokarev 提交于
      Commit e26110cf added a check for shacmd to create a hash
      for modules.  This check in configure is using bash construct &>
      to redirect both stdout and stderr, which does fun things on some
      shells.  Get rid of it, use standard redirection instead.
      Signed-off-by: NMichael Tokarev <mjt@tls.msk.ru>
      Reviewed-by: NFam Zheng <famz@redhat.com>
      4fc00556
    • M
      configure: make source tree build more robust · cab00a5a
      Michael S. Tsirkin 提交于
      When source directory can be arrived at by two paths,
      configure might misdetect an out of tree build.
      The simplest way to trigger the problem is running
      configure using a full path. E.g. (<firstpath> refers to qemu source
      tree):
          ln -s <firstpath> <secondpath>
          cd <firstpath>
          <secondpath>/configure
      
      A more practical way is when make runs configure automatically:
      
      1. cd <firstpath>/; ./configure
          SRC_PATH=<firstpath>/ is written into config_host.mak
      2. cd <secondpath>/; touch configure; make
          make now runs <firstpath>/configure, so configure
          assumes it's an out of tree build
      
      When this happens configure overwrites parts of
      the current tree with symlinks.
      
      Make the test more robust: look for configure
      in the current directory.
      If there - we know it's a source build!
      Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      cab00a5a
  17. 03 5月, 2014 1 次提交
    • R
      linux-user: remove configure option for setting uname release · e586822a
      Riku Voipio 提交于
      --enable-uname-release was a rather heavyweight hammer, as it allows
      providing values less that UNAME_MINIMUM_RELEASE. Also, it affects
      all built linux-user targets, which in most cases is not what user
      wants.
      
      Now that we have UNAME_MINIMUM_RELEASE for all linux-user platforms,
      we can drop --enable-uname-release and the related CONFIG_UNAME_RELEASE
      define.
      
      Users can still override the variable with QEMU_UNAME=2.6.32 or -r
      command line option. If distributors need to update a minimum version
      for a specific target, it can be done by updating UNAME_MINIMUM_RELEASE.
      Signed-off-by: NRiku Voipio <riku.voipio@linaro.org>
      e586822a
  18. 29 4月, 2014 2 次提交
  19. 27 4月, 2014 1 次提交
  20. 18 4月, 2014 2 次提交
  21. 14 4月, 2014 1 次提交
  22. 11 4月, 2014 1 次提交
  23. 01 4月, 2014 1 次提交
    • S
      configure: add option to disable -fstack-protector flags · 63678e17
      Steven Noonan 提交于
      The -fstack-protector flag family is useful for ensuring safety and for
      debugging, but has a performance impact. Here are some boot time comparisons of
      the various versions of -fstack-protector using qemu-system-arm on an x86_64
      host:
      
          # -fstack-protector-all
          Startup finished in 1.810s (kernel) + 12.331s (initrd) + 49.016s (userspace) = 1min 3.159s
          Startup finished in 1.801s (kernel) + 12.287s (initrd) + 47.925s (userspace) = 1min 2.013s
          Startup finished in 1.812s (kernel) + 12.302s (initrd) + 47.995s (userspace) = 1min 2.111s
      
          # -fstack-protector-strong
          Startup finished in 1.744s (kernel) + 11.223s (initrd) + 44.688s (userspace) = 57.657s
          Startup finished in 1.721s (kernel) + 11.222s (initrd) + 44.194s (userspace) = 57.138s
          Startup finished in 1.693s (kernel) + 11.250s (initrd) + 44.426s (userspace) = 57.370s
      
          # -fstack-protector
          Startup finished in 1.705s (kernel) + 11.409s (initrd) + 43.563s (userspace) = 56.677s
          Startup finished in 1.877s (kernel) + 11.137s (initrd) + 43.719s (userspace) = 56.734s
          Startup finished in 1.708s (kernel) + 11.141s (initrd) + 43.628s (userspace) = 56.478s
      
          # no stack protector
          Startup finished in 1.743s (kernel) + 11.190s (initrd) + 43.709s (userspace) = 56.643s
          Startup finished in 1.763s (kernel) + 11.216s (initrd) + 43.767s (userspace) = 56.747s
          Startup finished in 1.711s (kernel) + 11.283s (initrd) + 43.878s (userspace) = 56.873s
      
      This patch introduces a configure option to disable the stack protector
      entirely, and conditional stack protector flag selection (in order,
      based on availability): -fstack-protector-strong, -fstack-protector-all,
      no stack protector.
      Signed-off-by: NSteven Noonan <snoonan@amazon.com>
      Cc: Anthony Liguori <aliguori@amazon.com>
      Reviewed-by: NStefan Weil <sw@weilnetz.de>
      [Prefer -fstack-protector-all to -fstack-protector, suggested by
       Laurent Desnogues. - Paolo]
      Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      Signed-off-by: NPeter Maydell <peter.maydell@linaro.org>
      63678e17
  24. 27 3月, 2014 1 次提交
  25. 26 3月, 2014 1 次提交
  26. 19 3月, 2014 1 次提交
    • P
      block/nfs: bump libnfs requirement to 1.9.3 · b7d769c9
      Peter Lieven 提交于
      libnfs prior to 1.9.3 contains a bug that will report
      wrong transfer sizes if the file offset grows beyond 4GB
      and RPC responses are received out of order. this
      error is not detectable and fixable in qemu.
      
      additionally 1.9.3 introduces support for handling short
      read/writes in general and takes care of the necessary
      retransmissions internally.
      Signed-off-by: NPeter Lieven <pl@kamp.de>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      b7d769c9
  27. 15 3月, 2014 1 次提交