[Qemu-commits] [qemu/qemu] 2902a2: configure: Only clone softfloat-3 repositories if ...

[Peter Maydell]

  Branch: refs/heads/staging
  Home:   https://github.com/qemu/qemu
  Commit: 2902a278e4f509efccecd25e6dd8d381149a8f4a
      
https://github.com/qemu/qemu/commit/2902a278e4f509efccecd25e6dd8d381149a8f4a
  Author: Philippe Mathieu-Daudé <philmd@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M configure

  Log Message:
  -----------
  configure: Only clone softfloat-3 repositories if TCG is enabled

Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210512045821.3257963-1-philmd@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 50bac38115bf17b2437e9f0dce0ac887fad817da
      
https://github.com/qemu/qemu/commit/50bac38115bf17b2437e9f0dce0ac887fad817da
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M configure

  Log Message:
  -----------
  configure: check for submodules if --with-git-submodules=ignore

Right now --with-git-submodules=ignore has a subtle difference from
just running without a .git directory, in that it does not check
that submodule sources actually exist.  Move the check for
ui/keycodemapdb/README so that it happens even if the user
specified --with-git-submodules=ignore, with a customized
error message that is more suitable for this situation.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 957899f7b972ec1a02e3cb44a2b181fc8c0c17ef
      
https://github.com/qemu/qemu/commit/957899f7b972ec1a02e3cb44a2b181fc8c0c17ef
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M Makefile
    M configure

  Log Message:
  -----------
  configure: simplify assignment to GIT_SUBMODULES

Do not guard each assignment with a check for --with-git-submodules=ignore.
To avoid a confusing "GIT" line from the Makefile, guard the 
git-submodule-update
recipe so that it is empty when --with-git-submodules=ignore.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 7c37c73f0121a5aa2975a609f013c72c16eafb5d
      
https://github.com/qemu/qemu/commit/7c37c73f0121a5aa2975a609f013c72c16eafb5d
  Author: Philippe Mathieu-Daudé <philmd@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M default-configs/devices/ppc64-softmmu.mak
    M hw/arm/Kconfig
    M hw/i386/Kconfig
    M hw/mem/Kconfig
    M hw/ppc/Kconfig

  Log Message:
  -----------
  hw/mem/nvdimm: Use Kconfig 'imply' instead of 'depends on'

Per the kconfig.rst:

  A device should be listed [...] ``imply`` if (depending on
  the QEMU command line) the board may or  may not be started
  without it.

This is the case with the NVDIMM device, so use the 'imply'
weak reverse dependency to select the symbol.

Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210511155354.3069141-2-philmd@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 5c9f0f4113a1126e8c4ec4f3eb6126569762fa18
      
https://github.com/qemu/qemu/commit/5c9f0f4113a1126e8c4ec4f3eb6126569762fa18
  Author: Yang Zhong <yang.zhong@intel.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M target/i386/cpu.c
    M target/i386/cpu.h

  Log Message:
  -----------
  i386/cpu: Expose AVX_VNNI instruction to guest

Expose AVX (VEX-encoded) versions of the Vector Neural Network
Instructions to guest.

The bit definition:
CPUID.(EAX=7,ECX=1):EAX[bit 4] AVX_VNNI

The following instructions are available when this feature is
present in the guest.
  1. VPDPBUS: Multiply and Add Unsigned and Signed Bytes
  2. VPDPBUSDS: Multiply and Add Unsigned and Signed Bytes with Saturation
  3. VPDPWSSD: Multiply and Add Signed Word Integers
  4. VPDPWSSDS: Multiply and Add Signed Integers with Saturation

As for the kvm related code, please reference Linux commit id 1085a6b585d7.

The release document ref below link:
https://software.intel.com/content/www/us/en/develop/download/\
intel-architecture-instruction-set-extensions-programming-reference.html

Signed-off-by: Yang Zhong <yang.zhong@intel.com>
Message-Id: <20210407015609.22936-1-yang.zhong@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 05cf5cd7099161a896e0a48e7f585e50702b62a2
      
https://github.com/qemu/qemu/commit/05cf5cd7099161a896e0a48e7f585e50702b62a2
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M meson

  Log Message:
  -----------
  meson: bump submodule to 0.57.2

The main advantage of 0.57 is that it fixes
https://github.com/mesonbuild/meson/pull/7900, thus avoiding unnecessary
rebuilds after running meson.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: db02488b282b63fa2c9b276df6b4c33b8c6c3db0
      
https://github.com/qemu/qemu/commit/db02488b282b63fa2c9b276df6b4c33b8c6c3db0
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M hmp-commands.hx
    M qapi/qom.json

  Log Message:
  -----------
  object: add more commands to preconfig mode

Creating and destroying QOM objects does not require a fully constructed
machine.  Allow running object-add and object-del before machine
initialization has concluded.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 25142bd8bc114270e126bda639a991c2ab5c3d10
      
https://github.com/qemu/qemu/commit/25142bd8bc114270e126bda639a991c2ab5c3d10
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M qapi/qom.json
    M softmmu/qtest.c
    M softmmu/vl.c

  Log Message:
  -----------
  qtest: add a QOM object for qtest

The qtest server right now can only be created using the -qtest
and -qtest-log options.  Allow an alternative way to create it
using "-object qtest,chardev=...,log=...".

This is part of the long term plan to make more (or all) of
QEMU configurable through QMP and preconfig mode.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 06fd5cc0c27ff5bf9f59c91280c7598fec68c5df
      
https://github.com/qemu/qemu/commit/06fd5cc0c27ff5bf9f59c91280c7598fec68c5df
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c

  Log Message:
  -----------
  KVM: do not allow setting properties at runtime

Only allow accelerator properties to be set when the
accelerator is being created.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: cf0c7533946fc14a203db6d5d863d4114da72edd
      
https://github.com/qemu/qemu/commit/cf0c7533946fc14a203db6d5d863d4114da72edd
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M include/exec/memory.h
    M softmmu/memory.c

  Log Message:
  -----------
  memory: Introduce log_sync_global() to memory listener

Some of the memory listener may want to do log synchronization without
being able to specify a range of memory to sync but always globally.
Such a memory listener should provide this new method instead of the
log_sync() method.

Obviously we can also achieve similar thing when we put the global
sync logic into a log_sync() handler. However that's not efficient
enough because otherwise memory_global_dirty_log_sync() may do the
global sync N times, where N is the number of flat ranges in the
address space.

Make this new method be exclusive to log_sync().

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-2-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: d8f5f2e649259147e22bf8130996f5102a3eb5b9
      
https://github.com/qemu/qemu/commit/d8f5f2e649259147e22bf8130996f5102a3eb5b9
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M include/sysemu/kvm_int.h

  Log Message:
  -----------
  KVM: Use a big lock to replace per-kml slots_lock

Per-kml slots_lock will bring some trouble if we want to take all slots_lock of
all the KMLs, especially when we're in a context that we could have taken some
of the KML slots_lock, then we even need to figure out what we've taken and
what we need to take.

Make this simple by merging all KML slots_lock into a single slots lock.

Per-kml slots_lock isn't anything that helpful anyway - so far only x86 has two
address spaces (so, two slots_locks).  All the rest archs will be having one
address space always, which means there's actually one slots_lock so it will be
the same as before.

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-3-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 60182c016316029b3ce60174035584b41e747e43
      
https://github.com/qemu/qemu/commit/60182c016316029b3ce60174035584b41e747e43
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c

  Log Message:
  -----------
  KVM: Create the KVMSlot dirty bitmap on flag changes

Previously we have two places that will create the per KVMSlot dirty
bitmap:

  1. When a newly created KVMSlot has dirty logging enabled,
  2. When the first log_sync() happens for a memory slot.

The 2nd case is lazy-init, while the 1st case is not (which is a fix
of what the 2nd case missed).

To do explicit initialization of dirty bitmaps, what we're missing is
to create the dirty bitmap when the slot changed from not-dirty-track
to dirty-track.  Do that in kvm_slot_update_flags().

With that, we can safely remove the 2nd lazy-init.

This change will be needed for kvm dirty ring because kvm dirty ring
does not use the log_sync() interface at all.

Also move all the pre-checks into kvm_slot_init_dirty_bitmap().

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-4-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 8786de5d04389f916b0bdb15436da82027e0326f
      
https://github.com/qemu/qemu/commit/8786de5d04389f916b0bdb15436da82027e0326f
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M include/sysemu/kvm_int.h

  Log Message:
  -----------
  KVM: Provide helper to get kvm dirty log

Provide a helper kvm_slot_get_dirty_log() to make the function
kvm_physical_sync_dirty_bitmap() clearer.  We can even cache the as_id
into KVMSlot when it is created, so that we don't even need to pass it
down every time.

Since at it, remove return value of kvm_physical_sync_dirty_bitmap()
because it should never fail.

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-5-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 982f3f1bf4be5cd8dbe5929f6087c5887841d7b0
      
https://github.com/qemu/qemu/commit/982f3f1bf4be5cd8dbe5929f6087c5887841d7b0
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M include/sysemu/kvm_int.h

  Log Message:
  -----------
  KVM: Provide helper to sync dirty bitmap from slot to ramblock

kvm_physical_sync_dirty_bitmap() calculates the ramblock offset in an
awkward way from the MemoryRegionSection that passed in from the
caller.  The truth is for each KVMSlot the ramblock offset never
change for the lifecycle.  Cache the ramblock offset for each KVMSlot
into the structure when the KVMSlot is created.

With that, we can further simplify kvm_physical_sync_dirty_bitmap()
with a helper to sync KVMSlot dirty bitmap to the ramblock dirty
bitmap of a specific KVMSlot.

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-6-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: d5d7220922af91c56437b3a97db1561dce71f1a0
      
https://github.com/qemu/qemu/commit/d5d7220922af91c56437b3a97db1561dce71f1a0
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c

  Log Message:
  -----------
  KVM: Simplify dirty log sync in kvm_set_phys_mem

kvm_physical_sync_dirty_bitmap() on the whole section is inaccurate, because
the section can be a superset of the memslot that we're working on.  The result
is that if the section covers multiple kvm memslots, we could be doing the
synchronization for multiple times for each kvmslot in the section.

With the two helpers that we just introduced, it's very easy to do it right now
by calling the helpers.

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-7-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 37d20d06fb3c7b9593c1d5a9b806acecfc4cfe86
      
https://github.com/qemu/qemu/commit/37d20d06fb3c7b9593c1d5a9b806acecfc4cfe86
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M include/sysemu/kvm_int.h

  Log Message:
  -----------
  KVM: Cache kvm slot dirty bitmap size

Cache it too because we'll reference it more frequently in the future.

Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-8-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 5505a1f141e7ac0bbe8213fa978799d7d0e8a10e
      
https://github.com/qemu/qemu/commit/5505a1f141e7ac0bbe8213fa978799d7d0e8a10e
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M qemu-options.hx

  Log Message:
  -----------
  KVM: Add dirty-ring-size property

Add a parameter for dirty gfn count for dirty rings.  If zero, dirty ring is
disabled.  Otherwise dirty ring will be enabled with the per-vcpu gfn count as
specified.  If dirty ring cannot be enabled due to unsupported kernel or
illegal parameter, it'll fallback to dirty logging.

By default, dirty ring is not enabled (dirty-gfn-count default to 0).

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-9-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: e3b99a3d17157011d6b20425cc1cb64cb7f2e999
      
https://github.com/qemu/qemu/commit/e3b99a3d17157011d6b20425cc1cb64cb7f2e999
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c

  Log Message:
  -----------
  KVM: Disable manual dirty log when dirty ring enabled

KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2 is for KVM_CLEAR_DIRTY_LOG, which is only
useful for KVM_GET_DIRTY_LOG.  Skip enabling it for kvm dirty ring.

More importantly, KVM_DIRTY_LOG_INITIALLY_SET will not wr-protect all the pages
initially, which is against how kvm dirty ring is used - there's no way for kvm
dirty ring to re-protect a page before it's notified as being written first
with a GFN entry in the ring!  So when KVM_DIRTY_LOG_INITIALLY_SET is enabled
with dirty ring, we'll see silent data loss after migration.

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-10-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 9425d0baf3e9a656f54c554751f882d206120045
      
https://github.com/qemu/qemu/commit/9425d0baf3e9a656f54c554751f882d206120045
  Author: Peter Xu <peterx@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M accel/kvm/kvm-all.c
    M accel/kvm/trace-events
    M include/hw/core/cpu.h

  Log Message:
  -----------
  KVM: Dirty ring support

KVM dirty ring is a new interface to pass over dirty bits from kernel to the
userspace.  Instead of using a bitmap for each memory region, the dirty ring
contains an array of dirtied GPAs to fetch (in the form of offset in slots).
For each vcpu there will be one dirty ring that binds to it.

kvm_dirty_ring_reap() is the major function to collect dirty rings.  It can be
called either by a standalone reaper thread that runs in the background,
collecting dirty pages for the whole VM.  It can also be called directly by any
thread that has BQL taken.

Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20210506160549.130416-11-peterx@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: ba36c16421824668eed4fd46361a15a01e7109d2
      
https://github.com/qemu/qemu/commit/ba36c16421824668eed4fd46361a15a01e7109d2
  Author: Philippe Mathieu-Daudé <philmd@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M tests/qtest/fuzz/fuzz.c

  Log Message:
  -----------
  tests/qtest/fuzz: Fix build failure

On Fedora 32, using clang (version 10.0.1-3.fc32) we get:

  tests/qtest/fuzz/fuzz.c:237:5: error: implicit declaration of function 
'qemu_init' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
      qemu_init(result.we_wordc, result.we_wordv, NULL);
      ^

qemu_init() is declared in "sysemu/sysemu.h", include this
header to fix.

Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Message-Id: <20210513162008.3922223-1-philmd@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: dbddde143209195225c3708dc8ef53761ca6d96e
      
https://github.com/qemu/qemu/commit/dbddde143209195225c3708dc8ef53761ca6d96e
  Author: Katsuhiro Ueno <uenobk@gmail.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M meson.build

  Log Message:
  -----------
  meson: Set implicit_include_directories to false

Without this, libvixl cannot be compiled with macOS 11.3 SDK due to
include file name conflict (usr/include/c++/v1/version conflicts with
VERSION).

Signed-off-by: Katsuhiro Ueno <uenobk@gmail.com>
Message-Id: <CA+pCdY09+OQfXq3YmRNuQE59ACOq7Py2q4hqOwgq4PnepCXhTA@mail.gmail.com>
Tested-by: Alexander Graf <agraf@csgraf.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 02624c5d04b95e73a4d6a06f3f40b7608f9fbf0f
      
https://github.com/qemu/qemu/commit/02624c5d04b95e73a4d6a06f3f40b7608f9fbf0f
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    A include/qemu/qemu-options.h
    M os-posix.c
    M os-win32.c
    R qemu-options-wrapper.h
    R qemu-options.h
    M qemu-options.hx
    M softmmu/vl.c

  Log Message:
  -----------
  remove qemu-options* from root directory

These headers are also included from softmmu/vl.c, so they should be
in include/.  Remove qemu-options-wrapper.h, since elsewhere
we include "template" headers directly and #define the parameters in
the including file; move qemu-options.h to include/.

Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: dff1614b7aff6c0ea44897fc03554625f4165e9a
      
https://github.com/qemu/qemu/commit/dff1614b7aff6c0ea44897fc03554625f4165e9a
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M block/replication.c
    A include/block/replication.h
    M migration/colo.c
    M replication.c
    R replication.h
    M tests/unit/test-replication.c

  Log Message:
  -----------
  replication: move include out of root directory

The replication.h file is included from migration/colo.c and 
tests/unit/test-replication.c,
so it should be in include/.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: d1c7c7f4cd54ab185969caa8ecff1be239bd7785
      
https://github.com/qemu/qemu/commit/d1c7c7f4cd54ab185969caa8ecff1be239bd7785
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M softmmu/vl.c

  Log Message:
  -----------
  vl: allow not specifying size in -m when using -M memory-backend

Starting in QEMU 6.0's commit f5c9fcb82d ("vl: separate
qemu_create_machine", 2020-12-10), a function have_custom_ram_size()
replaced the return value of set_memory_options().

The purpose of the return value was to record the presence of
"-m size", and if it was not there, change the default RAM
size to the size of the memory backend passed with "-M
memory-backend".

With that commit, however, have_custom_ram_size() is now queried only
after set_memory_options has stored the fixed-up RAM size in QemuOpts for
"future use".  This was actually the only future use of the fixed-up RAM
size, so remove that code and fix the bug.

Cc: qemu-stable@nongnu.org
Fixes: f5c9fcb82d ("vl: separate qemu_create_machine", 2020-12-10)
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 940f52ed4cda9c3d10ace31b6ab21f57e53a041a
      
https://github.com/qemu/qemu/commit/940f52ed4cda9c3d10ace31b6ab21f57e53a041a
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M include/qemu/config-file.h
    M softmmu/vl.c
    M stubs/meson.build
    A stubs/module-opts.c
    M util/qemu-config.c

  Log Message:
  -----------
  qemu-config: load modules when instantiating option groups

Right now the SPICE module is special cased to be loaded when processing
of the -spice command line option.  However, the spice option group
can also be brought in via -readconfig, in which case the module is
not loaded.

Add a generic hook to load modules that provide a QemuOpts group,
and use it for the "spice" and "iscsi" groups.

Fixes: #194
Fixes: https://bugs.launchpad.net/qemu/+bug/1910696
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 976551ba504a3284f9ab9862d9434b422c6841a1
      
https://github.com/qemu/qemu/commit/976551ba504a3284f9ab9862d9434b422c6841a1
  Author: Paolo Bonzini <pbonzini@redhat.com>
  Date:   2021-05-18 (Tue, 18 May 2021)

  Changed paths:
    M block/file-posix.c
    M hw/scsi/scsi-generic.c

  Log Message:
  -----------
  scsi-generic: pass max_segments via max_iov field in BlockLimits

I/O to a disk via read/write is not limited by the number of segments allowed
by the host adapter; the kernel can split requests if needed, and the limit
imposed by the host adapter can be very low (256k or so) to avoid that SG_IO
returns EINVAL if memory is heavily fragmented.

Since this value is only interesting for SG_IO-based I/O, do not include
it in the max_transfer and only take it into account when patching the
block limits VPD page in the scsi-generic device.

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>


  Commit: 98e44d9953801bbda8e8ddfdb950e9d440a7e7bc
      
https://github.com/qemu/qemu/commit/98e44d9953801bbda8e8ddfdb950e9d440a7e7bc
  Author: Peter Maydell <peter.maydell@linaro.org>
  Date:   2021-05-20 (Thu, 20 May 2021)

  Changed paths:
    M Makefile
    M accel/kvm/kvm-all.c
    M accel/kvm/trace-events
    M block/file-posix.c
    M block/replication.c
    M configure
    M default-configs/devices/ppc64-softmmu.mak
    M hmp-commands.hx
    M hw/arm/Kconfig
    M hw/i386/Kconfig
    M hw/mem/Kconfig
    M hw/ppc/Kconfig
    M hw/scsi/scsi-generic.c
    A include/block/replication.h
    M include/exec/memory.h
    M include/hw/core/cpu.h
    M include/qemu/config-file.h
    A include/qemu/qemu-options.h
    M include/sysemu/kvm_int.h
    M meson
    M meson.build
    M migration/colo.c
    M os-posix.c
    M os-win32.c
    M qapi/qom.json
    R qemu-options-wrapper.h
    R qemu-options.h
    M qemu-options.hx
    M replication.c
    R replication.h
    M softmmu/memory.c
    M softmmu/qtest.c
    M softmmu/vl.c
    M stubs/meson.build
    A stubs/module-opts.c
    M target/i386/cpu.c
    M target/i386/cpu.h
    M tests/qtest/fuzz/fuzz.c
    M tests/unit/test-replication.c
    M util/qemu-config.c

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

* submodule cleanups (Philippe, myself)
* tiny step towards a usable preconfig mode (myself)
* bump Meson submodule (myself)
* Kconfig and LOCK_GUARD cleanups (philippe)
* new x86 CPUID feature (Yang Zhong)
* "-object qtest" support (myself)
* Dirty ring support for KVM (Peter)
* Fixes for 6.0 command line parsing breakage (myself)
* Fix for macOS 11.3 SDK (Katsuhiro)
* Fix for scsi-generic handling (myself)

# gpg: Signature made Tue 18 May 2021 16:51:28 BST
# gpg:                using RSA key F13338574B662389866C7682BFFBD25F78C7AE83
# gpg:                issuer "pbonzini@redhat.com"
# gpg: Good signature from "Paolo Bonzini <bonzini@gnu.org>" [full]
# gpg:                 aka "Paolo Bonzini <pbonzini@redhat.com>" [full]
# 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-gitlab/tags/tags/for-upstream-v2: (26 commits)
  scsi-generic: pass max_segments via max_iov field in BlockLimits
  qemu-config: load modules when instantiating option groups
  vl: allow not specifying size in -m when using -M memory-backend
  replication: move include out of root directory
  remove qemu-options* from root directory
  meson: Set implicit_include_directories to false
  tests/qtest/fuzz: Fix build failure
  KVM: Dirty ring support
  KVM: Disable manual dirty log when dirty ring enabled
  KVM: Add dirty-ring-size property
  KVM: Cache kvm slot dirty bitmap size
  KVM: Simplify dirty log sync in kvm_set_phys_mem
  KVM: Provide helper to sync dirty bitmap from slot to ramblock
  KVM: Provide helper to get kvm dirty log
  KVM: Create the KVMSlot dirty bitmap on flag changes
  KVM: Use a big lock to replace per-kml slots_lock
  memory: Introduce log_sync_global() to memory listener
  KVM: do not allow setting properties at runtime
  qtest: add a QOM object for qtest
  object: add more commands to preconfig mode
  ...

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>


Compare: https://github.com/qemu/qemu/compare/be05216b01d2...98e44d995380