qemu-commits
[Top][All Lists]
Advanced

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

[Qemu-commits] [qemu/qemu] c260da: seabios: update submodule to git snap


From: Alex Bennée
Subject: [Qemu-commits] [qemu/qemu] c260da: seabios: update submodule to git snapshot
Date: Mon, 18 Sep 2023 05:04:35 -0700

  Branch: refs/heads/staging
  Home:   https://github.com/qemu/qemu
  Commit: c260daec1018ace89bf8b8464cb6031dfdbfd76e
      
https://github.com/qemu/qemu/commit/c260daec1018ace89bf8b8464cb6031dfdbfd76e
  Author: Gerd Hoffmann <kraxel@redhat.com>
  Date:   2023-09-11 (Mon, 11 Sep 2023)

  Changed paths:
    M roms/seabios

  Log Message:
  -----------
  seabios: update submodule to git snapshot

git shortlog
------------

Gerd Hoffmann (7):
      disable array bounds warning
      better kvm detection
      detect physical address space size
      move 64bit pci window to end of address space
      be less conservative with the 64bit pci io window
      qemu: log reservations in fw_cfg e820 table
      check for e820 conflict

José Martínez (1):
      Fix high memory zone initialization in CSM mode

Lukas Stockner via SeaBIOS (1):
      virtio-blk: Fix integer overflow for large max IO sizes

Mark Cave-Ayland (3):
      esp-scsi: flush FIFO before sending SCSI command
      esp-scsi: check for INTR_BS/INTR_FC instead of STAT_TC for command 
completion
      esp-scsi: handle non-DMA SCSI commands with no data phase

Niklas Cassel via SeaBIOS (1):
      ahci: handle TFES irq correctly

Tony Titus via SeaBIOS (1):
      Increase BUILD_MAX_E820 to 128

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>


  Commit: 8991e6baa51feb6e294bb95938921b5162b6cf6d
      
https://github.com/qemu/qemu/commit/8991e6baa51feb6e294bb95938921b5162b6cf6d
  Author: Gerd Hoffmann <kraxel@redhat.com>
  Date:   2023-09-11 (Mon, 11 Sep 2023)

  Changed paths:
    M roms/config.seabios-128k

  Log Message:
  -----------
  seabios: turn off CONFIG_APMBIOS for 128k build

Needed to make the build fit into 128k.

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>


  Commit: a14c30fc3d38d569415259a2d877c36a0b8de058
      
https://github.com/qemu/qemu/commit/a14c30fc3d38d569415259a2d877c36a0b8de058
  Author: Gerd Hoffmann <kraxel@redhat.com>
  Date:   2023-09-11 (Mon, 11 Sep 2023)

  Changed paths:
    M pc-bios/bios-256k.bin
    M pc-bios/bios-microvm.bin
    M pc-bios/bios.bin
    M pc-bios/vgabios-ati.bin
    M pc-bios/vgabios-bochs-display.bin
    M pc-bios/vgabios-cirrus.bin
    M pc-bios/vgabios-qxl.bin
    M pc-bios/vgabios-ramfb.bin
    M pc-bios/vgabios-stdvga.bin
    M pc-bios/vgabios-virtio.bin
    M pc-bios/vgabios-vmware.bin
    M pc-bios/vgabios.bin

  Log Message:
  -----------
  seabios: update binaries to git snapshot

Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>


  Commit: e703c83797e0056d86d7d81fb4884e71eb620cc8
      
https://github.com/qemu/qemu/commit/e703c83797e0056d86d7d81fb4884e71eb620cc8
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Remove unused BlockReopenQueueEntry.perms_checked

This field has been unused since commit 72373e40fbc ('block:
bdrv_reopen_multiple: refresh permissions on updated graph').
Remove it.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-2-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 266bda4f2f31423f40374c9be861746164442798
      
https://github.com/qemu/qemu/commit/266bda4f2f31423f40374c9be861746164442798
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block/preallocate.c

  Log Message:
  -----------
  preallocate: Factor out preallocate_truncate_to_real_size()

It's essentially the same code in preallocate_check_perm() and
preallocate_close(), except that the latter ignores errors.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-3-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: c9374ca6212fbc8860bdfb73a77e181200567d84
      
https://github.com/qemu/qemu/commit/c9374ca6212fbc8860bdfb73a77e181200567d84
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block/preallocate.c

  Log Message:
  -----------
  preallocate: Don't poll during permission updates

When the permission related BlockDriver callbacks are called, we are in
the middle of an operation traversing the block graph. Polling in such a
place is a very bad idea because the graph could change in unexpected
ways. In the future, callers will also hold the graph lock, which is
likely to turn polling into a deadlock.

So we need to get rid of calls to functions like bdrv_getlength() or
bdrv_truncate() there as these functions poll internally. They are
currently used so that when no parent has write/resize permissions on
the image any more, the preallocate filter drops the extra preallocated
area in the image file and gives up write/resize permissions itself.

In order to achieve this without polling in .bdrv_check_perm, don't
immediately truncate the image, but only schedule a BH to do so. The
filter keeps the write/resize permissions a bit longer now until the BH
has executed.

There is one case in which delaying doesn't work: Reopening the image
read-only. In this case, bs->file will likely be reopened read-only,
too, so keeping write permissions a bit longer on it doesn't work. But
we can already cover this case in preallocate_reopen_prepare() and not
rely on the permission updates for it.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-4-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: cfc21271ef68aa782677b2f34a48047f39aad230
      
https://github.com/qemu/qemu/commit/cfc21271ef68aa782677b2f34a48047f39aad230
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M tests/unit/test-bdrv-drain.c
    M tests/unit/test-bdrv-graph-mod.c
    M tests/unit/test-block-iothread.c

  Log Message:
  -----------
  block: Take AioContext lock for bdrv_append() more consistently

The documentation for bdrv_append() says that the caller must hold the
AioContext lock for bs_top. Change all callers to actually adhere to the
contract.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-5-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: a69b8a6ca50a2c7f2f683a767a0e574c1f102eb9
      
https://github.com/qemu/qemu/commit/a69b8a6ca50a2c7f2f683a767a0e574c1f102eb9
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/graph-lock.c
    M include/block/block-global-state.h
    M tests/qemu-iotests/051.pc.out

  Log Message:
  -----------
  block: Introduce bdrv_schedule_unref()

bdrv_unref() is called by a lot of places that need to hold the graph
lock (it naturally happens in the context of operations that change the
graph). However, bdrv_unref() takes the graph writer lock internally, so
it can't actually be called while already holding a graph lock without
causing a deadlock.

bdrv_unref() also can't just become GRAPH_WRLOCK because it drains the
node before closing it, and draining requires that the graph is
unlocked.

The solution is to defer deleting the node until we don't hold the lock
any more and draining is possible again.

Note that keeping images open for longer than necessary can create
problems, too: You can't open an image again before it is really closed
(if image locking didn't prevent it, it would cause corruption).
Reopening an image immediately happens at least during bdrv_open() and
bdrv_co_create().

In order to solve this problem, make sure to run the deferred unref in
bdrv_graph_wrunlock(), i.e. the first possible place where we can drain
again. This is also why bdrv_schedule_unref() is marked GRAPH_WRLOCK.

The output of iotest 051 is updated because the additional polling
changes the order of HMP output, resulting in a new "(qemu)" prompt in
the test output that was previously on a separate line and filtered out.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Message-ID: <20230911094620.45040-6-kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: d2d36cb335cd5e82580763fd9f965236b4aabeec
      
https://github.com/qemu/qemu/commit/d2d36cb335cd5e82580763fd9f965236b4aabeec
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M include/block/block-common.h
    M scripts/block-coroutine-wrapper.py

  Log Message:
  -----------
  block-coroutine-wrapper: Add no_co_wrapper_bdrv_wrlock functions

Add a new wrapper type for GRAPH_WRLOCK functions that should be called
from coroutine context.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-7-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: c8c02ade086e8558ef4913d53a822519b1e06fbb
      
https://github.com/qemu/qemu/commit/c8c02ade086e8558ef4913d53a822519b1e06fbb
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M scripts/block-coroutine-wrapper.py

  Log Message:
  -----------
  block-coroutine-wrapper: Allow arbitrary parameter names

Don't assume specific parameter names like 'bs' or 'blk' in the
generated code, but use the actual name.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-8-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: d1df8b7ce1d0b327397bb5b2bb1883e197ff2b82
      
https://github.com/qemu/qemu/commit/d1df8b7ce1d0b327397bb5b2bb1883e197ff2b82
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Mark bdrv_replace_child_noperm() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_replace_child_noperm(). These callers will
typically already hold the graph lock once the locking work is
completed, which means that they can't call functions that take it
internally.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-9-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: ae2e30d85e85f44a239c3979561687a33692412c
      
https://github.com/qemu/qemu/commit/ae2e30d85e85f44a239c3979561687a33692412c
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Mark bdrv_replace_child_tran() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_replace_child_tran(). These callers will
typically already hold the graph lock once the locking work is
completed, which means that they can't call functions that take it
internally.

While a graph lock is held, polling is not allowed. Therefore draining
the necessary nodes can no longer be done in bdrv_remove_child() and
bdrv_replace_node_noperm(), but the callers must already make sure that
they are drained.

Note that the transaction callbacks still take the lock internally, so
tran_finalize() must be called without the lock held. This is because
bdrv_append() also calls bdrv_attach_child_noperm(), which currently
requires to be called unlocked. Once it changes, the transaction
callbacks can be changed, too.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-10-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 9fe2a9775f2663bf66bc6bdce40ed24f54a03562
      
https://github.com/qemu/qemu/commit/9fe2a9775f2663bf66bc6bdce40ed24f54a03562
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/stream.c

  Log Message:
  -----------
  block: Mark bdrv_attach_child_common() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_attach_child_common(). These callers will
typically already hold the graph lock once the locking work is
completed, which means that they can't call functions that take it
internally.

Note that the transaction callbacks still take the lock internally, so
tran_finalize() must be called without the lock held. This is because
bdrv_append() also calls bdrv_replace_node_noperm(), which currently
requires the transaction callbacks to be called unlocked. In the next
step, both of them can be switched to locked tran_finalize() calls
together.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-11-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: efca2ef1aef58b88fd0baf7bfd4eeaab7e51a697
      
https://github.com/qemu/qemu/commit/efca2ef1aef58b88fd0baf7bfd4eeaab7e51a697
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Call transaction callbacks with lock held

In previous patches, we changed some transactionable functions to be
marked as GRAPH_WRLOCK, but required that tran_finalize() is still
called without the lock. This was because all callbacks that can be in
the same transaction need to follow the same convention.

Now that we don't have conflicting requirements any more, we can switch
all of the transaction callbacks to be declared GRAPH_WRLOCK, too, and
call tran_finalize() with the lock held.

Document for each of these transactionable functions that the lock needs
to be held when completing the transaction, and make sure that all
callers down to the place where the transaction is finalised actually
have the writer lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-12-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: c363f18330d0108303d1309572250243956c8d8f
      
https://github.com/qemu/qemu/commit/c363f18330d0108303d1309572250243956c8d8f
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/quorum.c
    M block/replication.c
    M include/block/block-global-state.h
    M tests/unit/test-bdrv-drain.c
    M tests/unit/test-bdrv-graph-mod.c

  Log Message:
  -----------
  block: Mark bdrv_attach_child() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_attach_child_common(). These callers will
typically already hold the graph lock once the locking work is
completed, which means that they can't call functions that take it
internally.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-13-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: f0c088cebf6abf969c961b795a2579a7193c434a
      
https://github.com/qemu/qemu/commit/f0c088cebf6abf969c961b795a2579a7193c434a
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/block-backend.c
    M block/crypto.c
    M block/mirror.c
    M block/vmdk.c
    M include/block/block_int-common.h
    M include/block/block_int-global-state.h
    M include/sysemu/block-backend-global-state.h
    M tests/unit/test-bdrv-graph-mod.c

  Log Message:
  -----------
  block: Mark bdrv_parent_perms_conflict() and callers GRAPH_RDLOCK

The function reads the parents list, so it needs to hold the graph lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-14-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: d6a54732abc639761100f7f3cd5425185c4a4330
      
https://github.com/qemu/qemu/commit/d6a54732abc639761100f7f3cd5425185c4a4330
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M blockdev.c
    M include/block/block_int-common.h
    M include/block/block_int-global-state.h

  Log Message:
  -----------
  block: Mark bdrv_get_cumulative_perm() and callers GRAPH_RDLOCK

The function reads the parents list, so it needs to hold the graph lock.

This happens to result in BlockDriver.bdrv_set_perm() to be called with
the graph lock held. For consistency, make it the same for all of the
BlockDriver callbacks for updating permissions and annotate the function
pointers with GRAPH_RDLOCK_PTR.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-15-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 21a32c8eb65bb4ff8733e93a2a5a4f38a623fd4e
      
https://github.com/qemu/qemu/commit/21a32c8eb65bb4ff8733e93a2a5a4f38a623fd4e
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/copy-before-write.c
    M include/block/block_int-common.h

  Log Message:
  -----------
  block: Mark bdrv_child_perm() GRAPH_RDLOCK

This adds GRAPH_RDLOCK annotations to declare that callers of
bdrv_child_perm() need to hold a reader lock for the graph because
some implementations access the children list of a node.

The callers of bdrv_child_perm() conveniently already hold the lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-16-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 4dc516f9a36484fe344d02c95d727c47da156851
      
https://github.com/qemu/qemu/commit/4dc516f9a36484fe344d02c95d727c47da156851
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Mark bdrv_parent_cb_change_media() GRAPH_RDLOCK

The function reads the parents list, so it needs to hold the graph lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-17-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 20069b600576db171c295ca33dc0a7de75789b2a
      
https://github.com/qemu/qemu/commit/20069b600576db171c295ca33dc0a7de75789b2a
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Take graph rdlock in bdrv_drop_intermediate()

The function reads the parents list, so it needs to hold the graph lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Message-ID: <20230911094620.45040-18-kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 1acdef2a3078f04772faaefe38ff463605822b11
      
https://github.com/qemu/qemu/commit/1acdef2a3078f04772faaefe38ff463605822b11
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c

  Log Message:
  -----------
  block: Take graph rdlock in bdrv_change_aio_context()

The function reads the parents list, so it needs to hold the graph lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Message-ID: <20230911094620.45040-19-kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: fc9b4db2874cd5249a159b542f2de8e749add4c8
      
https://github.com/qemu/qemu/commit/fc9b4db2874cd5249a159b542f2de8e749add4c8
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/block-backend.c
    M blockjob.c
    M include/block/block_int-global-state.h

  Log Message:
  -----------
  block: Mark bdrv_root_unref_child() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_root_unref_child(). These callers will
typically already hold the graph lock once the locking work is
completed, which means that they can't call functions that take it
internally.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-20-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: b7a0b687cb180fc72d4861c538c9bf62a2c347ab
      
https://github.com/qemu/qemu/commit/b7a0b687cb180fc72d4861c538c9bf62a2c347ab
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block.c
    M block/blklogwrites.c
    M block/blkverify.c
    M block/qcow2.c
    M block/quorum.c
    M block/replication.c
    M block/snapshot.c
    M block/vmdk.c
    M include/block/block-global-state.h
    M tests/unit/test-bdrv-drain.c

  Log Message:
  -----------
  block: Mark bdrv_unref_child() GRAPH_WRLOCK

Instead of taking the writer lock internally, require callers to already
hold it when calling bdrv_unref_child(). These callers will typically
already hold the graph lock once the locking work is completed, which
means that they can't call functions that take it internally.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-21-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: b09cd2518542b6f941f9eea2a4cf58b1644a12c3
      
https://github.com/qemu/qemu/commit/b09cd2518542b6f941f9eea2a4cf58b1644a12c3
  Author: Kevin Wolf <kwolf@redhat.com>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block/quorum.c
    M blockdev.c
    M include/block/block-global-state.h
    M include/block/block_int-common.h

  Log Message:
  -----------
  block: Mark bdrv_add/del_child() and caller GRAPH_WRLOCK

The functions read the parents list in the generic block layer, so we
need to hold the graph lock already there. The BlockDriver
implementations actually modify the graph, so it has to be a writer
lock.

Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230911094620.45040-22-kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: f16f654288dc3a02bc260896a1082672787110cd
      
https://github.com/qemu/qemu/commit/f16f654288dc3a02bc260896a1082672787110cd
  Author: Andrey Drobyshev via <qemu-block@nongnu.org>
  Date:   2023-09-14 (Thu, 14 Sep 2023)

  Changed paths:
    M block/qcow.c
    M block/qcow2.c
    M block/vmdk.c
    M include/block/block-common.h

  Log Message:
  -----------
  block: add BDRV_BLOCK_COMPRESSED flag for bdrv_block_status()

Functions qcow2_get_host_offset(), get_cluster_offset(),
vmdk_co_block_status() explicitly report compressed cluster types when data
is compressed.  However, this information is never passed further.  Let's
make use of it by adding new BDRV_BLOCK_COMPRESSED flag for
bdrv_block_status(), so that caller may know that the data range is
compressed.  In particular, we're going to use this flag to tweak
"qemu-img map" output.

This new flag is only being utilized by qcow, qcow2 and vmdk formats, as only
those support compression.

Reviewed-by: Denis V. Lunev <den@openvz.org>
Reviewed-by: Hanna Czenczek <hreitz@redhat.com>
Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Message-ID: <20230907210226.953821-2-andrey.drobyshev@virtuozzo.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: b769769f0280eee924c26c2d1e213c4d996b9b93
      
https://github.com/qemu/qemu/commit/b769769f0280eee924c26c2d1e213c4d996b9b93
  Author: Andrey Drobyshev via <qemu-block@nongnu.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M qapi/block-core.json
    M qemu-img.c
    M tests/qemu-iotests/122.out
    M tests/qemu-iotests/146.out
    M tests/qemu-iotests/154.out
    M tests/qemu-iotests/179.out
    M tests/qemu-iotests/209.out
    M tests/qemu-iotests/221.out
    M tests/qemu-iotests/223.out
    M tests/qemu-iotests/241.out
    M tests/qemu-iotests/244.out
    M tests/qemu-iotests/252.out
    M tests/qemu-iotests/253.out
    M tests/qemu-iotests/274.out
    M tests/qemu-iotests/tests/nbd-qemu-allocation.out
    M tests/qemu-iotests/tests/qemu-img-bitmaps.out

  Log Message:
  -----------
  qemu-img: map: report compressed data blocks

Right now "qemu-img map" reports compressed blocks as containing data
but having no host offset.  This is not very informative.  Instead,
let's add another boolean field named "compressed" in case JSON output
mode is specified.  This is achieved by utilizing new allocation status
flag BDRV_BLOCK_COMPRESSED for bdrv_block_status().

Also update the expected qemu-iotests outputs to contain the new field.

Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Message-ID: <20230907210226.953821-3-andrey.drobyshev@virtuozzo.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 81e74f2a3ce808e89b1d9ecff8b30d9b7e3c4b41
      
https://github.com/qemu/qemu/commit/81e74f2a3ce808e89b1d9ecff8b30d9b7e3c4b41
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M block/block-backend.c
    M block/io.c
    M hw/nvme/ctrl.c
    M include/block/aio.h
    M include/block/block-global-state.h
    M include/block/block-io.h
    M softmmu/dma-helpers.c
    M util/thread-pool.c

  Log Message:
  -----------
  block: remove AIOCBInfo->get_aio_context()

The synchronous bdrv_aio_cancel() function needs the acb's AioContext so
it can call aio_poll() to wait for cancellation.

It turns out that all users run under the BQL in the main AioContext, so
this callback is not needed.

Remove the callback, mark bdrv_aio_cancel() GLOBAL_STATE_CODE just like
its blk_aio_cancel() caller, and poll the main loop AioContext.

The purpose of this cleanup is to identify bdrv_aio_cancel() as an API
that does not work with the multi-queue block layer.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-2-stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Klaus Jensen <k.jensen@samsung.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 7b4f0012abd1c8581616b18864e02b7c4b7230ce
      
https://github.com/qemu/qemu/commit/7b4f0012abd1c8581616b18864e02b7c4b7230ce
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/unit/test-bdrv-drain.c

  Log Message:
  -----------
  test-bdrv-drain: avoid race with BH in IOThread drain test

This patch fixes a race condition in test-bdrv-drain that is difficult
to reproduce. test-bdrv-drain sometimes fails without an error message
on the block pull request sent by Kevin Wolf on Sep 4, 2023. I was able
to reproduce it locally and found that "block-backend: process I/O in
the current AioContext" (in this patch series) is the first commit where
it reproduces.

I do not know why "block-backend: process I/O in the current AioContext"
exposes this bug. It might be related to the fact that the test's preadv
request runs in the main thread instead of IOThread a after my commit.
That might simply change the timing of the test.

Now on to the race condition in test-bdrv-drain. The main thread
schedules a BH in IOThread a and then drains the BDS:

  aio_bh_schedule_oneshot(ctx_a, test_iothread_main_thread_bh, &data);

  /* The request is running on the IOThread a. Draining its block device
   * will make sure that it has completed as far as the BDS is concerned,
   * but the drain in this thread can continue immediately after
   * bdrv_dec_in_flight() and aio_ret might be assigned only slightly
   * later. */
  do_drain_begin(drain_type, bs);

If the BH completes before do_drain_begin() then there is nothing to
worry about.

If the BH invokes bdrv_flush() before do_drain_begin(), then
do_drain_begin() waits for it to complete.

The problematic case is when do_drain_begin() runs before the BH enters
bdrv_flush(). Then do_drain_begin() misses the BH and the drain
mechanism has failed in quiescing I/O.

Fix this by incrementing the in_flight counter so that do_drain_begin()
waits for test_iothread_main_thread_bh().

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-3-stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 4ccdef69f752a6691e18d5111758c477e58a1045
      
https://github.com/qemu/qemu/commit/4ccdef69f752a6691e18d5111758c477e58a1045
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M block/block-backend.c

  Log Message:
  -----------
  block-backend: process I/O in the current AioContext

Switch blk_aio_*() APIs over to multi-queue by using
qemu_get_current_aio_context() instead of blk_get_aio_context(). This
change will allow devices to process I/O in multiple IOThreads in the
future.

I audited existing blk_aio_*() callers:
- migration/block.c: blk_mig_lock() protects the data accessed by the
  completion callback.
- The remaining emulated devices and exports run with
  qemu_get_aio_context() == blk_get_aio_context().

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-4-stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 6daef34f06e7b48a71f803d69990a04f7bba26b6
      
https://github.com/qemu/qemu/commit/6daef34f06e7b48a71f803d69990a04f7bba26b6
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M block/block-backend.c

  Log Message:
  -----------
  block-backend: process zoned requests in the current AioContext

Process zoned requests in the current thread's AioContext instead of in
the BlockBackend's AioContext.

There is no need to use the BlockBackend's AioContext thanks to CoMutex
bs->wps->colock, which protects zone metadata.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-5-stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 5d96864b73225ee61b0dad7e928f0cddf14270fc
      
https://github.com/qemu/qemu/commit/5d96864b73225ee61b0dad7e928f0cddf14270fc
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M scripts/block-coroutine-wrapper.py

  Log Message:
  -----------
  block-coroutine-wrapper: use qemu_get_current_aio_context()

Use qemu_get_current_aio_context() in mixed wrappers and coroutine
wrappers so that code runs in the caller's AioContext instead of moving
to the BlockDriverState's AioContext. This change is necessary for the
multi-queue block layer where any thread can call into the block layer.

Most wrappers are IO_CODE where it's safe to use the current AioContext
nowadays. BlockDrivers and the core block layer use their own locks and
no longer depend on the AioContext lock for thread-safety.

The bdrv_create() wrapper invokes GLOBAL_STATE code. Using the current
AioContext is safe because this code is only called with the BQL held
from the main loop thread.

The output of qemu-iotests 051 is sensitive to event loop activity.
Update the output because the monitor BH runs at a different time,
causing prompts to be printed differently in the output.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20230912231037.826804-6-stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>


  Commit: 07f348d77c35b6ff1f99075e20bffbf67e772d8b
      
https://github.com/qemu/qemu/commit/07f348d77c35b6ff1f99075e20bffbf67e772d8b
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    A crypto/clmul.c
    M crypto/meson.build
    A include/crypto/clmul.h

  Log Message:
  -----------
  crypto: Add generic 8-bit carry-less multiply routines

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 8e3da4c716ad6251e93972bf84428569737a913f
      
https://github.com/qemu/qemu/commit/8e3da4c716ad6251e93972bf84428569737a913f
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/arm/tcg/mve_helper.c
    M target/arm/tcg/vec_helper.c
    M target/arm/tcg/vec_internal.h

  Log Message:
  -----------
  target/arm: Use clmul_8* routines

Use generic routines for 8-bit carry-less multiply.
Remove our local version of pmull_h.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 2d8bc6815e9a1c81f0aa0a1365c4d9a1e0cb0a81
      
https://github.com/qemu/qemu/commit/2d8bc6815e9a1c81f0aa0a1365c4d9a1e0cb0a81
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/s390x/tcg/vec_int_helper.c

  Log Message:
  -----------
  target/s390x: Use clmul_8* routines

Use generic routines for 8-bit carry-less multiply.
Remove our local version of galois_multiply8.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: cec4090d9487be9afe937b055e02a82c33e53320
      
https://github.com/qemu/qemu/commit/cec4090d9487be9afe937b055e02a82c33e53320
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/ppc/int_helper.c

  Log Message:
  -----------
  target/ppc: Use clmul_8* routines

Use generic routines for 8-bit carry-less multiply.

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: cf1b2cab835f816915c8a170ec783922bc4e56a3
      
https://github.com/qemu/qemu/commit/cf1b2cab835f816915c8a170ec783922bc4e56a3
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M crypto/clmul.c
    M include/crypto/clmul.h

  Log Message:
  -----------
  crypto: Add generic 16-bit carry-less multiply routines

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: c6f0dcb1fdee2b1c2af15cea75bee98327308a8e
      
https://github.com/qemu/qemu/commit/c6f0dcb1fdee2b1c2af15cea75bee98327308a8e
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/arm/tcg/mve_helper.c
    M target/arm/tcg/vec_helper.c
    M target/arm/tcg/vec_internal.h

  Log Message:
  -----------
  target/arm: Use clmul_16* routines

Use generic routines for 16-bit carry-less multiply.
Remove our local version of pmull_w.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 25c304e93612b5a0ad75c55d43d596b6d3271aad
      
https://github.com/qemu/qemu/commit/25c304e93612b5a0ad75c55d43d596b6d3271aad
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/s390x/tcg/vec_int_helper.c

  Log Message:
  -----------
  target/s390x: Use clmul_16* routines

Use generic routines for 16-bit carry-less multiply.
Remove our local version of galois_multiply16.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: a2c67342eed42f181aa123803bc246b8fad7d1d9
      
https://github.com/qemu/qemu/commit/a2c67342eed42f181aa123803bc246b8fad7d1d9
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/ppc/int_helper.c

  Log Message:
  -----------
  target/ppc: Use clmul_16* routines

Use generic routines for 16-bit carry-less multiply.

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 9a65a570fab1bf2e907d593631a6b588a821d365
      
https://github.com/qemu/qemu/commit/9a65a570fab1bf2e907d593631a6b588a821d365
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M crypto/clmul.c
    M include/crypto/clmul.h

  Log Message:
  -----------
  crypto: Add generic 32-bit carry-less multiply routines

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: bae25f648e3cbf7755c74aef2278be7332190e53
      
https://github.com/qemu/qemu/commit/bae25f648e3cbf7755c74aef2278be7332190e53
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/arm/tcg/vec_helper.c

  Log Message:
  -----------
  target/arm: Use clmul_32* routines

Use generic routines for 32-bit carry-less multiply.
Remove our local version of pmull_d.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 653aab27ba9610e3d3e047d1475765bd01f6fc14
      
https://github.com/qemu/qemu/commit/653aab27ba9610e3d3e047d1475765bd01f6fc14
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/s390x/tcg/vec_int_helper.c

  Log Message:
  -----------
  target/s390x: Use clmul_32* routines

Use generic routines for 32-bit carry-less multiply.
Remove our local version of galois_multiply32.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: f56d3c1a140267ae88874d755fa2f24cb71a1572
      
https://github.com/qemu/qemu/commit/f56d3c1a140267ae88874d755fa2f24cb71a1572
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/ppc/int_helper.c

  Log Message:
  -----------
  target/ppc: Use clmul_32* routines

Use generic routines for 32-bit carry-less multiply.

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 00f463b38aa7cfca0bc65e3af7f2c49e1b9da690
      
https://github.com/qemu/qemu/commit/00f463b38aa7cfca0bc65e3af7f2c49e1b9da690
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M crypto/clmul.c
    A host/include/generic/host/crypto/clmul.h
    M include/crypto/clmul.h

  Log Message:
  -----------
  crypto: Add generic 64-bit carry-less multiply routine

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: a50cfdf0be23e4d3ef52d1beb5e206b7be2a80f2
      
https://github.com/qemu/qemu/commit/a50cfdf0be23e4d3ef52d1beb5e206b7be2a80f2
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/arm/tcg/vec_helper.c

  Log Message:
  -----------
  target/arm: Use clmul_64

Use generic routine for 64-bit carry-less multiply.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 7fcb505455aff817fe8984494b83e657f0f2e02b
      
https://github.com/qemu/qemu/commit/7fcb505455aff817fe8984494b83e657f0f2e02b
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/i386/ops_sse.h

  Log Message:
  -----------
  target/i386: Use clmul_64

Use generic routine for 64-bit carry-less multiply.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: ef73fe7cf1cedfb11b77e79d65638645ebd1cbc5
      
https://github.com/qemu/qemu/commit/ef73fe7cf1cedfb11b77e79d65638645ebd1cbc5
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/s390x/tcg/vec_int_helper.c

  Log Message:
  -----------
  target/s390x: Use clmul_64

Use the generic routine for 64-bit carry-less multiply.
Remove our local version of galois_multiply64.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 7bdbf233d9636a4bc73a2513b5e1a83a388626cf
      
https://github.com/qemu/qemu/commit/7bdbf233d9636a4bc73a2513b5e1a83a388626cf
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M target/ppc/int_helper.c

  Log Message:
  -----------
  target/ppc: Use clmul_64

Use generic routine for 64-bit carry-less multiply.

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: d6493dbb46b4b7be13a39425b5a1e523e72f5a68
      
https://github.com/qemu/qemu/commit/d6493dbb46b4b7be13a39425b5a1e523e72f5a68
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M host/include/i386/host/cpuinfo.h
    A host/include/i386/host/crypto/clmul.h
    A host/include/x86_64/host/crypto/clmul.h
    M include/qemu/cpuid.h
    M util/cpuinfo-i386.c

  Log Message:
  -----------
  host/include/i386: Implement clmul.h

Detect PCLMUL in cpuinfo; implement the accel hook.

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: 055c99015a4ec3c608d0260592368adc604429ea
      
https://github.com/qemu/qemu/commit/055c99015a4ec3c608d0260592368adc604429ea
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M host/include/aarch64/host/cpuinfo.h
    A host/include/aarch64/host/crypto/clmul.h
    M util/cpuinfo-aarch64.c

  Log Message:
  -----------
  host/include/aarch64: Implement clmul.h

Detect PMULL in cpuinfo; implement the accel hook.

Acked-by: Ard Biesheuvel <ardb@kernel.org>
Tested-by: Ard Biesheuvel <ardb@kernel.org>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Richard Henderson <richard.henderson@linaro.org>


  Commit: a1979aae0f5b27b85a2696fbfc5b2cdff7f417d9
      
https://github.com/qemu/qemu/commit/a1979aae0f5b27b85a2696fbfc5b2cdff7f417d9
  Author: Alex Bennée <alex.bennee@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/docker/dockerfiles/debian-amd64-cross.docker
    M tests/docker/dockerfiles/debian-amd64.docker
    M tests/docker/dockerfiles/debian-arm64-cross.docker
    M tests/docker/dockerfiles/debian-armel-cross.docker
    M tests/docker/dockerfiles/debian-armhf-cross.docker
    M tests/docker/dockerfiles/debian-ppc64el-cross.docker
    M tests/docker/dockerfiles/debian-s390x-cross.docker
    M tests/docker/dockerfiles/ubuntu2004.docker
    M tests/docker/dockerfiles/ubuntu2204.docker
    M tests/lcitool/libvirt-ci
    M tests/lcitool/refresh

  Log Message:
  -----------
  tests: update Debian images to Bookworm

Bookworm has been out a while now. Time to update our containers to
the current stable. This requires the latest lcitool repo so update
the sub-module too.

For some reason the MIPs containers won't build so skip those for now.

Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-2-alex.bennee@linaro.org>


  Commit: 2e41d635a33616abb8d56a32a71b2d306cafef55
      
https://github.com/qemu/qemu/commit/2e41d635a33616abb8d56a32a71b2d306cafef55
  Author: Alex Bennée <alex.bennee@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M .gitlab-ci.d/base.yml

  Log Message:
  -----------
  gitlab: fix typo/spelling in comments

Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-3-alex.bennee@linaro.org>


  Commit: e7def7861815973a1f91606b4f3f609e28ed938c
      
https://github.com/qemu/qemu/commit/e7def7861815973a1f91606b4f3f609e28ed938c
  Author: Richard Henderson <richard.henderson@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/docker/dockerfiles/debian-loongarch-cross.docker

  Log Message:
  -----------
  tests/docker: Update docker-loongarch-cross toolchain

Update from clfs 5.0 to clfs 8.1, which includes updates
to binutils 2.41, gcc 13.2, and glibc 2.38.

See https://github.com/loongson/build-tools

Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Song Gao <gaosong@loongson.cn>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230829220228.928506-2-richard.henderson@linaro.org>
Message-Id: <20230914155422.426639-4-alex.bennee@linaro.org>


  Commit: cb74b62684ef9dc1e36c377473c21731136990a4
      
https://github.com/qemu/qemu/commit/cb74b62684ef9dc1e36c377473c21731136990a4
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/qtest/microbit-test.c

  Log Message:
  -----------
  microbit: add missing qtest_quit() call

Without this call, the QEMU process is being left running which on
FreeBSD 13.2 at least, makes meson think the test is still running,
and thus execution of "make check" continues forever.

This fixes the regression introduced in:

  commit a9c9bbee855877293683012942d3485d50f286af
  Author: Chris Laplante <chris@laplante.io>
  Date:   Tue Aug 22 17:31:02 2023 +0100

    qtest: microbit-test: add tests for nRF51 DETECT

Fixes: https://gitlab.com/qemu-project/qemu/-/issues/1882
Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230912184130.3056054-2-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-5-alex.bennee@linaro.org>


  Commit: 3fbfd85911cee4a71f23989d725412d0dff756e6
      
https://github.com/qemu/qemu/commit/3fbfd85911cee4a71f23989d725412d0dff756e6
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/qtest/libqtest.c

  Log Message:
  -----------
  qtest: kill orphaned qtest QEMU processes on FreeBSD

On Linux we use PR_SET_PDEATHSIG to kill orphaned QEMU processes
if we fail to call qtest_quit(), or the test program aborts/segvs.
This prevents meson from hanging forever due to the orphaned
process keeping stdout open.

On FreeBSD we can achieve the same using PROC_PDEATHSIG_CTL, which
gives us the equivalent protection against hangs.

Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230912184130.3056054-3-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-6-alex.bennee@linaro.org>


  Commit: 6bef7a9133ad821c38da469bccdcf2dca1616698
      
https://github.com/qemu/qemu/commit/6bef7a9133ad821c38da469bccdcf2dca1616698
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M .gitlab-ci.d/cirrus.yml
    M .gitlab-ci.d/cirrus/build.yml

  Log Message:
  -----------
  gitlab: make Cirrus CI timeout explicit

On the GitLab side we're invoking the Cirrus CI job using the
cirrus-run tool which speaks to the Cirrus REST API. Cirrus
sometimes tasks 5-10 minutes to actually schedule the task,
and thus the execution time of 'cirrus-run' inside GitLab will
be slightly longer than the execution time of the Cirrus CI
task.

Setting the timeout in the GitLab CI job should thus be done
in relation to the timeout set for the Cirrus CI job. While
Cirrus CI defaults to 60 minutes, it is better to set this
explicitly, and make the relationship between the jobs
explicit

Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230912184130.3056054-4-berrange@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-7-alex.bennee@linaro.org>


  Commit: add780c2d1cd9bdbe725fceaab98d91656b39e1b
      
https://github.com/qemu/qemu/commit/add780c2d1cd9bdbe725fceaab98d91656b39e1b
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M .gitlab-ci.d/cirrus.yml

  Log Message:
  -----------
  gitlab: make Cirrus CI jobs gating

The Cirrus CI jobs have been non-gating for a while to let us build
confidence in their reliability. Aside from periodic dependancy
problems when FreeBSD Ports switches to be based on a new FreeBSD
image version, the jobs have been reliable. It is thus worth making
them gating to prevent build failures being missed during merges.

Signed-off-by: "Daniel P. Berrangé" <berrange@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20230912184130.3056054-5-berrange@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-8-alex.bennee@linaro.org>


  Commit: 37f115a7b4e28f13d92e1ad97d319e6e50825a2b
      
https://github.com/qemu/qemu/commit/37f115a7b4e28f13d92e1ad97d319e6e50825a2b
  Author: Nicholas Piggin <npiggin@gmail.com>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M python/qemu/machine/machine.py
    M tests/avocado/avocado_qemu/__init__.py

  Log Message:
  -----------
  tests/avocado: Fix console data loss

Occasionally some avocado tests will fail waiting for console line
despite the machine running correctly. Console data goes missing, as can
be seen in the console log. This is due to _console_interaction calling
makefile() on the console socket each time it is invoked, which must be
losing old buffer contents when going out of scope.

It is not enough to makefile() with buffered=0. That helps significantly
but data loss is still possible. My guess is that readline() has a line
buffer even when the file is in unbuffered mode, that can eat data.

Fix this by providing a console file that persists for the life of the
console.

Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Reviewed-by: "Daniel P. Berrangé" <berrange@redhat.com>
Message-Id: <20230912131340.405619-1-npiggin@gmail.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Acked-by: John Snow <jsnow@redhat.com>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-9-alex.bennee@linaro.org>


  Commit: 5acd4bf25dc9becd05b8772b94982722e1fa76a3
      
https://github.com/qemu/qemu/commit/5acd4bf25dc9becd05b8772b94982722e1fa76a3
  Author: Philippe Mathieu-Daudé <philmd@linaro.org>
  Date:   2023-09-15 (Fri, 15 Sep 2023)

  Changed paths:
    M tests/avocado/boot_linux_console.py
    M tests/avocado/machine_mips_malta.py
    M tests/avocado/replay_kernel.py
    M tests/avocado/tuxrun_baselines.py

  Log Message:
  -----------
  tests/avocado: Disable MIPS Malta tests due to GitLab issue #1884

Commit 0d58c66068 ("softmmu: Use async_run_on_cpu in tcg_commit")
introduced a regression which is only triggered by the MIPS Malta
machine. Since those tests are gatting and disturb the CI workflow,
disable them until https://gitlab.com/qemu-project/qemu/-/issues/1866
is fixed.

  $ make check-avocado \
      AVOCADO_TAGS='arch:mipsel arch:mips64el' \
      AVOCADO_ALLOW_UNTRUSTED_CODE=1 \
      AVOCADO_TIMEOUT_EXPECTED=1
    AVOCADO tests/avocado
   (04/24) 
tests/avocado/boot_linux_console.py:BootLinuxConsole.test_mips_malta32el_nanomips_4k:
 INTERRUPTED: Test interrupted by SIGTERM\nRunner error occurred: Timeout 
reached\nOriginal status: ERROR\n... (90.39 s)
   (05/24) 
tests/avocado/boot_linux_console.py:BootLinuxConsole.test_mips_malta32el_nanomips_16k_up:
 INTERRUPTED: Test interrupted by SIGTERM\nRunner error occurred: Timeout 
reached\nOriginal status: ERROR\n... (90.29 s)
   (06/24) 
tests/avocado/boot_linux_console.py:BootLinuxConsole.test_mips_malta32el_nanomips_64k_dbg:
 INTERRUPTED: Test interrupted by SIGTERM\nRunner error occurred: Timeout 
reached\nOriginal status: ERROR\n... (92.53 s)
   (11/24) 
tests/avocado/machine_mips_malta.py:MaltaMachineFramebuffer.test_mips_malta_i6400_framebuffer_logo_1core:
 INTERRUPTED: Test interrupted by SIGTERM\nRunner error occurred: Timeout 
reached\nOriginal status: ERROR\n... (25.78 s)
  RESULTS    : PASS 8 | ERROR 0 | FAIL 0 | SKIP 7 | WARN 2 | INTERRUPT 5 | 
CANCEL 2
  JOB TIME   : 525.60 s                                      ^^^^^^^^^^^

Reported-by: Thomas Huth <thuth@redhat.com>
Suggested-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Message-Id: <20230913135339.9128-1-philmd@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20230914155422.426639-10-alex.bennee@linaro.org>


  Commit: 8450c26c60df55f24710ece126ceb06c7a10ff39
      
https://github.com/qemu/qemu/commit/8450c26c60df55f24710ece126ceb06c7a10ff39
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-18 (Mon, 18 Sep 2023)

  Changed paths:
    M pc-bios/bios-256k.bin
    M pc-bios/bios-microvm.bin
    M pc-bios/bios.bin
    M pc-bios/vgabios-ati.bin
    M pc-bios/vgabios-bochs-display.bin
    M pc-bios/vgabios-cirrus.bin
    M pc-bios/vgabios-qxl.bin
    M pc-bios/vgabios-ramfb.bin
    M pc-bios/vgabios-stdvga.bin
    M pc-bios/vgabios-virtio.bin
    M pc-bios/vgabios-vmware.bin
    M pc-bios/vgabios.bin
    M roms/config.seabios-128k
    M roms/seabios

  Log Message:
  -----------
  Merge tag 'firmware/seabios-20230912-pull-request' of 
https://gitlab.com/kraxel/qemu into staging

seabios: update to git snapshot

Give seabios updates some testing coverage before
tagging a new release.  Update to release code
will follow later in the 8.2 devel cycle.

# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCgAdFiEEoDKM/7k6F6eZAf59TLbY7tPocTgFAmUAQuYACgkQTLbY7tPo
# cTigtBAAzQIPtXi703Bn+bQ4Fwi31MjbvnmtwXbFRMCZMoYuckJyxLa6Uos74ypk
# Anr7/1C8eaWqzvEP7G6EK5LLl4CrhlSm5fl5cL4YGUqPPoZhm/h0Og4QWze0ivjx
# gNbBUnc4UraTp65qPHXKs5nqkjksx7W9w+KNbunyJkBlzUFevvvGryJXglJU22HM
# d9ezFZi710XOFqr+CJWrHpV9V2VJCo4iIXz+nqi68hGChYk0IhUov36LM0oGT2Pf
# zKToaPLsnbVhWzuFQHOOjWmnqN05t0I0/K2ZzLKyXbvk4plY5rckPhBQ7AizJ1vM
# mgFvoYdfaQEC49MIFvhaBm+ebJ+dMMKzzMzv9P6mEn62LkWo41od66QonI70fS1f
# tarec+t4PLJcDC/VcyunR2kLENkfs6ABwd6RkUWQ9zvm8ljon8cd8O5hadMq/HPJ
# tr+xkUw97s+kDsvW+0hqXH/OuqgzVI3IRH7elmwH4ajN/pIuSpnG8HtZJJp5U9bx
# Gvd3IH1npAkrjHtzRbD3tshr4iuNCoHcGUU/GdHWqiTcB3UKquTgB/LT2faBxKJB
# kk9UHw+J182KDUy7vCr/NyA+KcEUJhPl1FRxSMoqedU4e6ICcGHHfv2yckCXl+eg
# 03fP1KN5pHQ08EM3lZtKIrs3TwHlq8TpwSz8puQ8oLModQvidcc=
# =7Yfq
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue 12 Sep 2023 06:52:22 EDT
# gpg:                using RSA key A0328CFFB93A17A79901FE7D4CB6D8EED3E87138
# gpg: Good signature from "Gerd Hoffmann (work) <kraxel@redhat.com>" [full]
# gpg:                 aka "Gerd Hoffmann <gerd@kraxel.org>" [full]
# gpg:                 aka "Gerd Hoffmann (private) <kraxel@gmail.com>" [full]
# Primary key fingerprint: A032 8CFF B93A 17A7 9901  FE7D 4CB6 D8EE D3E8 7138

* tag 'firmware/seabios-20230912-pull-request' of 
https://gitlab.com/kraxel/qemu:
  seabios: update binaries to git snapshot
  seabios: turn off CONFIG_APMBIOS for 128k build
  seabios: update submodule to git snapshot

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: 1738b8c11330ee73b3449582212c4bedc83540c2
      
https://github.com/qemu/qemu/commit/1738b8c11330ee73b3449582212c4bedc83540c2
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-18 (Mon, 18 Sep 2023)

  Changed paths:
    M block.c
    M block/blklogwrites.c
    M block/blkverify.c
    M block/block-backend.c
    M block/copy-before-write.c
    M block/crypto.c
    M block/graph-lock.c
    M block/io.c
    M block/mirror.c
    M block/preallocate.c
    M block/qcow.c
    M block/qcow2.c
    M block/quorum.c
    M block/replication.c
    M block/snapshot.c
    M block/stream.c
    M block/vmdk.c
    M blockdev.c
    M blockjob.c
    M hw/nvme/ctrl.c
    M include/block/aio.h
    M include/block/block-common.h
    M include/block/block-global-state.h
    M include/block/block-io.h
    M include/block/block_int-common.h
    M include/block/block_int-global-state.h
    M include/sysemu/block-backend-global-state.h
    M qapi/block-core.json
    M qemu-img.c
    M scripts/block-coroutine-wrapper.py
    M softmmu/dma-helpers.c
    M tests/qemu-iotests/051.pc.out
    M tests/qemu-iotests/122.out
    M tests/qemu-iotests/146.out
    M tests/qemu-iotests/154.out
    M tests/qemu-iotests/179.out
    M tests/qemu-iotests/209.out
    M tests/qemu-iotests/221.out
    M tests/qemu-iotests/223.out
    M tests/qemu-iotests/241.out
    M tests/qemu-iotests/244.out
    M tests/qemu-iotests/252.out
    M tests/qemu-iotests/253.out
    M tests/qemu-iotests/274.out
    M tests/qemu-iotests/tests/nbd-qemu-allocation.out
    M tests/qemu-iotests/tests/qemu-img-bitmaps.out
    M tests/unit/test-bdrv-drain.c
    M tests/unit/test-bdrv-graph-mod.c
    M tests/unit/test-block-iothread.c
    M util/thread-pool.c

  Log Message:
  -----------
  Merge tag 'for-upstream' of https://repo.or.cz/qemu/kevin into staging

Block layer patches

- Graph locking part 4 (node management)
- qemu-img map: report compressed data blocks
- block-backend: process I/O in the current AioContext

# -----BEGIN PGP SIGNATURE-----
#
# iQJFBAABCAAvFiEE3D3rFZqa+V09dFb+fwmycsiPL9YFAmUEbPkRHGt3b2xmQHJl
# ZGhhdC5jb20ACgkQfwmycsiPL9bIaQ//QAwYKudsfXZXaeWxqDm88tKHzN5oTt5P
# Fkb4MyHDqN0OboGwLbpHRFPDt5BPw3MhLzIyhsmWBD5Twyv+7+nTf7OzSp/ciNlg
# hISy/eZwEbqNZUktiYD8vCeuDJuCHSPlDKGe1as7mqSfVg1KwScYK2Yf8HWoTNz6
# Ku/Dm9opEX5obaOfeyLWXIzoWj5w2PcK4mn6hOTOSew6Ia44usV+QQe+yNAhMrJf
# sozoezaec6OUFXzoOlgz+nuEFcvxihST9ZBc/34msOSBGxDJuIHxBoAzsSTLZdmY
# LlsnzfjfFwd1qTb+m5h/HL2oEC9fje79XFWn8AAINkenXY8qZMfzXo+286DlQN/M
# YN6iq5pLmzOfbPLM6xq0EG/FBCm50mBmOgfyuLBuOhc3CTj/EzsGI7MAdeX32+cO
# 4pu2hGnzvqmWuJi+bVo40d1xpUnhEztzDK0d/NTvQMqNdQ4ieiLqCw1pgDvW4w6f
# 32xElO7wiut3SnylZoghXk2BACuK8SHeCgV2+iI9TRl8t0uBVsrYX/0mD4hNAtE0
# igNPQTfeZogqrFYhxrHftmL4pMfzvHXEaU1HbvJMTHnMdj+8bjtWfPpinmeLviP6
# fy1x90VJ7bSOgSgZSEGJTwCyOV+0M8bY5c+4uyRIRkye5QZtftYt5kJCvb0+4aTB
# ADq6DjKxX/A=
# =EgzU
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 15 Sep 2023 10:40:57 EDT
# gpg:                using RSA key DC3DEB159A9AF95D3D7456FE7F09B272C88F2FD6
# gpg:                issuer "kwolf@redhat.com"
# gpg: Good signature from "Kevin Wolf <kwolf@redhat.com>" [full]
# Primary key fingerprint: DC3D EB15 9A9A F95D 3D74  56FE 7F09 B272 C88F 2FD6

* tag 'for-upstream' of https://repo.or.cz/qemu/kevin: (28 commits)
  block-coroutine-wrapper: use qemu_get_current_aio_context()
  block-backend: process zoned requests in the current AioContext
  block-backend: process I/O in the current AioContext
  test-bdrv-drain: avoid race with BH in IOThread drain test
  block: remove AIOCBInfo->get_aio_context()
  qemu-img: map: report compressed data blocks
  block: add BDRV_BLOCK_COMPRESSED flag for bdrv_block_status()
  block: Mark bdrv_add/del_child() and caller GRAPH_WRLOCK
  block: Mark bdrv_unref_child() GRAPH_WRLOCK
  block: Mark bdrv_root_unref_child() GRAPH_WRLOCK
  block: Take graph rdlock in bdrv_change_aio_context()
  block: Take graph rdlock in bdrv_drop_intermediate()
  block: Mark bdrv_parent_cb_change_media() GRAPH_RDLOCK
  block: Mark bdrv_child_perm() GRAPH_RDLOCK
  block: Mark bdrv_get_cumulative_perm() and callers GRAPH_RDLOCK
  block: Mark bdrv_parent_perms_conflict() and callers GRAPH_RDLOCK
  block: Mark bdrv_attach_child() GRAPH_WRLOCK
  block: Call transaction callbacks with lock held
  block: Mark bdrv_attach_child_common() GRAPH_WRLOCK
  block: Mark bdrv_replace_child_tran() GRAPH_WRLOCK
  ...

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: 43e04b59ed0d8c0ff27839b7b57f8230eba7f408
      
https://github.com/qemu/qemu/commit/43e04b59ed0d8c0ff27839b7b57f8230eba7f408
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-18 (Mon, 18 Sep 2023)

  Changed paths:
    M .gitlab-ci.d/base.yml
    M .gitlab-ci.d/cirrus.yml
    M .gitlab-ci.d/cirrus/build.yml
    M python/qemu/machine/machine.py
    M tests/avocado/avocado_qemu/__init__.py
    M tests/avocado/boot_linux_console.py
    M tests/avocado/machine_mips_malta.py
    M tests/avocado/replay_kernel.py
    M tests/avocado/tuxrun_baselines.py
    M tests/docker/dockerfiles/debian-amd64-cross.docker
    M tests/docker/dockerfiles/debian-amd64.docker
    M tests/docker/dockerfiles/debian-arm64-cross.docker
    M tests/docker/dockerfiles/debian-armel-cross.docker
    M tests/docker/dockerfiles/debian-armhf-cross.docker
    M tests/docker/dockerfiles/debian-loongarch-cross.docker
    M tests/docker/dockerfiles/debian-ppc64el-cross.docker
    M tests/docker/dockerfiles/debian-s390x-cross.docker
    M tests/docker/dockerfiles/ubuntu2004.docker
    M tests/docker/dockerfiles/ubuntu2204.docker
    M tests/lcitool/libvirt-ci
    M tests/lcitool/refresh
    M tests/qtest/libqtest.c
    M tests/qtest/microbit-test.c

  Log Message:
  -----------
  Merge tag 'pull-maintainer-ominbus-150923-1' of 
https://gitlab.com/stsquad/qemu into staging

testing updates:

  - update most Debian to bookworm
  - fix some typos
  - update loongarch toolchain
  - fix microbit test
  - handle GitLab/Cirrus timeout discrepancy
  - improve avocado console handling
  - disable mips avocado images pending bugfix

# -----BEGIN PGP SIGNATURE-----
#
# iQEzBAABCgAdFiEEZoWumedRZ7yvyN81+9DbCVqeKkQFAmUEaC4ACgkQ+9DbCVqe
# KkTF3gf/Vx2bCmVJhro1Rve49fyZJXx2udqPbPVjAeXXK/SfvZqBzodM6DS4Aw7h
# 2ZC5uP9gx7Ra+9p+87SUUEenXLUBY0GqWL4AJuYlQ3EzJsDz8A98MGA2Hzr83ngE
# I036pnkaWYD+sxu+1O40e3n2pYOYKsufzvRzOLe/+9Fzh8gcdDrMdqkjA9SXkRlY
# QVaaMMdPClsSy5hq++8smvWNarAHth6WA02SrdFsJBt5hsICDYiDA8ny0+xmN/dl
# huElcdk562dkAnpBDmOEKjIvywThBRpxVPhI7NeA78k1gkBNCg0r+en4P5OSQ6f0
# 6zqcy5q3mkUVQ7xLK656BwhFCUl/PQ==
# =4GVc
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 15 Sep 2023 10:20:30 EDT
# gpg:                using RSA key 6685AE99E75167BCAFC8DF35FBD0DB095A9E2A44
# gpg: Good signature from "Alex Bennée (Master Work Key) 
<alex.bennee@linaro.org>" [unknown]
# gpg: WARNING: This key is not certified with a trusted signature!
# gpg:          There is no indication that the signature belongs to the owner.
# Primary key fingerprint: 6685 AE99 E751 67BC AFC8  DF35 FBD0 DB09 5A9E 2A44

* tag 'pull-maintainer-ominbus-150923-1' of https://gitlab.com/stsquad/qemu:
  tests/avocado: Disable MIPS Malta tests due to GitLab issue #1884
  tests/avocado: Fix console data loss
  gitlab: make Cirrus CI jobs gating
  gitlab: make Cirrus CI timeout explicit
  qtest: kill orphaned qtest QEMU processes on FreeBSD
  microbit: add missing qtest_quit() call
  tests/docker: Update docker-loongarch-cross toolchain
  gitlab: fix typo/spelling in comments
  tests: update Debian images to Bookworm

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


  Commit: 961476f356f30966afd5a090323f696dddc1e0e2
      
https://github.com/qemu/qemu/commit/961476f356f30966afd5a090323f696dddc1e0e2
  Author: Stefan Hajnoczi <stefanha@redhat.com>
  Date:   2023-09-18 (Mon, 18 Sep 2023)

  Changed paths:
    A crypto/clmul.c
    M crypto/meson.build
    M host/include/aarch64/host/cpuinfo.h
    A host/include/aarch64/host/crypto/clmul.h
    A host/include/generic/host/crypto/clmul.h
    M host/include/i386/host/cpuinfo.h
    A host/include/i386/host/crypto/clmul.h
    A host/include/x86_64/host/crypto/clmul.h
    A include/crypto/clmul.h
    M include/qemu/cpuid.h
    M target/arm/tcg/mve_helper.c
    M target/arm/tcg/vec_helper.c
    M target/arm/tcg/vec_internal.h
    M target/i386/ops_sse.h
    M target/ppc/int_helper.c
    M target/s390x/tcg/vec_int_helper.c
    M util/cpuinfo-aarch64.c
    M util/cpuinfo-i386.c

  Log Message:
  -----------
  Merge tag 'pull-crypto-20230915' of https://gitlab.com/rth7680/qemu into 
staging

Unify implementation of carry-less multiply.
Accelerate carry-less multiply for 64x64->128.

# -----BEGIN PGP SIGNATURE-----
#
# iQFRBAABCgA7FiEEekgeeIaLTbaoWgXAZN846K9+IV8FAmUEiPodHHJpY2hhcmQu
# aGVuZGVyc29uQGxpbmFyby5vcmcACgkQZN846K9+IV/akgf/XkiIeErWJr1YXSbS
# YPQtCsDAfIrqn3RiyQ2uwSn2eeuwVqTFFPGER04YegRDK8dyO874JBfvOwmBT70J
# I/aU8Z4BbRyNu9nfaCtFMlXQH9KArAKcAds1PnshfcnI5T2yBloZ1sAU97IuJFZk
# Uuz96H60+ohc4wzaUiPqPhXQStgZeSYwwAJB0s25DhCckdea0udRCAJ1tQTVpxkM
# wIFef1SHPoM6DtMzFKHLLUH6VivSlHjqx8GqFusa7pVqfQyDzNBfwvDl1F/bkE07
# yTocQEkV3QnZvIplhqUxAaZXIFZr9BNk7bDimMjHW6z3pNPN3T8zRn4trNjxbgPV
# jqzAtg==
# =8nnk
# -----END PGP SIGNATURE-----
# gpg: Signature made Fri 15 Sep 2023 12:40:26 EDT
# gpg:                using RSA key 7A481E78868B4DB6A85A05C064DF38E8AF7E215F
# gpg:                issuer "richard.henderson@linaro.org"
# gpg: Good signature from "Richard Henderson <richard.henderson@linaro.org>" 
[full]
# Primary key fingerprint: 7A48 1E78 868B 4DB6 A85A  05C0 64DF 38E8 AF7E 215F

* tag 'pull-crypto-20230915' of https://gitlab.com/rth7680/qemu:
  host/include/aarch64: Implement clmul.h
  host/include/i386: Implement clmul.h
  target/ppc: Use clmul_64
  target/s390x: Use clmul_64
  target/i386: Use clmul_64
  target/arm: Use clmul_64
  crypto: Add generic 64-bit carry-less multiply routine
  target/ppc: Use clmul_32* routines
  target/s390x: Use clmul_32* routines
  target/arm: Use clmul_32* routines
  crypto: Add generic 32-bit carry-less multiply routines
  target/ppc: Use clmul_16* routines
  target/s390x: Use clmul_16* routines
  target/arm: Use clmul_16* routines
  crypto: Add generic 16-bit carry-less multiply routines
  target/ppc: Use clmul_8* routines
  target/s390x: Use clmul_8* routines
  target/arm: Use clmul_8* routines
  crypto: Add generic 8-bit carry-less multiply routines

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>


Compare: https://github.com/qemu/qemu/compare/005ad32358f1...961476f356f3



reply via email to

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