Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 04 9月, 2009 4 次提交
    • L
      monitor: Port handler_0 to use QDict · f96fc8a0
      由 Luiz Capitulino 提交于 
      This commit ports command handlers that receive no arguments to use
the new monitor's dictionary.

It might seem no sense to do this, as the handlers have no arguments,
but at the end of this porting work all handlers will have the same
structure.
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      f96fc8a0
    • L
      monitor: Setup a QDict with arguments to handlers · f7188bbe
      由 Luiz Capitulino 提交于 
      With this commit monitor_handle_command() will be able to setup a
QDict with arguments to command handlers.

However, the current 'args[]' method is still being used, next
changes will port commands to get their arguments from the dictionary.

Two changes are worth noting:

1. The '/' argument type always adds the following standard keys in the
dictionary: 'count', 'format' and 'size'. This way, the argument
name used in the 'args_type' string doesn't matter

2. The optional argument type '?' doesn't need to pass the additional
'has_arg' argument, hanlders can do the same check with qdict_haskey()
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      f7188bbe
    • L
      monitor: New format for handlers argument types · 4d76d2ba
      由 Luiz Capitulino 提交于 
      Current handlers argument types, as defined in qemu-monitor.hx file,
are a sequence of chars where each one represents one argument type
of the command handler. The number of chars is also used to know how
many arguments a given handler accepts.

This commit defines a new format, which makes mandatory the use of
a name for each argument.

For example, do_eject() command handler is currently defined as:

{ "eject", "-fB", do_eject, ... }

With the new format it becomes:

{ "eject", "force:-f,filename:B", do_eject, ... }

This way the Monitor will be capable of setting up a dictionary, using
each argument's name as the key and the argument itself as the value.

This commit also adds two new functions: key_get_info() and
next_arg_type(), both are used to parse the new format.

Currently key_get_info() consumes the 'key' part of the new format and
discards it, this way the current parsing code is not affected by this
change.
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      4d76d2ba
    • L
      Add wrappers to functions used by the Monitor · 38183186
      由 Luiz Capitulino 提交于 
      Some functions exported to be used by the Monitor as command
handlers are also called in other places as regular functions.

When those functions got ported to use the Monitor dictionary
to pass argments, the callers will have to setup a dictionary
to be able to call them.

To avoid this problem, this commit add wrappers to those functions,
so that we change the wrapper to accept the dictionary, letting
the current functions as is.

The following wrappers are being added:

- do_help_cmd()
- do_pci_device_hot_remove()
Signed-off-by: NLuiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      38183186
  3. 31 8月, 2009 1 次提交
  5. 28 8月, 2009 4 次提交
  7. 24 8月, 2009 2 次提交
    • A
      Unbreak large mem support by removing kqemu · 4a1418e0
      由 Anthony Liguori 提交于 
      kqemu introduces a number of restrictions on the i386 target.  The worst is that
it prevents large memory from working in the default build.

Furthermore, kqemu is fundamentally flawed in a number of ways.  It relies on
the TSC as a time source which will not be reliable on a multiple processor
system in userspace.  Since most modern processors are multicore, this severely
limits the utility of kqemu.

kvm is a viable alternative for people looking to accelerate qemu and has the
benefit of being supported by the upstream Linux kernel.  If someone can
implement work arounds to remove the restrictions introduced by kqemu, I'm
happy to avoid and/or revert this patch.

N.B. kqemu will still function in the 0.11 series but this patch removes it from
the 0.12 series.

Paul, please Ack or Nack this patch.
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      4a1418e0
    • B
      Fix device name completion for 'eject' · 2a1704a7
      由 Blue Swirl 提交于 
      Signed-off-by: NBlue Swirl <blauwirbel@gmail.com>
      2a1704a7
  9. 11 8月, 2009 2 次提交
  11. 01 8月, 2009 1 次提交
  13. 30 7月, 2009 1 次提交
  15. 28 7月, 2009 1 次提交
    • G
      kill drives_table · 751c6a17
      由 Gerd Hoffmann 提交于 
      First step cleaning up the drives handling.  This one does nothing but
removing drives_table[], still it became seriously big.

drive_get_index() is gone and is replaced by drives_get() which hands
out DriveInfo pointers instead of a table index.  This needs adaption in
*tons* of places all over.

The drives are now maintained as linked list.
Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>
      751c6a17
  17. 27 7月, 2009 2 次提交
  19. 17 7月, 2009 1 次提交
  21. 16 7月, 2009 1 次提交
  23. 10 7月, 2009 2 次提交
  25. 30 6月, 2009 2 次提交
  27. 29 6月, 2009 2 次提交
  29. 11 6月, 2009 4 次提交
  31. 06 6月, 2009 1 次提交
  33. 05 6月, 2009 1 次提交
  35. 28 5月, 2009 1 次提交
  37. 27 5月, 2009 1 次提交
  39. 08 5月, 2009 1 次提交
    • J
      Drop CONFIG_GDBSTUB · 322f9d01
      由 Jan Kiszka 提交于 
      This is no user-flippable switch, and no arch makes use of disabling
gdbstub support. So it's pointless to keep the related #ifdefs and
configure hunks around - and risking breakages like 711c410fdd again.
Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      322f9d01
  41. 01 5月, 2009 1 次提交
  43. 23 4月, 2009 1 次提交
  45. 22 4月, 2009 3 次提交