Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 01 11月, 2012 6 次提交
  3. 23 9月, 2012 1 次提交
  5. 14 9月, 2012 1 次提交
  7. 06 9月, 2012 2 次提交
  9. 04 9月, 2012 1 次提交
  11. 31 8月, 2012 1 次提交
  13. 14 7月, 2012 1 次提交
  15. 25 2月, 2012 2 次提交
  17. 24 2月, 2012 2 次提交
    • M
      console: Eliminate text_consoles[] · 8811e1e1
      由 Markus Armbruster 提交于 
      Simply use consoles[] instead.
Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      8811e1e1
    • M
      Revert "qemu-char: Print strerror message on failure" and deps · 1f51470d
      由 Markus Armbruster 提交于 
      The commit's purpose is laudable:

    The only way for chardev drivers to communicate an error was to
    return a NULL pointer, which resulted in an error message that
    said _that_ something went wrong, but not _why_.

It attempts to achieve it by changing the interface to return 0/-errno
and update qemu_chr_open_opts() to use strerror() to display a more
helpful error message.  Unfortunately, it has serious flaws:

1. Backends "socket" and "udp" return bogus error codes, because
qemu_chr_open_socket() and qemu_chr_open_udp() assume that
unix_listen_opts(), unix_connect_opts(), inet_listen_opts(),
inet_connect_opts() and inet_dgram_opts() fail with errno set
appropriately.  That assumption is wrong, and the commit turns
unspecific error messages into misleading error messages.  For
instance:

    $ qemu-system-x86_64 -nodefaults -vnc :0 -chardev socket,id=bar,host=xxx
    inet_connect: host and/or port not specified
    chardev: opening backend "socket" failed: No such file or directory

ENOENT is what happens to be in my errno when the backend returns
-errno.  Let's put ERANGE there just for giggles:

    $ qemu-system-x86_64 -nodefaults -vnc :0 -chardev socket,id=bar,host=xxx -drive if=none,iops=99999999999999999999
    inet_connect: host and/or port not specified
    chardev: opening backend "socket" failed: Numerical result out of range

Worse: when errno happens to be zero, return -errno erroneously
signals success, and qemu_chr_new_from_opts() dies dereferencing
uninitialized chr.  I observe this with "-serial unix:".

2. All qemu_chr_open_opts() knows about the error is an errno error
code.  That's simply not enough for a decent message.  For instance,
when inet_dgram() can't resolve the parameter host, which errno code
should it use?  What if it can't resolve parameter localaddr?

Clue: many backends already report errors in their open methods.
Let's revert the flawed commit along with its dependencies, and fix up
the silent error paths instead.

This reverts commit 6e1db57b.

Conflicts:

	console.c
	hw/baum.c
	qemu-char.c

This reverts commit aad04cd0.

The parts of commit db418a0a "Add stdio char device on windows" that
depend on the reverted change fixed up.
Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      1f51470d
  19. 03 1月, 2012 1 次提交
    • A
      console: Fix segfault on screendump without VGA adapter · 33bcd98c
      由 Alexander Graf 提交于 
      When trying to create a screen dump without having any VGA adapter
inside the guest, QEMU segfaults.

This is because it's trying to switch back to the "previous" screen
it was on before dumping the VGA screen. Unfortunately, in my case
there simply is no previous screen so it accesses a NULL pointer.

Fix it by checking if previous_active_console is actually available.

This is 1.0 material.
Signed-off-by: NAlexander Graf <agraf@suse.de>
      33bcd98c
  21. 06 12月, 2011 3 次提交
  23. 08 11月, 2011 1 次提交
  25. 05 10月, 2011 1 次提交
  27. 16 9月, 2011 1 次提交
  29. 10 9月, 2011 1 次提交
  31. 22 8月, 2011 3 次提交
  33. 21 8月, 2011 1 次提交
  35. 24 7月, 2011 1 次提交
  37. 24 6月, 2011 1 次提交
  39. 03 6月, 2011 1 次提交
  41. 22 3月, 2011 1 次提交
  43. 21 3月, 2011 1 次提交
    • P
      change all rt_clock references to use millisecond resolution accessors · 7bd427d8
      由 Paolo Bonzini 提交于 
      This was done with:

    sed -i '/get_clock\>.*rt_clock/s/get_clock\>/get_clock_ms/' \
        $(git grep -l 'get_clock\>.*rt_clock' )
    sed -i '/new_timer\>.*rt_clock/s/new_timer\>/new_timer_ms/' \
        $(git grep -l 'new_timer\>.*rt_clock' )

after checking that get_clock and new_timer never occur twice
on the same line.  There were no missed occurrences; however, even
if there had been, they would have been caught by the compiler.
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      7bd427d8
  45. 02 2月, 2011 3 次提交
  47. 03 10月, 2010 1 次提交
  49. 02 6月, 2010 2 次提交