[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] ea43e2: virtio/migration: Add VMStateDescript
|
From: |
GitHub |
|
Subject: |
[Qemu-commits] [qemu/qemu] ea43e2: virtio/migration: Add VMStateDescription to Virtio... |
|
Date: |
Thu, 03 Nov 2016 14:30:07 -0700 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: ea43e259873a9899227848bd2a24b57356395516
https://github.com/qemu/qemu/commit/ea43e259873a9899227848bd2a24b57356395516
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio.c
M include/hw/virtio/virtio.h
Log Message:
-----------
virtio/migration: Add VMStateDescription to VirtioDeviceClass
Provide a vmsd pointer for VirtIO devices to use instead of the
load/save methods.
We'll eventually kill off the load/save methods.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 019518a80e24af8fcc14689a1fdfde50c5488d2d
https://github.com/qemu/qemu/commit/019518a80e24af8fcc14689a1fdfde50c5488d2d
Author: Dr. David Alan Gilbert <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-balloon.c
Log Message:
-----------
virtio/migration: Migrate balloon to VMState
Replace the load/save with a vmsd.
Signed-off-by: Dr. David Alan Gilbert <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: ca2b413c39b5cb2412bc236ddf3aa22d96594feb
https://github.com/qemu/qemu/commit/ca2b413c39b5cb2412bc236ddf3aa22d96594feb
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/s390x/virtio-ccw.c
M hw/virtio/virtio-pci.c
Log Message:
-----------
virtio: disable ioeventfd as early as possible
Avoid "tricking" virtio-blk-dataplane into thinking that ioeventfd will be
available when it is not. This bug has always been there, but it will break
TCG+ioeventfd=on once the dataplane code will be always used when ioeventfd=on.
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 4ddcc2d5cb8f14d43a4ed31beaad982557a418fd
https://github.com/qemu/qemu/commit/4ddcc2d5cb8f14d43a4ed31beaad982557a418fd
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/s390x/virtio-ccw.c
M hw/s390x/virtio-ccw.h
M hw/virtio/virtio-bus.c
M hw/virtio/virtio-mmio.c
M hw/virtio/virtio-pci.c
M hw/virtio/virtio-pci.h
M include/hw/virtio/virtio-bus.h
Log Message:
-----------
virtio: move ioeventfd_disabled flag to VirtioBusState
This simplifies the code and removes the ioeventfd_set_disabled
callback.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: b13d39622703ae7449f769c14da7a90f20f2c25c
https://github.com/qemu/qemu/commit/b13d39622703ae7449f769c14da7a90f20f2c25c
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/block/dataplane/virtio-blk.c
M hw/s390x/virtio-ccw.c
M hw/s390x/virtio-ccw.h
M hw/scsi/virtio-scsi-dataplane.c
M hw/virtio/vhost.c
M hw/virtio/virtio-bus.c
M hw/virtio/virtio-mmio.c
M hw/virtio/virtio-pci.c
M hw/virtio/virtio-pci.h
M include/hw/virtio/virtio-bus.h
Log Message:
-----------
virtio: move ioeventfd_started flag to VirtioBusState
This simplifies the code and removes the ioeventfd_started
and ioeventfd_set_started callback. The only difference is
in how virtio-ccw handles an error---it doesn't disable
ioeventfd forever anymore. It was the only backend to do
so, and if desired this behavior should be implemented in
virtio-bus.c.
Instead of ioeventfd_started, the ioeventfd_assign callback now
determines whether the virtio bus supports host notifiers.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: ff4c07df67f098234d9e49850435ccb49b8cbbdc
https://github.com/qemu/qemu/commit/ff4c07df67f098234d9e49850435ccb49b8cbbdc
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-bus.c
M hw/virtio/virtio.c
M include/hw/virtio/virtio-bus.h
M include/hw/virtio/virtio.h
Log Message:
-----------
virtio: add start_ioeventfd and stop_ioeventfd to VirtioDeviceClass
Allow customization of the start and stop of ioeventfd. This will
allow direct start of dataplane without passing through the default
ioeventfd handlers, which in turn allows using the dataplane logic
instead of virtio_add_queue_aio. It will also enable some code
simplification, because the sole entry point to ioeventfd setup
will be virtio_bus_set_host_notifier.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 8e93cef14e6f32adf6914b30b096039e6264f0e3
https://github.com/qemu/qemu/commit/8e93cef14e6f32adf6914b30b096039e6264f0e3
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/s390x/virtio-ccw.c
M hw/virtio/virtio-bus.c
M hw/virtio/virtio-mmio.c
M hw/virtio/virtio-pci.c
M hw/virtio/virtio.c
M include/hw/virtio/virtio-bus.h
M include/hw/virtio/virtio.h
Log Message:
-----------
virtio: introduce virtio_device_ioeventfd_enabled
This will be used to forbid iothread configuration when the
proxy does not allow using ioeventfd. To simplify the implementation,
change the direction of the ioeventfd_disabled callback too.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 9ffe337c08388d5c587eae1d77db1b0d1a47c7b1
https://github.com/qemu/qemu/commit/9ffe337c08388d5c587eae1d77db1b0d1a47c7b1
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/block/dataplane/virtio-blk.c
M hw/block/dataplane/virtio-blk.h
M hw/block/virtio-blk.c
Log Message:
-----------
virtio-blk: always use dataplane path if ioeventfd is active
Override start_ioeventfd and stop_ioeventfd to start/stop the
whole dataplane logic. This has some positive side effects:
- no need anymore for virtio_add_queue_aio (i.e. a revert of
commit 0ff841f6d138904d514efa1d885bcaf54583852d)
- no need anymore to switch from generic ioeventfd handlers to
dataplane
It detects some errors better:
$ qemu-system-x86_64 -object iothread,id=io \
-drive id=null,file=null-aio://,if=none,format=raw \
-device virtio-blk-pci,ioeventfd=off,iothread=io,drive=null
qemu-system-x86_64: -device
virtio-blk-pci,ioeventfd=off,iothread=io,drive=null:
ioeventfd is required for iothread
while previously it would have started just fine.
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: ad07cd69ecaffbaa015459a46975ab32e50df805
https://github.com/qemu/qemu/commit/ad07cd69ecaffbaa015459a46975ab32e50df805
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/scsi/virtio-scsi-dataplane.c
M hw/scsi/virtio-scsi.c
M include/hw/virtio/virtio-scsi.h
Log Message:
-----------
virtio-scsi: always use dataplane path if ioeventfd is active
Override start_ioeventfd and stop_ioeventfd to start/stop the
whole dataplane logic. This has some positive side effects:
- no need anymore for virtio_add_queue_aio (i.e. a revert of
commit 1c627137c10ee2dcf59e0383ade8a9abfa2d4355)
- no need anymore to switch from generic ioeventfd handlers to
dataplane
It detects some errors better:
$ qemu-system-x86_64 -object iothread,id=io \
-device virtio-scsi-pci,ioeventfd=off,iothread=io
qemu-system-x86_64: -device virtio-scsi-pci,ioeventfd=off,iothread=io:
ioeventfd is required for iothread
while previously it would have started just fine.
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: f1ac6a552207c791a77e3d33f4f1dd5cd5af7814
https://github.com/qemu/qemu/commit/f1ac6a552207c791a77e3d33f4f1dd5cd5af7814
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio.c
M include/hw/virtio/virtio.h
Log Message:
-----------
Revert "virtio: Introduce virtio_add_queue_aio"
This reverts commit 872dd82c83745a603d2e07a03d34313eb6467ae4.
virtio_add_queue_aio is unused.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 6019f3b966d5764fd655b57887599e5e2d544f73
https://github.com/qemu/qemu/commit/6019f3b966d5764fd655b57887599e5e2d544f73
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-bus.c
M hw/virtio/virtio.c
M include/hw/virtio/virtio-bus.h
Log Message:
-----------
virtio: remove set_handler argument from set_host_notifier_internal
Make virtio_device_start_ioeventfd_impl use the same logic as
dataplane to set up the host notifier. This removes the need
for the set_handler argument in set_host_notifier_internal.
This is a first step towards using virtio_bus_set_host_notifier
as the sole entry point to set up ioeventfds. At least now
the functions have the same interface, but they still differ
in that virtio_bus_set_host_notifier sets ioeventfd_disabled.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: e616c2f390634a241f7899ff4c52bed9803103c6
https://github.com/qemu/qemu/commit/e616c2f390634a241f7899ff4c52bed9803103c6
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/vhost.c
M hw/virtio/virtio-bus.c
M include/hw/virtio/virtio-bus.h
Log Message:
-----------
virtio: remove ioeventfd_disabled altogether
Now that there is not anymore a switch from the generic ioeventfd handler
to the dataplane handler, virtio_bus_set_host_notifier(assign=true) is
always called with !bus->ioeventfd_started, hence virtio_bus_stop_ioeventfd
does nothing in this case. Move the invocation to vhost.c, which is the
only place that needs it.
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: ed08a2a0ba165bfa3d520126eed340c803308321
https://github.com/qemu/qemu/commit/ed08a2a0ba165bfa3d520126eed340c803308321
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-bus.c
M hw/virtio/virtio.c
M include/hw/virtio/virtio-bus.h
Log Message:
-----------
virtio: use virtio_bus_set_host_notifier to start/stop ioeventfd
ioeventfd_disabled was the only reason for the default
implementation of virtio_device_start_ioeventfd not to use
virtio_bus_set_host_notifier. This is now fixed, and the sole entry
point to set up ioeventfd can be virtio_bus_set_host_notifier.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: fa283a4a8be621d9be88c87458355aa4800b731c
https://github.com/qemu/qemu/commit/fa283a4a8be621d9be88c87458355aa4800b731c
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-bus.c
M hw/virtio/virtio.c
M include/hw/virtio/virtio.h
Log Message:
-----------
virtio: inline virtio_queue_set_host_notifier_fd_handler
Of the three possible parameter combinations for
virtio_queue_set_host_notifier_fd_handler:
- assign=true/set_handler=true is only called from
virtio_device_start_ioeventfd
- assign=false/set_handler=false is called from
set_host_notifier_internal but it only does something when
reached from virtio_device_stop_ioeventfd_impl; otherwise
there is no EventNotifier set on qemu_get_aio_context().
- assign=true/set_handler=false is called from
set_host_notifier_internal, but it is not doing anything:
with the new start_ioeventfd and stop_ioeventfd methods,
there is never an EventNotifier set on qemu_get_aio_context()
at this point. This is enforced by the assertion in
virtio_bus_set_host_notifier.
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 2bd3c31a606e38ba12156d8ec11b9226354a2aff
https://github.com/qemu/qemu/commit/2bd3c31a606e38ba12156d8ec11b9226354a2aff
Author: Paolo Bonzini <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M hw/virtio/virtio-bus.c
Log Message:
-----------
virtio: inline set_host_notifier_internal
This is only called from virtio_bus_set_host_notifier.
Reviewed-by: Stefan Hajnoczi <address@hidden>
Reviewed-by: Cornelia Huck <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: d0ee7a135fe499dd900bdca4d70efc2beaa6ef9c
https://github.com/qemu/qemu/commit/d0ee7a135fe499dd900bdca4d70efc2beaa6ef9c
Author: Gonglei <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M backends/Makefile.objs
A backends/cryptodev.c
A include/sysemu/cryptodev.h
Log Message:
-----------
cryptodev: introduce cryptodev backend interface
cryptodev backend interface is used to realize the active work for
virtual crypto device.
This patch only add the framework, doesn't include specific operations.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 9e4f86a84ea2abfd85c46829310d9bdd563648e1
https://github.com/qemu/qemu/commit/9e4f86a84ea2abfd85c46829310d9bdd563648e1
Author: Gonglei <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M backends/cryptodev.c
M include/sysemu/cryptodev.h
Log Message:
-----------
cryptodev: add symmetric algorithm operation stuff
This patch adds session operation and crypto operation
stuff in the cryptodev backend, including function
pointers and corresponding structures.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 5551e3a88e74c49218a8fc2b28293a8db4a95253
https://github.com/qemu/qemu/commit/5551e3a88e74c49218a8fc2b28293a8db4a95253
Author: Gonglei <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
A include/standard-headers/linux/virtio_crypto.h
Log Message:
-----------
virtio-crypto: introduce virtio_crypto.h
Introduce the virtio_crypto.h which follows
virtio-crypto specification.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 1653a5f3fc79bc5f3d43b09d23c225c04d4f14d0
https://github.com/qemu/qemu/commit/1653a5f3fc79bc5f3d43b09d23c225c04d4f14d0
Author: Gonglei <address@hidden>
Date: 2016-10-30 (Sun, 30 Oct 2016)
Changed paths:
M backends/Makefile.objs
A backends/cryptodev-builtin.c
M qemu-options.hx
Log Message:
-----------
cryptodev: introduce a new cryptodev backend
The new cryptodev backend named cryptodev-builtin,
which realized by QEMU cipher APIs. These APIs can
be backed by either nettle or gcrypt.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: e20e718cdea2527ce560a03c5d8cd248decb537a
https://github.com/qemu/qemu/commit/e20e718cdea2527ce560a03c5d8cd248decb537a
Author: Paolo Bonzini <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M scripts/checkpatch.pl
Log Message:
-----------
checkpatch: tweak "struct should normally be const" warning
Avoid triggering on
typedef struct BlockJobDriver BlockJobDriver;
or
struct BlockJobDriver {
Cc: John Snow <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 9bc9732faeff09828fe38c0ebe2401ee131a6fca
https://github.com/qemu/qemu/commit/9bc9732faeff09828fe38c0ebe2401ee131a6fca
Author: Changlong Xie <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M block/nbd-client.c
M block/nbd-client.h
Log Message:
-----------
nbd: Use CoQueue for free_sema instead of CoMutex
NBD is using the CoMutex in a way that wasn't anticipated. For example, if
there are
N(N=26, MAX_NBD_REQUESTS=16) nbd write requests, so we will invoke
nbd_client_co_pwritev
N times.
----------------------------------------------------------------------------------------
time request Actions
1 1 in_flight=1, Coroutine=C1
2 2 in_flight=2, Coroutine=C2
...
15 15 in_flight=15, Coroutine=C15
16 16 in_flight=16, Coroutine=C16, free_sema->holder=C16,
mutex->locked=true
17 17 in_flight=16, Coroutine=C17, queue C17 into free_sema->queue
18 18 in_flight=16, Coroutine=C18, queue C18 into free_sema->queue
...
26 N in_flight=16, Coroutine=C26, queue C26 into free_sema->queue
----------------------------------------------------------------------------------------
Once nbd client recieves request No.16' reply, we will re-enter C16. It's ok,
because
it's equal to 'free_sema->holder'.
----------------------------------------------------------------------------------------
time request Actions
27 16 in_flight=15, Coroutine=C16, free_sema->holder=C16,
mutex->locked=false
----------------------------------------------------------------------------------------
Then nbd_coroutine_end invokes qemu_co_mutex_unlock what will pop coroutines
from
free_sema->queue's head and enter C17. More free_sema->holder is C17 now.
----------------------------------------------------------------------------------------
time request Actions
28 17 in_flight=16, Coroutine=C17, free_sema->holder=C17,
mutex->locked=true
----------------------------------------------------------------------------------------
In above scenario, we only recieves request No.16' reply. As time goes by, nbd
client will
almostly recieves replies from requests 1 to 15 rather than request 17 who owns
C17. In this
case, we will encounter assert "mutex->holder == self" failed since Kevin's
commit 0e438cdc
"coroutine: Let CoMutex remember who holds it". For example, if nbd client
recieves request
No.15' reply, qemu will stop unexpectedly:
----------------------------------------------------------------------------------------
time request Actions
29 15(most case) in_flight=15, Coroutine=C15, free_sema->holder=C17,
mutex->locked=false
----------------------------------------------------------------------------------------
Per Paolo's suggestion "The simplest fix is to change it to CoQueue, which is
like a condition
variable", this patch replaces CoMutex with CoQueue.
Cc: Wen Congyang <address@hidden>
Reported-by: zhanghailiang <address@hidden>
Suggested-by: Paolo Bonzini <address@hidden>
Signed-off-by: Changlong Xie <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 397d30e9401d2da96dbdf0ce49805d6d4bb68833
https://github.com/qemu/qemu/commit/397d30e9401d2da96dbdf0ce49805d6d4bb68833
Author: Paolo Bonzini <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M include/qemu/error-report.h
M monitor.c
M stubs/Makefile.objs
A stubs/error-printf.c
R stubs/mon-printf.c
M util/qemu-error.c
Log Message:
-----------
qemu-error: remove dependency of stubs on monitor
Leave the implementation of error_vprintf and error_vprintf_unless_qmp
(the latter now trivially wrapped by error_printf_unless_qmp) to
libqemustub.a and monitor.c. This has two advantages: it lets us
remove the monitor_printf and monitor_vprintf stubs, and it lets
tests provide a different implementation of the functions that uses
g_test_message.
Signed-off-by: Paolo Bonzini <address@hidden>
Message-Id: <address@hidden>
Commit: 28017e010ddf6849cfa830e898da3e44e6610952
https://github.com/qemu/qemu/commit/28017e010ddf6849cfa830e898da3e44e6610952
Author: Paolo Bonzini <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M include/glib-compat.h
M stubs/error-printf.c
Log Message:
-----------
tests: send error_report to test log
Implement error_vprintf to send the output of error_report to
the test log. This silences test-vmstate.
Signed-off-by: Paolo Bonzini <address@hidden>
Message-Id: <address@hidden>
Commit: f35e44e7645edbb08e35b111c10c2fc57e2905c7
https://github.com/qemu/qemu/commit/f35e44e7645edbb08e35b111c10c2fc57e2905c7
Author: Alex Bennée <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M exec.c
Log Message:
-----------
exec.c: ensure all AddressSpaceDispatch updates under RCU
The memory_dispatch field is meant to be protected by RCU so we should
use the correct primitives when accessing it. This race was flagged up
by the ThreadSanitizer.
Signed-off-by: Alex Bennée <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: d6af99c9f8d577927a52d00af3fa8e6ec0b2a4e2
https://github.com/qemu/qemu/commit/d6af99c9f8d577927a52d00af3fa8e6ec0b2a4e2
Author: Haozhong Zhang <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M exec.c
Log Message:
-----------
exec.c: do not truncate non-empty memory backend file
For '-object memory-backend-file,mem-path=foo,size=xyz', if the size of
file 'foo' does not match the given size 'xyz', the current QEMU will
truncate the file to the given size, which may corrupt the existing data
in that file. To avoid such data corruption, this patch disables
truncating non-empty backend files.
Signed-off-by: Haozhong Zhang <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: ea4d8ac2daea311d186569efab6b9a271a24190f
https://github.com/qemu/qemu/commit/ea4d8ac2daea311d186569efab6b9a271a24190f
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/Makefile.objs
A hw/virtio/virtio-crypto.c
A include/hw/virtio/virtio-crypto.h
M include/standard-headers/linux/virtio_ids.h
Log Message:
-----------
virtio-crypto: add virtio crypto device emulation
Introduce the virtio crypto realization, I'll
finish the core code in the following patches. The
thoughts came from virtio net realization.
For more information see:
http://qemu-project.org/Features/VirtioCrypto
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: b307d308c9a6256610bdaf12a6fea0cfa18df6f6
https://github.com/qemu/qemu/commit/b307d308c9a6256610bdaf12a6fea0cfa18df6f6
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/Makefile.objs
A hw/virtio/virtio-crypto-pci.c
M hw/virtio/virtio-pci.h
Log Message:
-----------
virtio-crypto-pci: add virtio crypto pci support
This patch adds virtio-crypto-pci, which is the pci proxy for the virtio
crypto device.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 050652d9be4c723da2a36f2e9ca5be20e27e93b7
https://github.com/qemu/qemu/commit/050652d9be4c723da2a36f2e9ca5be20e27e93b7
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/virtio-crypto.c
M include/hw/virtio/virtio-crypto.h
Log Message:
-----------
virtio-crypto: set capacity of algorithms supported
Expose the capacity of algorithms supported by
virtio crypto device to the frontend driver using
pci configuration space.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 59c360ca42121e6f6ed83bc740aa5d1a1b59be1d
https://github.com/qemu/qemu/commit/59c360ca42121e6f6ed83bc740aa5d1a1b59be1d
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/virtio-crypto.c
Log Message:
-----------
virtio-crypto: add control queue handler
Realize the symmetric algorithm control queue handler,
including plain cipher and chainning algorithms.
Currently the control queue is used to create and
close session for symmetric algorithm.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 04b9b37edda85964cca033a48dcc0298036782f2
https://github.com/qemu/qemu/commit/04b9b37edda85964cca033a48dcc0298036782f2
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/virtio-crypto.c
M include/hw/virtio/virtio-crypto.h
Log Message:
-----------
virtio-crypto: add data queue processing handler
Introduces VirtIOCryptoReq structure to store
crypto request so that we can easily support
asynchronous crypto operation in the future.
At present, we only support cipher and algorithm
chaining.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: d6634ac09abf20d890fd094773f125ee0ff0b1cb
https://github.com/qemu/qemu/commit/d6634ac09abf20d890fd094773f125ee0ff0b1cb
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M backends/cryptodev.c
M hw/virtio/virtio-crypto.c
M include/sysemu/cryptodev.h
Log Message:
-----------
cryptodev: introduce an unified wrapper for crypto operation
We use an opaque point to the VirtIOCryptoReq which
can support different packets based on different
algorithms.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 20cb2ffd5ff3fdbf47d7a69d1bb649000aca66b6
https://github.com/qemu/qemu/commit/20cb2ffd5ff3fdbf47d7a69d1bb649000aca66b6
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/virtio/virtio-crypto.c
M include/hw/virtio/virtio-crypto.h
Log Message:
-----------
virtio-crypto: using bh to handle dataq's requests
Make crypto operations are executed asynchronously,
so that other QEMU threads and monitor couldn't
be blocked at the virtqueue handling context.
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 6034011c7e00e9408e18d42a7fb807a0f12157fc
https://github.com/qemu/qemu/commit/6034011c7e00e9408e18d42a7fb807a0f12157fc
Author: Gonglei <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M MAINTAINERS
Log Message:
-----------
virtio-crypto: add myself as virtio-crypto and cryptodev backends maintainer
This patch includes two parts: Cryptodev Backends
and virtio-crypto stuff. I can maintain cryptodev backends
which introduced by myself. For virtio-crypto stuff, I can
share the work with Michael (The whole virtio supporter).
Signed-off-by: Gonglei <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: d51d1d7edeb869e0010d6b3833bd53ad561ff805
https://github.com/qemu/qemu/commit/d51d1d7edeb869e0010d6b3833bd53ad561ff805
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: fix wrong buffer size returned by DSM method
Currently, 'RLEN' is the totally buffer size written by QEMU and it is
ACPI internally used only. The buffer size returned to guest should
not include 'RLEN' itself
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: c0b3b863acb0087120322497ac2fdbcf149a2e62
https://github.com/qemu/qemu/commit/c0b3b863acb0087120322497ac2fdbcf149a2e62
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: fix OperationRegion definition
Based on ACPI spec:
RegionOffset := TermArg => Integer
However, Named object is not a TermArg.
This patch moves OperationRegion to NCAL() and uses localX as
its RegionOffset
Suggested-by: Igor Mammedov <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 6ab0c4bd1dc758b8a1f456d7f748ec313b5fde3d
https://github.com/qemu/qemu/commit/6ab0c4bd1dc758b8a1f456d7f748ec313b5fde3d
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: fix device physical address base
According to ACPI 6.0 spec, "Memory Device Physical Address
Region Base" in memdev is defined as "This field provides the
Device Physical Address base of the region". This field should
be zero in our case
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: dba00936ea26e2b103ade4ac0f8a31aa6c410b6f
https://github.com/qemu/qemu/commit/dba00936ea26e2b103ade4ac0f8a31aa6c410b6f
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: fix ARG3 conflict
As ARG3 is a reserved name, we rename it to FARG
Suggested-by: Igor Mammedov <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 48bee47697c6bf89e9e58e65829337f8ce7b6e46
https://github.com/qemu/qemu/commit/48bee47697c6bf89e9e58e65829337f8ce7b6e46
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: fix Arg6 usage
As the function only has 5 args, we use local7 instead of it
Suggested-by: Igor Mammedov <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 08f0fbaac4df9f17336f77d7491000442addffdc
https://github.com/qemu/qemu/commit/08f0fbaac4df9f17336f77d7491000442addffdc
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/Makefile.objs
Log Message:
-----------
nvdimm acpi: compile nvdimm acpi code arch-independently
As the arch dependent info, TARGET_PAGE_SIZE, has been dropped
from nvdimm acpi code, it can be compiled arch-independently
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: fa1a448dda87c97431d1f177075fbf00ace5f9d8
https://github.com/qemu/qemu/commit/fa1a448dda87c97431d1f177075fbf00ace5f9d8
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi nvdimm: rename result_size to dsm_out_buf_siz
Rename it as dsm_out_buf_siz is more descriptive
Suggested-by: Igor Mammedov <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 3ae66c45f94fe806c58daf95142d917ad14f7afb
https://github.com/qemu/qemu/commit/3ae66c45f94fe806c58daf95142d917ad14f7afb
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
nvdimm acpi: use common macros instead of magic names
There are some names repeatedly used in acpi code, define them
as macros to refine the code
Suggested-by: Igor Mammedov <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: bdfd065b1f75cacca21af0b8d4811c64cc48d04c
https://github.com/qemu/qemu/commit/bdfd065b1f75cacca21af0b8d4811c64cc48d04c
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
M hw/i386/acpi-build.c
M include/hw/mem/nvdimm.h
Log Message:
-----------
nvdimm acpi: prebuild nvdimm devices for available slots
For each NVDIMM present or intended to be supported by platform,
platform firmware also exposes an ACPI Namespace Device under
the root device
So it builds nvdimm devices for all slots to support vNVDIMM hotplug
Reviewed-by: Stefan Hajnoczi <address@hidden>
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 75b0713e189a981e5bfd087d5f35705446bbb12a
https://github.com/qemu/qemu/commit/75b0713e189a981e5bfd087d5f35705446bbb12a
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
M hw/core/hotplug.c
M hw/core/qdev.c
M hw/i386/acpi-build.c
M hw/i386/pc.c
M include/hw/hotplug.h
M include/hw/mem/nvdimm.h
Log Message:
-----------
nvdimm acpi: introduce fit buffer
The buffer is used to save the FIT info for all the presented nvdimm
devices which is updated after the nvdimm device is plugged or
unplugged. In the later patch, it will be used to construct NVDIMM
ACPI _FIT method which reflects the presented nvdimm devices after
nvdimm hotplug
As FIT buffer can not completely mapped into guest address space,
OSPM will exit to QEMU multiple times, however, there is the race
condition - FIT may be changed during these multiple exits, so that
some rules are introduced:
1) the user should hold the @lock to access the buffer and
2) mark @dirty whenever the buffer is updated.
@dirty is cleared for the first time OSPM gets fit buffer, if
dirty is detected in the later access, OSPM will restart the
access
As fit should be updated after nvdimm device is successfully realized
so that a new hotplug callback, post_hotplug, is introduced
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 806864d9a8a6d5c4cee2ca9bd00474346143113b
https://github.com/qemu/qemu/commit/806864d9a8a6d5c4cee2ca9bd00474346143113b
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M docs/specs/acpi_nvdimm.txt
M hw/acpi/nvdimm.c
Log Message:
-----------
nvdimm acpi: introduce _FIT
_FIT is required for hotplug support, guest will inquire the updated
device info from it if a hotplug event is received
As FIT buffer is not completely mapped into guest address space, so a
new function, Read FIT whose UUID is UUID
648B9CF2-CDA1-4312-8AD9-49C4AF32BD62, handle 0x10000, function index
is 0x1, is reserved by QEMU to read the piece of FIT buffer. The buffer
is concatenated before _FIT return
Refer to docs/specs/acpi-nvdimm.txt for detailed design
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: b097cc52fc9126bd1a71dae8302b8536d28104dd
https://github.com/qemu/qemu/commit/b097cc52fc9126bd1a71dae8302b8536d28104dd
Author: Xiao Guangrong <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M docs/specs/acpi_mem_hotplug.txt
M hw/acpi/memory_hotplug.c
M hw/i386/acpi-build.c
M hw/i386/pc.c
M hw/mem/nvdimm.c
M include/hw/acpi/acpi_dev_interface.h
Log Message:
-----------
pc: memhp: enable nvdimm device hotplug
_GPE.E04 is dedicated for nvdimm device hotplug
Signed-off-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 66abfddb28e9fe92d8230d711c8faeaf496aaa88
https://github.com/qemu/qemu/commit/66abfddb28e9fe92d8230d711c8faeaf496aaa88
Author: Corey Minyard <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/ipmi_bmc_extern.c
M hw/ipmi/ipmi_bmc_sim.c
Log Message:
-----------
ipmi: Remove hotplug from IPMI BMCs
No hotplug support, make sure it doesn't happen.
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Marc-André Lureau <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 0eb4d4eee1ac94600fbb7bf675cb5cae2aead217
https://github.com/qemu/qemu/commit/0eb4d4eee1ac94600fbb7bf675cb5cae2aead217
Author: Corey Minyard <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/ipmi_bmc_sim.c
Log Message:
-----------
ipmi_bmc_sim: Remove an unnecessary mutex
Get rid of the unnecessary mutex, it was a vestige
of something else that was not done. That way we don't
have to free it.
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Marc-André Lureau <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 2b7812d303a477d70c3cf62eaf3b1545babe05e1
https://github.com/qemu/qemu/commit/2b7812d303a477d70c3cf62eaf3b1545babe05e1
Author: Cédric Le Goater <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/ipmi.c
Log Message:
-----------
ipmi: chassis poweroff should use qemu_system_shutdown_request()
When issuing a chassis 'powerdown' control command, the routine
qemu_system_shutdown_request() should be used to exit the guest.
qemu_system_powerdown_request() will initiate a soft shutdown which is
not what is required by the IPMI (28.3 Chassis Control Command):
0h = power down. Force system into soft off (S4/S45) state. This
is for 'emergency' management power down actions. The command does
not initiate a clean shut-down of the operating system prior to
powering down the system
Signed-off-by: Cédric Le Goater <address@hidden>
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 9c22c1c347af736ce86b7ecea8afa3a366f987c3
https://github.com/qemu/qemu/commit/9c22c1c347af736ce86b7ecea8afa3a366f987c3
Author: Corey Minyard <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/ipmi.c
Log Message:
-----------
ipmi: Implement shutdown via ACPI overtemp
This is allowed by the IPMI specification for graceful shutdown,
so implement it.
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 4059fa63b7fae7e92cd54bd905366c46d0b62e69
https://github.com/qemu/qemu/commit/4059fa63b7fae7e92cd54bd905366c46d0b62e69
Author: Daniel P. Berrange <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/Makefile.objs
Log Message:
-----------
ipmi: fix build config variable name for ipmi_bmc_extern.o
The original commit:
commit 67aa56fc03bea44ccf384ea400515a8a58844a50
Author: Corey Minyard <address@hidden>
Date: Thu Dec 17 12:50:06 2015 -0600
ipmi: Add an external connection simulation interface
defined a new variable CONFIG_IPMI_EXTERN, but then went
on to mistakely use the pre-existing CONFIG_IPMI_LOCAL
variable.
Signed-off-by: Daniel P. Berrange <address@hidden>
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: f53b9f3625f1fc66e4514981e7d9315fa74516a7
https://github.com/qemu/qemu/commit/f53b9f3625f1fc66e4514981e7d9315fa74516a7
Author: Corey Minyard <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/ipmi/ipmi_bmc_extern.c
M tests/ipmi-bt-test.c
Log Message:
-----------
ipmi: Add graceful shutdown handling to the external BMC
I misunderstood the workings of the power settings, the power off
is a force off operation and there needs to be a separate graceful
shutdown operation. So replace the force off operation with a
graceful shutdown.
Signed-off-by: Corey Minyard <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 698ae42b9124dce23e03d0fea2e635b70540ef13
https://github.com/qemu/qemu/commit/698ae42b9124dce23e03d0fea2e635b70540ef13
Author: Corey Minyard <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/ipmi.c
Log Message:
-----------
acpi/ipmi: Initialize the fwinfo before fetching it
The initialization was missed before, resulting in some
bad data in the smbus case.
Signed-off-by: Corey Minyard <address@hidden>
Cc: address@hidden
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 53000638f233d6ba1d584a68b74f2cde79615b80
https://github.com/qemu/qemu/commit/53000638f233d6ba1d584a68b74f2cde79615b80
Author: Haozhong Zhang <address@hidden>
Date: 2016-11-01 (Tue, 01 Nov 2016)
Changed paths:
M hw/acpi/nvdimm.c
Log Message:
-----------
acpi: fix assert failure caused by commit 35c5a52d
Commit 35c5a52d "acpi: do not use TARGET_PAGE_SIZE" changed struct
NvdimmDsmIn from a variable-size structure to a fixed-size structure of
4096 bytes. It forgot to adjust an assert in
nvdimm_dsm_set_label_data(..., NvdimmDsmIn *in, ...):
assert(sizeof(*in) + sizeof(*set_label_data) + set_label_data->length <=
4096);
which could crash QEMU when guest writes NVDIMM labels.
Fix it by replacing sizeof(*in) by offsetof(NvdimmDsmIn, arg3).
Signed-off-by: Haozhong Zhang <address@hidden>
Reported-by: Dan Williams <address@hidden>
Tested-by: Dan Williams <address@hidden>
Reviewed-by: Xiao Guangrong <address@hidden>
Reviewed-by: Michael S. Tsirkin <address@hidden>
Signed-off-by: Michael S. Tsirkin <address@hidden>
Commit: 1775f111eaf7f49efcec30152db44a184c1e2222
https://github.com/qemu/qemu/commit/1775f111eaf7f49efcec30152db44a184c1e2222
Author: Haozhong Zhang <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M exec.c
Log Message:
-----------
exec.c: check memory backend file size with 'size' option
If the memory backend file is not large enough to hold the required 'size',
Qemu will report error and exit.
Signed-off-by: Haozhong Zhang <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Eduardo Habkost <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: b1a75b3348010820cc324943f09e090ea1fc524f
https://github.com/qemu/qemu/commit/b1a75b3348010820cc324943f09e090ea1fc524f
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M include/block/nbd.h
M nbd/nbd-internal.h
M nbd/server.c
M qemu-nbd.c
M qemu-nbd.texi
Log Message:
-----------
nbd: Add qemu-nbd -D for human-readable description
The NBD protocol allows servers to advertise a human-readable
description alongside an export name during NBD_OPT_LIST. Add
an option to pass through the user's string to the NBD client.
Doing this also makes it easier to test commit 200650d4, which
is the client counterpart of receiving the description.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: b626b51a6721e53817155af720243f59072e424f
https://github.com/qemu/qemu/commit/b626b51a6721e53817155af720243f59072e424f
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M block/nbd-client.c
M include/block/nbd.h
M nbd/client.c
M nbd/nbd-internal.h
M nbd/server.c
Log Message:
-----------
nbd: Treat flags vs. command type as separate fields
Current upstream NBD documents that requests have a 16-bit flags,
followed by a 16-bit type integer; although older versions mentioned
only a 32-bit field with masking to find flags. Since the protocol
is in network order (big-endian over the wire), the ABI is unchanged;
but dealing with the flags as a separate field rather than masking
will make it easier to add support for upcoming NBD extensions that
increase the number of both flags and commands.
Improve some comments in nbd.h based on the current upstream
NBD protocol (https://github.com/yoe/nbd/blob/master/doc/proto.md),
and touch some nearby code to keep checkpatch.pl happy.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 315f78abfce1f12bca259e8d8a41a42efbf970d1
https://github.com/qemu/qemu/commit/315f78abfce1f12bca259e8d8a41a42efbf970d1
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/server.c
Log Message:
-----------
nbd: Rename NBDRequest to NBDRequestData
We have both 'struct NBDRequest' and 'struct nbd_request'; making
it confusing to see which does what. Furthermore, we want to
rename nbd_request to align with our normal CamelCase naming
conventions. So, rename the struct which is used to associate
the data received during request callbacks, while leaving the
shorter name for the description of the request sent over the
wire in the NBD protocol.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 10676b81a9a69e9660fc203e3fe7d61a80ef1089
https://github.com/qemu/qemu/commit/10676b81a9a69e9660fc203e3fe7d61a80ef1089
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M block/nbd-client.c
M block/nbd-client.h
M block/nbd.c
Log Message:
-----------
nbd: Rename NbdClientSession to NBDClientSession
It's better to use consistent capitalization of the namespace
used for NBD functions; we have more instances of NBD* than
Nbd*.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: ed2dd91267a813e4ac5619a2fb53f55c005fcfa6
https://github.com/qemu/qemu/commit/ed2dd91267a813e4ac5619a2fb53f55c005fcfa6
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M block/nbd-client.c
M block/nbd-client.h
M include/block/nbd.h
M nbd/client.c
M nbd/server.c
Log Message:
-----------
nbd: Rename struct nbd_request and nbd_reply
Our coding convention prefers CamelCase names, and we already
have other existing structs with NBDFoo naming. Let's be
consistent, before later patches add even more structs.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 526e5c6559928ed98332dd27f026e8cbc95f466a
https://github.com/qemu/qemu/commit/526e5c6559928ed98332dd27f026e8cbc95f466a
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/server.c
Log Message:
-----------
nbd: Share common reply-sending code in server
Rather than open-coding NBD_REP_SERVER, reuse the code we
already have by adding a length parameter. Additionally,
the refactoring will make adding NBD_OPT_GO in a later patch
easier.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 3668328303429f3bc93ab3365c66331600b06a2d
https://github.com/qemu/qemu/commit/3668328303429f3bc93ab3365c66331600b06a2d
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/server.c
Log Message:
-----------
nbd: Send message along with server NBD_REP_ERR errors
The NBD Protocol allows us to send human-readable messages
along with any NBD_REP_ERR error during option negotiation;
make use of this fact for clients that know what to do with
our message.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: c8a3a1b6c4034cf53cdbd953331c72f9573edb77
https://github.com/qemu/qemu/commit/c8a3a1b6c4034cf53cdbd953331c72f9573edb77
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M include/block/nbd.h
M nbd/client.c
M nbd/nbd-internal.h
Log Message:
-----------
nbd: Share common option-sending code in client
Rather than open-coding each option request, it's easier to
have common helper functions do the work. That in turn requires
having convenient packed types for handling option requests
and replies.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 2cdbf41362cbc9b977dd458b6508352e45f2cb42
https://github.com/qemu/qemu/commit/2cdbf41362cbc9b977dd458b6508352e45f2cb42
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/client.c
Log Message:
-----------
nbd: Let server know when client gives up negotiation
The NBD spec says that a client should send NBD_OPT_ABORT
rather than just dropping the connection, if the client doesn't
like something the server sent during option negotiation. This
is a best-effort attempt only, and can only be done in places
where we know the server is still in sync with what we've sent,
whether or not we've read everything the server has sent.
Technically, the server then has to reply with NBD_REP_ACK, but
it's not worth complicating the client to wait around for that
reply.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 7d3123e1775f16bf23fa8d5bac17a3d8a9e72583
https://github.com/qemu/qemu/commit/7d3123e1775f16bf23fa8d5bac17a3d8a9e72583
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/client.c
Log Message:
-----------
nbd: Let client skip portions of server reply
The server has a nice helper function nbd_negotiate_drop_sync()
which lets it easily ignore fluff from the client (such as the
payload to an unknown option request). We can't quite make it
common, since it depends on nbd_negotiate_read() which handles
coroutine magic, but we can copy the idea into the client where
we have places where we want to ignore data (such as the
description tacked on the end of NBD_REP_SERVER).
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 75368aab9ba27f762acf5a51062c951a1fb1e006
https://github.com/qemu/qemu/commit/75368aab9ba27f762acf5a51062c951a1fb1e006
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/client.c
Log Message:
-----------
nbd: Less allocation during NBD_OPT_LIST
Since we know that the maximum name we are willing to accept
is small enough to stack-allocate, rework the iteration over
NBD_OPT_LIST responses to reuse a stack buffer rather than
allocating every time. Furthermore, we don't even have to
allocate if we know the server's length doesn't match what
we are searching for.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: c203c59ad9dc677b27e00ba76d221fd7e93c1aa6
https://github.com/qemu/qemu/commit/c203c59ad9dc677b27e00ba76d221fd7e93c1aa6
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M include/block/nbd.h
M nbd/client.c
M nbd/server.c
Log Message:
-----------
nbd: Support shorter handshake
The NBD Protocol allows the server and client to mutually agree
on a shorter handshake (omit the 124 bytes of reserved 0), via
the server advertising NBD_FLAG_NO_ZEROES and the client
acknowledging with NBD_FLAG_C_NO_ZEROES (only possible in
newstyle, whether or not it is fixed newstyle). It doesn't
shave much off the wire, but we might as well implement it.
Signed-off-by: Eric Blake <address@hidden>
Reviewed-by: Alex Bligh <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 8b34a9dbc3f2c0afe3450cb20b94cc30f450e77b
https://github.com/qemu/qemu/commit/8b34a9dbc3f2c0afe3450cb20b94cc30f450e77b
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M nbd/client.c
Log Message:
-----------
nbd: Refactor conversion to errno to silence checkpatch
Checkpatch complains that 'return EINVAL' is usually wrong
(since we tend to favor 'return -EINVAL'). But it is a
false positive for nbd_errno_to_system_errno(). Since NBD
may add future defined wire values, refactor the code to
keep checkpatch happy.
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: b6f5d3b573fe43da1f9fa07b7454e4492f409411
https://github.com/qemu/qemu/commit/b6f5d3b573fe43da1f9fa07b7454e4492f409411
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M include/block/nbd.h
M include/qemu/osdep.h
M nbd/client.c
M nbd/nbd-internal.h
M nbd/server.c
Log Message:
-----------
nbd: Improve server handling of shutdown requests
NBD commit 6d34500b clarified how clients and servers are supposed
to behave before closing a connection. It added NBD_REP_ERR_SHUTDOWN
(for the server to announce it is about to go away during option
haggling, so the client should quit sending NBD_OPT_* other than
NBD_OPT_ABORT) and ESHUTDOWN (for the server to announce it is about
to go away during transmission, so the client should quit sending
NBD_CMD_* other than NBD_CMD_DISC). It also clarified that
NBD_OPT_ABORT gets a reply, while NBD_CMD_DISC does not.
This patch merely adds the missing reply to NBD_OPT_ABORT and teaches
the client to recognize server errors. Actually teaching the server
to send NBD_REP_ERR_SHUTDOWN or ESHUTDOWN would require knowing that
the server has been requested to shut down soon (maybe we could do
that by installing a SIGINT handler in qemu-nbd, which transitions
from RUNNING to a new state that waits for the client to react,
rather than just out-right quitting - but that's a bigger task for
another day).
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
[Move dummy ESHUTDOWN to include/qemu/osdep.h. - Paolo]
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f
https://github.com/qemu/qemu/commit/1f4d6d18edfeaea64ae74bf5254b8d0e923dc73f
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M include/block/nbd.h
M nbd/server.c
Log Message:
-----------
nbd: Implement NBD_CMD_WRITE_ZEROES on server
Upstream NBD protocol recently added the ability to efficiently
write zeroes without having to send the zeroes over the wire,
along with a flag to control whether the client wants to allow
a hole.
Note that when it comes to requiring full allocation, vs.
permitting optimizations, the NBD spec intentionally picked a
different sense for the flag; the rules in qemu are:
MAY_UNMAP == 0: must write zeroes
MAY_UNMAP == 1: may use holes if reads will see zeroes
while in NBD, the rules are:
FLAG_NO_HOLE == 1: must write zeroes
FLAG_NO_HOLE == 0: may use holes if reads will see zeroes
In all cases, the 'may use holes' scenario is optional (the
server need not use a hole, and must not use a hole if
subsequent reads would not see zeroes).
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: fa778fffdfafce811bba3dd97de41fb524b861f7
https://github.com/qemu/qemu/commit/fa778fffdfafce811bba3dd97de41fb524b861f7
Author: Eric Blake <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M block/nbd-client.c
M block/nbd-client.h
M block/nbd.c
Log Message:
-----------
nbd: Implement NBD_CMD_WRITE_ZEROES on client
Upstream NBD protocol recently added the ability to efficiently
write zeroes without having to send the zeroes over the wire,
along with a flag to control whether the client wants a hole.
The generic block code takes care of falling back to the obvious
write of lots of zeroes if we return -ENOTSUP because the server
does not have WRITE_ZEROES.
Ideally, since NBD_CMD_WRITE_ZEROES does not involve any data
over the wire, we want to support transactions that are much
larger than the normal 32M limit imposed on NBD_CMD_WRITE. But
the server may still have a limit smaller than UINT_MAX, so
until experimental NBD protocol additions for advertising various
command sizes is finalized (see [1], [2]), for now we just stick to
the same limits as normal writes.
[1] https://github.com/yoe/nbd/blob/extension-info/doc/proto.md
[2] https://sourceforge.net/p/nbd/mailman/message/35081223/
Signed-off-by: Eric Blake <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: fffbd9cf1befa256d75bc45541adca405bb65dd5
https://github.com/qemu/qemu/commit/fffbd9cf1befa256d75bc45541adca405bb65dd5
Author: Paolo Bonzini <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M qemu-char.c
Log Message:
-----------
qemu-char: do not forward events through the mux until QEMU has started
Otherwise, the CHR_EVENT_OPENED event is sent twice: first when the
backend (for example "stdio") is opened, and second after processing
the command line.
The incorrect sending of the event prints the monitor banner when
QEMU is started with "-serial mon:stdio". This includes the "(qemu)"
prompt; thus the monitor seems to be dead, whereas actually the
active front-end is the serial port.
Reported-by: Dr. David Alan Gilbert <address@hidden>
Tested-by: Dr. David Alan Gilbert <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: d14fabd9c2debef0d51ec90af1326e83111a77de
https://github.com/qemu/qemu/commit/d14fabd9c2debef0d51ec90af1326e83111a77de
Author: Paolo Bonzini <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M net/slirp.c
Log Message:
-----------
slirp: fix CharDriver breakage
SLIRP expects a CharBackend as the third argument to slirp_add_exec,
but net/slirp.c was passing a CharDriverState. Fix this to restore
guestfwd functionality.
Reported-by: Dr. David Alan Gilbert <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 95ea69fb46266aaa46d0c8b7f0ba8c4903dbe4e3
https://github.com/qemu/qemu/commit/95ea69fb46266aaa46d0c8b7f0ba8c4903dbe4e3
Author: Luwei Kang <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M target-i386/cpu.c
M target-i386/cpu.h
Log Message:
-----------
x86: add AVX512_4VNNIW and AVX512_4FMAPS features
The spec can be found in Intel Software Developer Manual or in
Instruction Set Extensions Programming Reference.
Signed-off-by: Piotr Luc <address@hidden>
Signed-off-by: Luwei Kang <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 000980cb8307afe0578368cee8f31018905bb036
https://github.com/qemu/qemu/commit/000980cb8307afe0578368cee8f31018905bb036
Author: Jeff Cody <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M scripts/checkpatch.pl
Log Message:
-----------
checkpatch: allow spaces before parenthesis for 'coroutine_fn'
Signed-off-by: Jeff Cody <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 864111f422babcf8ce837fb47f7f9e1948446f22
https://github.com/qemu/qemu/commit/864111f422babcf8ce837fb47f7f9e1948446f22
Author: Christian Borntraeger <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M qapi-schema.json
M vl.c
Log Message:
-----------
vl: exit qemu on guest panic if -no-shutdown is not set
For automated testing purposes it can be helpful to exit qemu
(poweroff) when the guest panics. Make this the default unless
-no-shutdown is specified.
For internal-errors like errors from KVM_RUN the behaviour is
not changed, in other words QEMU does not exit to allow debugging
in the QEMU monitor.
Signed-off-by: Christian Borntraeger <address@hidden>
Message-Id: <address@hidden>
Reviewed-by: Eric Blake <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 85cdeb36a4d4f46f04ea3f4a9e4f1e86dd8e5c9a
https://github.com/qemu/qemu/commit/85cdeb36a4d4f46f04ea3f4a9e4f1e86dd8e5c9a
Author: Pranith Kumar <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M docs/rcu.txt
Log Message:
-----------
docs/rcu.txt: Fix minor typo
s/presented/prevented/
Signed-off-by: Pranith Kumar <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: 7d175d29c9430fcba7a98f2c71925137b7870da4
https://github.com/qemu/qemu/commit/7d175d29c9430fcba7a98f2c71925137b7870da4
Author: Max Reitz <address@hidden>
Date: 2016-11-02 (Wed, 02 Nov 2016)
Changed paths:
M main-loop.c
Log Message:
-----------
main-loop: Suppress I/O thread warning under qtest
We do not want to display the "I/O thread spun" warning for test cases
that run under qtest. The first attempt for this (commit
01c22f2cdd4fcf02276ea10f48253850a5fd7259) tested whether qtest_enabled()
was true.
Commit 21a24302e85024dd7b2a151158adbc1f5dc5c4dd correctly recognized
that just testing qtest_enabled() is not sufficient since there are some
tests that do not use the qtest accelerator but just the qtest character
device, and thus replaced qtest_enabled() by qtest_driver().
However, there are also some tests that only use the qtest accelerator
and not the qtest chardev; perhaps most notably the bash iotests.
Therefore, we have to check both qtest_enabled() and qtest_driver().
Signed-off-by: Max Reitz <address@hidden>
Message-Id: <address@hidden>
Signed-off-by: Paolo Bonzini <address@hidden>
Commit: c2a4b384f5484fed94b4466151c7f9a705414a57
https://github.com/qemu/qemu/commit/c2a4b384f5484fed94b4466151c7f9a705414a57
Author: Stefan Hajnoczi <address@hidden>
Date: 2016-11-03 (Thu, 03 Nov 2016)
Changed paths:
M MAINTAINERS
M backends/Makefile.objs
A backends/cryptodev-builtin.c
A backends/cryptodev.c
M docs/specs/acpi_mem_hotplug.txt
M docs/specs/acpi_nvdimm.txt
M hw/acpi/Makefile.objs
M hw/acpi/ipmi.c
M hw/acpi/memory_hotplug.c
M hw/acpi/nvdimm.c
M hw/block/dataplane/virtio-blk.c
M hw/block/dataplane/virtio-blk.h
M hw/block/virtio-blk.c
M hw/core/hotplug.c
M hw/core/qdev.c
M hw/i386/acpi-build.c
M hw/i386/pc.c
M hw/ipmi/Makefile.objs
M hw/ipmi/ipmi.c
M hw/ipmi/ipmi_bmc_extern.c
M hw/ipmi/ipmi_bmc_sim.c
M hw/mem/nvdimm.c
M hw/s390x/virtio-ccw.c
M hw/s390x/virtio-ccw.h
M hw/scsi/virtio-scsi-dataplane.c
M hw/scsi/virtio-scsi.c
M hw/virtio/Makefile.objs
M hw/virtio/vhost.c
M hw/virtio/virtio-balloon.c
M hw/virtio/virtio-bus.c
A hw/virtio/virtio-crypto-pci.c
A hw/virtio/virtio-crypto.c
M hw/virtio/virtio-mmio.c
M hw/virtio/virtio-pci.c
M hw/virtio/virtio-pci.h
M hw/virtio/virtio.c
M include/hw/acpi/acpi_dev_interface.h
M include/hw/hotplug.h
M include/hw/mem/nvdimm.h
M include/hw/virtio/virtio-bus.h
A include/hw/virtio/virtio-crypto.h
M include/hw/virtio/virtio-scsi.h
M include/hw/virtio/virtio.h
A include/standard-headers/linux/virtio_crypto.h
M include/standard-headers/linux/virtio_ids.h
A include/sysemu/cryptodev.h
M qemu-options.hx
M tests/ipmi-bt-test.c
Log Message:
-----------
Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging
virtio, pc: fixes and features
nvdimm hotplug support
virtio migration and ioeventfd rework
virtio crypto device
ipmi fixes
Signed-off-by: Michael S. Tsirkin <address@hidden>
# gpg: Signature made Tue 01 Nov 2016 05:23:40 PM GMT
# gpg: using RSA key 0x281F0DB8D28D5469
# gpg: Good signature from "Michael S. Tsirkin <address@hidden>"
# gpg: aka "Michael S. Tsirkin <address@hidden>"
# Primary key fingerprint: 0270 606B 6F3C DF3D 0B17 0970 C350 3912 AFBE 8E67
# Subkey fingerprint: 5D09 FD08 71C8 F85B 94CA 8A0D 281F 0DB8 D28D 5469
* remotes/mst/tags/for_upstream: (47 commits)
acpi: fix assert failure caused by commit 35c5a52d
acpi/ipmi: Initialize the fwinfo before fetching it
ipmi: Add graceful shutdown handling to the external BMC
ipmi: fix build config variable name for ipmi_bmc_extern.o
ipmi: Implement shutdown via ACPI overtemp
ipmi: chassis poweroff should use qemu_system_shutdown_request()
ipmi_bmc_sim: Remove an unnecessary mutex
ipmi: Remove hotplug from IPMI BMCs
pc: memhp: enable nvdimm device hotplug
nvdimm acpi: introduce _FIT
nvdimm acpi: introduce fit buffer
nvdimm acpi: prebuild nvdimm devices for available slots
nvdimm acpi: use common macros instead of magic names
acpi nvdimm: rename result_size to dsm_out_buf_siz
nvdimm acpi: compile nvdimm acpi code arch-independently
acpi nvdimm: fix Arg6 usage
acpi nvdimm: fix ARG3 conflict
acpi nvdimm: fix device physical address base
acpi nvdimm: fix OperationRegion definition
acpi nvdimm: fix wrong buffer size returned by DSM method
...
Signed-off-by: Stefan Hajnoczi <address@hidden>
Commit: 199a5bde46b0eab898ab1ec591f423000302569f
https://github.com/qemu/qemu/commit/199a5bde46b0eab898ab1ec591f423000302569f
Author: Stefan Hajnoczi <address@hidden>
Date: 2016-11-03 (Thu, 03 Nov 2016)
Changed paths:
M block/nbd-client.c
M block/nbd-client.h
M block/nbd.c
M docs/rcu.txt
M exec.c
M include/block/nbd.h
M include/glib-compat.h
M include/qemu/error-report.h
M include/qemu/osdep.h
M main-loop.c
M monitor.c
M nbd/client.c
M nbd/nbd-internal.h
M nbd/server.c
M net/slirp.c
M qapi-schema.json
M qemu-char.c
M qemu-nbd.c
M qemu-nbd.texi
M scripts/checkpatch.pl
M stubs/Makefile.objs
A stubs/error-printf.c
R stubs/mon-printf.c
M target-i386/cpu.c
M target-i386/cpu.h
M util/qemu-error.c
M vl.c
Log Message:
-----------
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging
* NBD bugfix (Changlong)
* NBD write zeroes support (Eric)
* Memory backend fixes (Haozhong)
* Atomics fix (Alex)
* New AVX512 features (Luwei)
* "make check" logging fix (Paolo)
* Chardev refactoring fallout (Paolo)
* Small checkpatch improvements (Paolo, Jeff)
# gpg: Signature made Wed 02 Nov 2016 08:31:11 AM GMT
# gpg: using RSA key 0xBFFBD25F78C7AE83
# gpg: Good signature from "Paolo Bonzini <address@hidden>"
# gpg: aka "Paolo Bonzini <address@hidden>"
# 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: (30 commits)
main-loop: Suppress I/O thread warning under qtest
docs/rcu.txt: Fix minor typo
vl: exit qemu on guest panic if -no-shutdown is not set
checkpatch: allow spaces before parenthesis for 'coroutine_fn'
x86: add AVX512_4VNNIW and AVX512_4FMAPS features
slirp: fix CharDriver breakage
qemu-char: do not forward events through the mux until QEMU has started
nbd: Implement NBD_CMD_WRITE_ZEROES on client
nbd: Implement NBD_CMD_WRITE_ZEROES on server
nbd: Improve server handling of shutdown requests
nbd: Refactor conversion to errno to silence checkpatch
nbd: Support shorter handshake
nbd: Less allocation during NBD_OPT_LIST
nbd: Let client skip portions of server reply
nbd: Let server know when client gives up negotiation
nbd: Share common option-sending code in client
nbd: Send message along with server NBD_REP_ERR errors
nbd: Share common reply-sending code in server
nbd: Rename struct nbd_request and nbd_reply
nbd: Rename NbdClientSession to NBDClientSession
...
Signed-off-by: Stefan Hajnoczi <address@hidden>
Compare: https://github.com/qemu/qemu/compare/4eb28abd52d4...199a5bde46b0
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-commits] [qemu/qemu] ea43e2: virtio/migration: Add VMStateDescription to Virtio...,
GitHub <=