qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] d6edb1: qom: Add can_be_deleted callback to U


From: GitHub
Subject: [Qemu-commits] [qemu/qemu] d6edb1: qom: Add can_be_deleted callback to UserCreatableC...
Date: Wed, 01 Apr 2015 05:30:08 -0700

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: d6edb15576643ab348a9f73e115c2e037edf7460
      
https://github.com/qemu/qemu/commit/d6edb15576643ab348a9f73e115c2e037edf7460
  Author: Lin Ma <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M include/qom/object_interfaces.h
    M qmp.c
    M qom/object_interfaces.c

  Log Message:
  -----------
  qom: Add can_be_deleted callback to UserCreatableClass

If backends implement the can_be_deleted and it returns false,
Then the qmp_object_del won't delete the given backends.

Signed-off-by: Lin Ma <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Igor Mammedov <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 36bce5ca5da7a7dbdc5001dc65b40b7439472106
      
https://github.com/qemu/qemu/commit/36bce5ca5da7a7dbdc5001dc65b40b7439472106
  Author: Lin Ma <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M backends/hostmem.c

  Log Message:
  -----------
  hostmem: Prevent removing an in-use memory backend

showing a memory device whose memdev is removed leads an assert:

(qemu) object_add memory-backend-ram,id=ram0,size=128M
(qemu) device_add pc-dimm,id=d0,memdev=ram0
(qemu) object_del ram0
(qemu) info memory-devices
**
ERROR:qom/object.c:1274:object_get_canonical_path_component:\
                      assertion failed: (obj->parent != NULL)
Aborted

The patch prevents removing an in-use mem backend and error out.

Signed-off-by: Lin Ma <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Igor Mammedov <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: e65bef6954415b24ee17184b959333d9456bece8
      
https://github.com/qemu/qemu/commit/e65bef6954415b24ee17184b959333d9456bece8
  Author: Igor Mammedov <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M hw/i386/acpi-build.c

  Log Message:
  -----------
  pc: acpi: fix pvpanic regression

Commit cd61cb2  pc: acpi-build: generate pvpanic device description dynamically

introduced regression changing pvpanic device HID from
QEMU0001 to QEMU0002.
Fix AML generated code so that pvpanic device
would keep its original HID. i.e. QEMU0001

Signed-off-by: Igor Mammedov <address@hidden>
Reported-by: Gal Hammer <address@hidden>
Message-Id: <address@hidden>
Acked-by: Michael S. Tsirkin <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: a59629fcc6f603e19b516dc08f75334e5c480bd0
      
https://github.com/qemu/qemu/commit/a59629fcc6f603e19b516dc08f75334e5c480bd0
  Author: Paolo Bonzini <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M include/qemu/rcu.h
    M linux-user/syscall.c
    M os-posix.c
    M util/rcu.c

  Log Message:
  -----------
  rcu: do not create thread in pthread_atfork callback

If QEMU forks after the CPU threads have been created, qemu_mutex_lock_iothread
will not be able to do qemu_cpu_kick_thread.  There is no solution other than
assuming that forks after the CPU threads have been created will end up in an
exec.  Forks before the CPU threads have been created (such as -daemonize)
have to call rcu_after_fork manually.

Notably, the oxygen theme for GTK+ forks and shows a "No such process" error
without this patch.

This patch can be reverted once the iothread loses the "kick the TCG thread"
magic.

User-mode emulation does not use the iothread, so it can also call
rcu_after_fork.

Reported by: Dr. David Alan Gilbert <address@hidden>
Tested by: Dr. David Alan Gilbert <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: 4025446f0ac6213335c22ec43f3c3d8362ce7286
      
https://github.com/qemu/qemu/commit/4025446f0ac6213335c22ec43f3c3d8362ce7286
  Author: Paolo Bonzini <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M exec.c

  Log Message:
  -----------
  Revert "exec: Respect as_tranlsate_internal length clamp"

This reverts commit c3c1bb99d1c11978d9ce94d1bdcf0705378c1459.
It causes problems with boards that declare memory regions shorter
than the registers they contain.

Reported-by: Zoltan Balaton <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>


  Commit: b8a86c4ac4d04c106ba38fbd707041cba334a155
      
https://github.com/qemu/qemu/commit/b8a86c4ac4d04c106ba38fbd707041cba334a155
  Author: Peter Maydell <address@hidden>
  Date:   2015-04-01 (Wed, 01 Apr 2015)

  Changed paths:
    M backends/hostmem.c
    M exec.c
    M hw/i386/acpi-build.c
    M include/qemu/rcu.h
    M include/qom/object_interfaces.h
    M linux-user/syscall.c
    M os-posix.c
    M qmp.c
    M qom/object_interfaces.c
    M util/rcu.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging

Fix for object_del of in-use memory, pvpanic
regression, PPC regression and bogus error message with
Oxygen theme.

# gpg: Signature made Wed Apr  1 09:08:20 2015 BST using RSA key ID 78C7AE83
# gpg: Good signature from "Paolo Bonzini <address@hidden>"
# gpg:                 aka "Paolo Bonzini <address@hidden>"
# gpg: WARNING: This key is not certified with sufficiently trusted signatures!
# gpg:          It is not certain that the signature belongs to the owner.
# Primary key fingerprint: 46F5 9FBD 57D6 12E7 BFD4  E2F7 7E15 100C CD36 69B1
#      Subkey fingerprint: F133 3857 4B66 2389 866C  7682 BFFB D25F 78C7 AE83

* remotes/bonzini/tags/for-upstream:
  Revert "exec: Respect as_tranlsate_internal length clamp"
  rcu: do not create thread in pthread_atfork callback
  pc: acpi: fix pvpanic regression
  hostmem: Prevent removing an in-use memory backend
  qom: Add can_be_deleted callback to UserCreatableClass

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/033a20359aaf...b8a86c4ac4d0

reply via email to

[Prev in Thread] Current Thread [Next in Thread]