Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 26 10月, 2018 2 次提交
  3. 24 10月, 2018 1 次提交
  5. 19 10月, 2018 5 次提交
  7. 17 10月, 2018 1 次提交
  9. 12 10月, 2018 2 次提交
  11. 06 10月, 2018 1 次提交
    • E
      tests/fp/fp-test: add floating point tests · 3ac1f813
      由 Emilio G. Cota 提交于 
      By leveraging berkeley's softfloat and testfloat.

With this we get decent coverage of softfloat.c:

$ ./fp-test -r even:	67.22% coverage
$ ./fp-test -r all:	73.11% coverage

Note that we do not yet test parts of softfloat.c that aren't
in the original softfloat library, namely:

- denormal inputs
- *_to_int16/uint16 conversions
- scalbn for fixed point
- muladd variants
- min/max
- exp2
- log2
- float*_compare (except float16_compare)
Signed-off-by: NEmilio G. Cota <cota@braap.org>
[rth: Add the new modules to git_submodules.]
Signed-off-by: NRichard Henderson <richard.henderson@linaro.org>
      3ac1f813
  13. 03 10月, 2018 3 次提交
    • V
      contrib: add elf2dmp tool · 3fa2d384
      由 Viktor Prutyanov 提交于 
      elf2dmp is a converter from ELF dump (produced by 'dump-guest-memory') to
Windows MEMORY.DMP format (also know as 'Complete Memory Dump') which can be
opened in WinDbg.

This tool can help if VMCoreInfo device/driver is absent in Windows VM and
'dump-guest-memory -w' is not available but dump can be created in ELF format.

The tool works as follows:
1. Determine the system paging root looking at GS_BASE or KERNEL_GS_BASE
to locate the PRCB structure and finds the kernel CR3 nearby if QEMU CPU
state CR3 is not suitable.
2. Find an address within the kernel image by dereferencing the first
IDT entry and scans virtual memory upwards until the start of the
kernel.
3. Download a PDB matching the kernel from the Microsoft symbol store,
and figure out the layout of certain relevant structures necessary for
the dump.
4. Populate the corresponding structures in the memory image and create
the appropriate dump header.
Signed-off-by: NViktor Prutyanov <viktor.prutyanov@virtuozzo.com>
Message-Id: <1535546488-30208-3-git-send-email-viktor.prutyanov@virtuozzo.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      3fa2d384
    • E
      configure: enable mttcg for i386 and x86_64 · 0a7fa00a
      由 Emilio G. Cota 提交于 
      Reviewed-by: NRichard Henderson <richard.henderson@linaro.org>
Signed-off-by: NEmilio G. Cota <cota@braap.org>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      0a7fa00a
    • D
      configure: preserve various environment variables in config.status · e811da7f
      由 Daniel P. Berrangé 提交于 
      The config.status script is auto-generated by configure upon
completion. The intention is that config.status can be later invoked by
the developer directly, or by make indirectly, to re-detect the same
environment that configure originally used.

The current config.status script, however, only contains a record of the
command line arguments to configure. Various environment variables have
an effect on what configure will find. In particular PKG_CONFIG_LIBDIR &
PKG_CONFIG_PATH vars will affect what libraries pkg-config finds. The
PATH var will affect what toolchain binaries and XXXX-config scripts are
found. The LD_LIBRARY_PATH var will affect what libraries are
found. Most commands have env variables that will override the name/path
of the default version configure finds.

All these key env variables should be recorded in the config.status script.

Autoconf would also preserve CFLAGS, LDFLAGS, LIBS, CPPFLAGS, but QEMU
deals with those differently, expecting extra flags to be set using
configure args, rather than env variables. At the end of the script we
also don't have the original values of those env vars, as we modify them
during configure.
Reviewed-by: NEric Blake <eblake@redhat.com>
Reviewed-by: NStefan Weil <sw@weilnetz.de>
Signed-off-by: NDaniel P. Berrange <berrange@redhat.com>
Message-Id: <20180904123603.10016-1-berrange@redhat.com>
Reviewed-by: NThomas Huth <thuth@redhat.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
Signed-off-by: NDaniel P. Berrangé <berrange@redhat.com>
      e811da7f
  15. 27 9月, 2018 1 次提交
    • G
      display/edid: add edid generator to qemu. · 72d277a7
      由 Gerd Hoffmann 提交于 
      EDID is a metadata format to describe monitors.  On physical hardware
the monitor has an eeprom with that data block which can be read over
i2c bus.

On a linux system you can usually find the EDID data block in
/sys/class/drm/$card/$connector/edid.  xorg ships a edid-decode utility
which you can use to turn the blob into readable form.

I think it would be a good idea to use EDID for virtual displays too.
Needs changes in both qemu and guest kms drivers.  This patch is the
first step, it adds an generator for EDID blobs to qemu.  Comes with a
qemu-edid test tool included.

With EDID we can pass more information to the guest.  Names and serial
numbers, so the guests display configuration has no boring "Unknown
Monitor".  List of video modes.  Display resolution, pretty important
in case we want add HiDPI support some day.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
Message-id: 20180925075646.25114-2-kraxel@redhat.com
      72d277a7
  17. 28 8月, 2018 1 次提交
  19. 24 8月, 2018 1 次提交
  21. 23 8月, 2018 2 次提交
  23. 18 8月, 2018 1 次提交
  25. 16 8月, 2018 1 次提交
  27. 10 8月, 2018 1 次提交
  29. 05 7月, 2018 1 次提交
  31. 03 7月, 2018 1 次提交
  33. 02 7月, 2018 1 次提交
  35. 29 6月, 2018 4 次提交
  37. 21 6月, 2018 4 次提交
  39. 18 6月, 2018 1 次提交
  41. 16 6月, 2018 1 次提交
  43. 09 6月, 2018 1 次提交
  45. 05 6月, 2018 2 次提交
  47. 01 6月, 2018 1 次提交