Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: c75847f9eb8fb09dde0c0f4fa4710c6bde11f5a9
      
https://github.com/qemu/qemu/commit/c75847f9eb8fb09dde0c0f4fa4710c6bde11f5a9
  Author: Peter Xu <pet...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M system/physmem.c

  Log Message:
  -----------
  memory: Fix addr/len for flatview_access_allowed()

flatview_access_allowed() should pass in the address offset of the memory
region, rather than the global address space. Shouldn't be a major issue
yet, since the addr is only used in an error log.

Cc: Philippe Mathieu-Daudé <phi...@linaro.org>
Fixes: 3ab6fdc91b ("softmmu/physmem: Introduce MemTxAttrs::memory field and 
MEMTX_ACCESS_ERROR")
Reviewed-by: Philippe Mathieu-Daudé <phi...@linaro.org>
Reviewed-by: David Hildenbrand <da...@redhat.com>
Link: https://lore.kernel.org/r/20250903142932.1038765-1-pet...@redhat.com
Signed-off-by: Peter Xu <pet...@redhat.com>


  Commit: ac7a892fd37ce4427d390ca8556203c9a2eb9d38
      
https://github.com/qemu/qemu/commit/ac7a892fd37ce4427d390ca8556203c9a2eb9d38
  Author: Peter Xu <pet...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M docs/devel/memory.rst
    M system/memory.c

  Log Message:
  -----------
  memory: Fix leaks due to owner-shared MRs circular references

Currently, QEMU refcounts the MR by always taking it from the owner.

It's common that one object will have multiple MR objects embeded in the
object itself.  All the MRs in this case share the same lifespan of the
owner object.

It's also common that in the instance_init() of an object, MR A can be a
container of MR B, C, D, by using memory_region_add_subregion*() set of
memory region APIs.

Now we have a circular reference issue, as when adding subregions for MR A,
we essentially incremented the owner's refcount within the instance_init(),
meaning the object will be self-boosted and its refcount can never go down
to zero if the MRs won't get detached properly before object's finalize().

Delete subregions within object's finalize() won't work either, because
finalize() will be invoked only if the refcount goes to zero first.  What
is worse, object_finalize() will do object_property_del_all() first before
object_deinit().  Since embeded MRs will be properties of the owner object,
it means they'll be freed _before_ the owner's finalize().

To fix that, teach memory API to stop refcount on MRs that share the same
owner.  Because if they share the lifecycle of the owner, then they share
the same lifecycle between themselves, hence the refcount doesn't help but
only introduce troubles.

Meanwhile, allow auto-detachments of MRs during finalize() of MRs even
against its container, as long as they belong to the same owner.

The latter is needed because now it's possible to have MRs' finalize()
happen in any order when they share the same lifespan with a same owner.
In this case, we should allow finalize() to happen in any order of either
the parent or child MR.  Loose the mr->container check in MR's finalize()
to allow auto-detach.  Double check it shares the same owner.

Proper document this behavior in code.

This patch is heavily based on the work done by Akihiko Odaki:

https://lore.kernel.org/r/cafeaca8dv40fgsci76r4yep1p-sp_qjnrdd2ozpxjx5wrs0...@mail.gmail.com

Cc: Akihiko Odaki <od...@rsg.ci.i.u-tokyo.ac.jp>
Cc: Paolo Bonzini <pbonz...@redhat.com>
Reviewed-by: Clément Mathieu--Drif <clement.mathieu--d...@eviden.com>
Reviewed-by: Peter Maydell <peter.mayd...@linaro.org>
Tested-by: Peter Maydell <peter.mayd...@linaro.org>
Link: https://lore.kernel.org/r/20250826221750.285242-1-pet...@redhat.com
Signed-off-by: Peter Xu <pet...@redhat.com>


  Commit: 2d26741fc5170e51621eb365a34460fadb5f969e
      
https://github.com/qemu/qemu/commit/2d26741fc5170e51621eb365a34460fadb5f969e
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/error.py
    M python/qemu/qmp/message.py
    M python/qemu/qmp/protocol.py
    M python/qemu/qmp/qmp_client.py

  Log Message:
  -----------
  python: backport 'Change error classes to have better repr methods'

By passing all of the arguments to the base class and overriding the
__str__ method when we want a different "human readable" message that
isn't just printing the list of arguments, we can ensure that all custom
error classes have a reasonable __repr__ implementation.

In the case of ExecuteError, the pseudo-field that isn't actually
correlated to an input argument can be re-imagined as a read-only
property; this forces consistency in the class and makes the repr output
more obviously correct.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@afdb7893f3b34212da4259b7202973f9a8cb85b3
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: cb0e43804038e47bbaf0179ce67df678ec13a392
      
https://github.com/qemu/qemu/commit/cb0e43804038e47bbaf0179ce67df678ec13a392
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/events.py

  Log Message:
  -----------
  python: backport 'EventListener: add __repr__ method'

When the object is not stateful, this repr method prints what you'd
expect. In cases where there are pending events, the output is augmented
to illustrate that.

The object itself has no idea if it's "active" or not, so it cannot
convey that information.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@8a6f2e136dae395fec8aa5fd77487cfe12d9e05e
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 1e343714bfc06cc982e68a290f3809117d6dfcd0
      
https://github.com/qemu/qemu/commit/1e343714bfc06cc982e68a290f3809117d6dfcd0
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/legacy.py

  Log Message:
  -----------
  python: backport 'kick event queue on legacy event_pull()'

This corrects an oversight in qmp-shell operation where new events will
not accumulate in the event queue when pressing "enter" with an empty
command buffer, so no new events show up.

Reported-by: Jag Raman <jag.ra...@oracle.com>
Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@0443582d16cf9efd52b2c41a7b5be7af42c856cd
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 094ded5227dc4e8dde2c78a9788bf6c90771ad85
      
https://github.com/qemu/qemu/commit/094ded5227dc4e8dde2c78a9788bf6c90771ad85
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/protocol.py

  Log Message:
  -----------
  python: backport 'protocol: adjust logging name when changing client name'

The client name is mutable, so the logging name should also change to
reflect it when it changes.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@e10b73c633ce138ba30bc8beccd2ab31989eaf3d
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: f9d2e0a3bd7ba2a693a892881f91cf53fa90cc71
      
https://github.com/qemu/qemu/commit/f9d2e0a3bd7ba2a693a892881f91cf53fa90cc71
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/protocol.py
    M python/qemu/qmp/qmp_tui.py
    M python/qemu/qmp/util.py
    M python/tests/protocol.py

  Log Message:
  -----------
  python: backport 'drop Python3.6 workarounds'

Now that the minimum version is 3.7, drop some of the 3.6-specific hacks
we've been carrying. A single remaining compatibility hack concerning
3.6's lack of @asynccontextmanager is addressed in the following commit.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@3e8e34e594cfc6b707e6f67959166acde4b421b8
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 0408b8d7a086486f5c1887798be744b2d73bcda9
      
https://github.com/qemu/qemu/commit/0408b8d7a086486f5c1887798be744b2d73bcda9
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/protocol.py

  Log Message:
  -----------
  python: backport 'Use @asynciocontextmanager'

This removes a non-idiomatic use of a "coroutine callback" in favor of
something a bit more standardized.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit python-qemu-qmp@commit 
97f7ffa3be17a50544b52767d14b6fd478c07b9e
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 8fd9ccebd905dfe3afdee03732ba09e46a3a1d49
      
https://github.com/qemu/qemu/commit/8fd9ccebd905dfe3afdee03732ba09e46a3a1d49
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/qmp_shell.py

  Log Message:
  -----------
  python: backport 'qmp-shell: add common_parser()'

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@20a88c2471f37d10520b2409046d59e1d0f1e905
Signed-off-by: John Snow <js...@redhat.com>
Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 653f501434889b23a5062b3fe00488d140eb79fd
      
https://github.com/qemu/qemu/commit/653f501434889b23a5062b3fe00488d140eb79fd
  Author: Adam Dorsey <adam.dor...@twosixtech.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/protocol.py
    M python/qemu/qmp/qmp_client.py

  Log Message:
  -----------
  python: backport 'feat: allow setting read buffer limit'

Expose the limit parameter of the underlying StreamReader and StreamWriter
instances.

This is helpful for the use case of transferring files in and out of a VM
via the QEMU guest agent's guest-file-open, guest-file-read, guest-file-write,
and guest-file-close methods, as it allows pushing the buffer size up to the
guest agent's limit of 48MB per transfer.

Signed-off-by: Adam Dorsey <adam@dorseys.email>
cherry picked from commit 
python-qemu-qmp@9ba6a698344eb3b570fa4864e906c54042824cd6
cherry picked from commit 
python-qemu-qmp@e4d0d3f835d82283ee0e48438d1b154e18303491
[Squashed in linter fixups. --js]
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: a50b8572f0e3873db64dd6660cea047f067ca5f7
      
https://github.com/qemu/qemu/commit/a50b8572f0e3873db64dd6660cea047f067ca5f7
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/protocol.py

  Log Message:
  -----------
  python: backport 'make require() preserve async-ness'

This is not strictly needed functionality-wise, but doing this allows
sphinx to see which decorated methods are async. Without this, sphinx
misses the "async" classifier on generated docs, which ... for an async
library, isn't great.

It does make an already gnarly function even gnarlier, though.

So, what's going on here?

A synchronous function (like require() before this patch) can return a
coroutine that can be awaited on, for example:

  def some_func():
      return asyncio.task(asyncio.sleep(5))

  async def some_async_func():
      await some_func()

However, this function is not considered to be an "async" function in
the eyes of the abstract syntax tree. Specifically,
some_func.__code__.co_flags will not be set with CO_COROUTINE.

The interpreter uses this flag to know if it's legal to use "await" from
within the body of the function. Since this function is just wrapping
another function, it doesn't matter much for the decorator, but sphinx
uses the stdlib inspect.iscoroutinefunction() to determine when to add
the "async" prefix in generated output. This function uses the presence
of CO_COROUTINE.

So, in order to preserve the "async" flag for docs, the require()
decorator needs to differentiate based on whether it is decorating a
sync or async function and use a different wrapping mechanism
accordingly.

Phew.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@40aa9699d619849f528032aa456dd061a4afa957
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: fcaeeb7653d2c6f38183170e1cae5729adb7875c
      
https://github.com/qemu/qemu/commit/fcaeeb7653d2c6f38183170e1cae5729adb7875c
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/qmp_shell.py

  Log Message:
  -----------
  python: backport 'qmp-shell-wrap: handle missing binary gracefully'

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@9c889dcbd58817b0c917a9d2dd16161f48ac8203
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: fd0ed46d4effbf2700804657bad9c6db086527c4
      
https://github.com/qemu/qemu/commit/fd0ed46d4effbf2700804657bad9c6db086527c4
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/qmp_tui.py

  Log Message:
  -----------
  python: backport 'qmp-tui: Do not crash if optional dependencies are not met'

Based on the discussion at https://github.com/pypa/pip/issues/9726 -
even though the setuptools documentation implies that it is possible to
guard script execution with optional dependency groups, this is not true
in practice with the scripts generated by pip.

Just do the simple thing and guard the import statements.

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@df520dcacf9a75dd4c82ab1129768de4128b554c
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 5d99044d09db0fa8c2b3294e301927118f9effc9
      
https://github.com/qemu/qemu/commit/5d99044d09db0fa8c2b3294e301927118f9effc9
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/legacy.py
    M python/qemu/qmp/qmp_tui.py
    M python/tests/protocol.py

  Log Message:
  -----------
  python: backport 'Remove deprecated get_event_loop calls'

This method was deprecated in 3.12 because it ordinarily should not be
used from coroutines; if there is not a currently running event loop,
this automatically creates a new event loop - which is usually not what
you want from code that would ever run in the bottom half.

In our case, we do want this behavior in two places:

(1) The synchronous shim, for convenience: this allows fully sync
programs to use QEMUMonitorProtocol() without needing to set up an event
loop beforehand. This is intentional to fully box in the async
complexities into the legacy sync shim.

(2) The qmp_tui shell; instead of relying on asyncio.run to create and
run an asyncio program, we need to be able to pass the current asyncio
loop to urwid setup functions. For convenience, again, we create one if
one is not present to simplify the creation of the TUI appliance.

The remaining user of get_event_loop() was in fact one of the erroneous
users that should not have been using this function: if there's no
running event loop inside of a coroutine, you're in big trouble :)

Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@aa1ff9907603a3033296027e1bd021133df86ef1
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 85f223e5b031eb8ab63fbca314a4fb296a3a2632
      
https://github.com/qemu/qemu/commit/85f223e5b031eb8ab63fbca314a4fb296a3a2632
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/legacy.py
    M python/qemu/qmp/qmp_tui.py
    M python/qemu/qmp/util.py

  Log Message:
  -----------
  python: backport 'avoid creating additional event loops per thread'

This commit is two backports squashed into one to avoid regressions.

python: *really* remove get_event_loop

A prior commit, aa1ff990, switched away from using get_event_loop *by
default*, but this is not good enough to avoid deprecation warnings as
`asyncio.get_event_loop_policy().get_event_loop()` is *also*
deprecated. Replace this mechanism with explicit calls to
asyncio.get_new_loop() and revise the cleanup mechanisms in __del__ to
match.

python: avoid creating additional event loops per thread

"Too hasty by far!", commit 21ce2ee4 attempted to avoid deprecated
behavior altogether by calling new_event_loop() directly if there was no
loop currently running, but this has the unfortunate side effect of
potentially creating multiple event loops per thread if tests
instantiate multiple QMP connections in a single thread. This behavior
is apparently not well-defined and causes problems in some, but not all,
combinations of Python interpreter version and platform environment.

Partially revert to Daniel Berrange's original patch, which calls
get_event_loop and simply suppresses the deprecation warning in
Python<=3.13. This time, however, additionally register new loops
created with new_event_loop() so that future calls to get_event_loop()
will return the loop already created.

Reported-by: Richard W.M. Jones <rjo...@redhat.com>
Reported-by: Daniel P. Berrangé <berra...@redhat.com>
Signed-off-by: John Snow <js...@redhat.com>
cherry picked from commit 
python-qemu-qmp@21ce2ee4f2df87efe84a27b9c5112487f4670622
cherry picked from commit 
python-qemu-qmp@c08fb82b38212956ccffc03fc6d015c3979f42fe
Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: f414048e32262830e06d50240b2f15b6e5857efe
      
https://github.com/qemu/qemu/commit/f414048e32262830e06d50240b2f15b6e5857efe
  Author: John Snow <js...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/qmp/__init__.py
    M python/qemu/qmp/events.py
    M python/qemu/qmp/legacy.py
    M python/qemu/qmp/message.py
    M python/qemu/qmp/models.py
    M python/qemu/qmp/protocol.py
    M python/qemu/qmp/qmp_client.py
    M python/qemu/qmp/qmp_shell.py
    M python/qemu/qmp/util.py

  Log Message:
  -----------
  python: synchronize qemu.qmp documentation

This patch collects comments and documentation changes from many commits
in the python-qemu-qmp repository; bringing the qemu.git copy in
bit-identical alignment with the standalone library *except* for several
copyright messages that reference the "LICENSE" file which is, for QEMU,
named "COPYING" instead and are therefore left unchanged.

Signed-off-by: John Snow <js...@redhat.com>
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 82c7cb93c750196f513a1b11cb85e0328bad444f
      
https://github.com/qemu/qemu/commit/82c7cb93c750196f513a1b11cb85e0328bad444f
  Author: Daniel P. Berrangé <berra...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M tests/qemu-iotests/testenv.py
    M tests/qemu-iotests/testrunner.py

  Log Message:
  -----------
  iotests: drop compat for old version context manager

Our minimum python is now 3.9, so back compat with prior
python versions is no longer required.

Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 6ccb48ffc19fe25511313a246d4a8bad51114ea9
      
https://github.com/qemu/qemu/commit/6ccb48ffc19fe25511313a246d4a8bad51114ea9
  Author: Daniel P. Berrangé <berra...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M python/qemu/machine/qtest.py

  Log Message:
  -----------
  python: ensure QEMUQtestProtocol closes its socket

While QEMUQtestMachine closes the socket that was passed to
QEMUQtestProtocol, the python resource leak manager still
believes that the copy QEMUQtestProtocol holds is open. We
must explicitly call close to avoid this leak warnnig.

Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: d4d0ebfcc926c11d16320d0d5accf22e3441c115
      
https://github.com/qemu/qemu/commit/d4d0ebfcc926c11d16320d0d5accf22e3441c115
  Author: Daniel P. Berrangé <berra...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M tests/qemu-iotests/147

  Log Message:
  -----------
  iotests/147: ensure temporary sockets are closed before exiting

This avoids the python resource leak detector from issuing warnings
in the iotests.

Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 2b2fb25c2aaf5b2e8172d845db39cc50a951a12e
      
https://github.com/qemu/qemu/commit/2b2fb25c2aaf5b2e8172d845db39cc50a951a12e
  Author: Daniel P. Berrangé <berra...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M tests/qemu-iotests/151

  Log Message:
  -----------
  iotests/151: ensure subprocesses are cleaned up

The iotest 151 creates a bunch of subprocesses, with their stdout
connected to a pipe but never reads any data from them and does
not gurantee the processes are killed on cleanup.

This triggers resource leak warnings from python when the
subprocess.Popen object is garbage collected.

Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: 9a494d83538680651197651031375c2b6fa2490b
      
https://github.com/qemu/qemu/commit/9a494d83538680651197651031375c2b6fa2490b
  Author: Daniel P. Berrangé <berra...@redhat.com>
  Date:   2025-09-15 (Mon, 15 Sep 2025)

  Changed paths:
    M tests/qemu-iotests/check

  Log Message:
  -----------
  iotests/check: always enable all python warnings

Of most importance is that this gives us a heads-up if anything
we rely on has been deprecated. The default python behaviour
only emits a warning if triggered from __main__ which is very
limited.

Setting the env variable further ensures that any python child
processes will also display warnings.

Signed-off-by: Daniel P. Berrangé <berra...@redhat.com>


  Commit: aa3c761c7095476acde9b7140cc1dfff2ee0e170
      
https://github.com/qemu/qemu/commit/aa3c761c7095476acde9b7140cc1dfff2ee0e170
  Author: Richard Henderson <richard.hender...@linaro.org>
  Date:   2025-09-16 (Tue, 16 Sep 2025)

  Changed paths:
    M tests/functional/x86_64/test_memlock.py

  Log Message:
  -----------
  tests/functional/x86_64: Accept a few locked pages in test_memlock.py

Startup of libgcrypt locks a small pool of pages -- by default 16k.
Testing for zero locked pages is isn't correct, while testing for
32k is a decent compromise.

Reviewed-by: Thomas Huth <th...@redhat.com>
Signed-off-by: Richard Henderson <richard.hender...@linaro.org>


  Commit: a11d1847d5ef8a7db58e6d4e44f36fec708f0981
      
https://github.com/qemu/qemu/commit/a11d1847d5ef8a7db58e6d4e44f36fec708f0981
  Author: Alex Bennée <alex.ben...@linaro.org>
  Date:   2025-09-16 (Tue, 16 Sep 2025)

  Changed paths:
    M .gitmodules

  Log Message:
  -----------
  .gitmodules: move u-boot mirrors to qemu-project-mirrors

To continue our GitLab Open Source Program license we need to pass an
automated license check for all repos under qemu-project. While U-Boot
is clearly GPLv2 rather than fight with the automated validation
script just move the mirror across to a separate project.

Signed-off-by: Alex Bennée <alex.ben...@linaro.org>
Suggested-by: Daniel P. Berrangé <berra...@redhat.com>
Cc: qemu-sta...@nongnu.org
Reviewed-by: Daniel P. Berrangé <berra...@redhat.com>
Signed-off-by: Richard Henderson <richard.hender...@linaro.org>
Message-ID: <20250908141911.2546063-1-alex.ben...@linaro.org>
Signed-off-by: Richard Henderson <richard.hender...@linaro.org>


  Commit: 5bf071485af9340fb7f387d071da0494f80e20d1
      
https://github.com/qemu/qemu/commit/5bf071485af9340fb7f387d071da0494f80e20d1
  Author: Richard Henderson <richard.hender...@linaro.org>
  Date:   2025-09-16 (Tue, 16 Sep 2025)

  Changed paths:
    M docs/devel/memory.rst
    M system/memory.c
    M system/physmem.c

  Log Message:
  -----------
  Merge tag 'mem-staging-pull-request' of https://gitlab.com/peterx/qemu into 
staging

Memory pull for 10.2

- Peter's fix on flatview_access_allowed()
- Peter's fix on MR circular ref

# -----BEGIN PGP SIGNATURE-----
#
# iIgEABYKADAWIQS5GE3CDMRX2s990ak7X8zN86vXBgUCaMg4oxIccGV0ZXJ4QHJl
# ZGhhdC5jb20ACgkQO1/MzfOr1wYeLAD+LQ44LdRTjbdlAbDjSNnCorfEBFUmNysK
# St4ut4Z9ZzAA+gK8DO12zc41Oi51NaBdD+X0s94DCV4UFl4Cz1D8HoIF
# =hAUJ
# -----END PGP SIGNATURE-----
# gpg: Signature made Mon 15 Sep 2025 09:02:43 AM PDT
# gpg:                using EDDSA key B9184DC20CC457DACF7DD1A93B5FCCCDF3ABD706
# gpg:                issuer "pet...@redhat.com"
# gpg: Good signature from "Peter Xu <xzpe...@gmail.com>" [unknown]
# gpg:                 aka "Peter Xu <pet...@redhat.com>" [unknown]
# gpg: WARNING: The key's User ID is not certified with a trusted signature!
# gpg:          There is no indication that the signature belongs to the owner.
# Primary key fingerprint: B918 4DC2 0CC4 57DA CF7D  D1A9 3B5F CCCD F3AB D706

* tag 'mem-staging-pull-request' of https://gitlab.com/peterx/qemu:
  memory: Fix leaks due to owner-shared MRs circular references
  memory: Fix addr/len for flatview_access_allowed()

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


  Commit: 41511ed734dbf32f3c42ece60db0b86e081de4d2
      
https://github.com/qemu/qemu/commit/41511ed734dbf32f3c42ece60db0b86e081de4d2
  Author: Richard Henderson <richard.hender...@linaro.org>
  Date:   2025-09-16 (Tue, 16 Sep 2025)

  Changed paths:
    M python/qemu/machine/qtest.py
    M python/qemu/qmp/__init__.py
    M python/qemu/qmp/error.py
    M python/qemu/qmp/events.py
    M python/qemu/qmp/legacy.py
    M python/qemu/qmp/message.py
    M python/qemu/qmp/models.py
    M python/qemu/qmp/protocol.py
    M python/qemu/qmp/qmp_client.py
    M python/qemu/qmp/qmp_shell.py
    M python/qemu/qmp/qmp_tui.py
    M python/qemu/qmp/util.py
    M python/tests/protocol.py
    M tests/qemu-iotests/147
    M tests/qemu-iotests/151
    M tests/qemu-iotests/check
    M tests/qemu-iotests/testenv.py
    M tests/qemu-iotests/testrunner.py

  Log Message:
  -----------
  Merge tag 'python-pull-request' of https://gitlab.com/jsnow/qemu into staging

Python Pull Request

Python 3.14 support & synchronize with python-qemu-qmp repo

# -----BEGIN PGP SIGNATURE-----
#
# iQIzBAABCgAdFiEE+ber27ys35W+dsvQfe+BBqr8OQ4FAmjJjxIACgkQfe+BBqr8
# OQ48aA/+JRRIEN8LMbNDRvPTTkvCxstSAb2q8yA+8ccWg0H+EGcewjd+oCoPOqjC
# SwIMAGYJ6Dv2LW6c+rK6VjKw1Da8J9WgEpKmfoWu+1Pef8odU5PoRhAvvZdMq+Eh
# Kqk0r1f87fTiZK1gCBhBUIO0oTroOYxDvIYV0B6UFDPArL8jJ5eTpGLCVAYuk8tH
# MuzQD0IcxCBoraOx9vqVMbKIHwMH/m9pJ2IqINzIStpLoFgT1d5V9CoKXImMVXmF
# XovcMWQzFz1a/lm0ybSAzhgXcpW/vNjstb1IcrigYjQWXU6S+/bRpq17c2WqAJtG
# 78Dal7heSjpvWyyCCii+QO+BegH53Mgz3W+aQN7+fkcepjivVYy8tnxOrSjJR+pX
# DqRhMNSc4CrLvJH4BOHKUsJaWMxjd4oJiNhUmhJ7MxZhPTHZvERsOo9kpoJo4eTw
# GhRV98FnJbotgs2kjQpSBF8FDj9LZqPwTfMuEU2NUsIB9o7/Iqj36RDe9L+2r9Ch
# 2UKhnUg58y4eYFoC4CO8yCfjsR6HzLdqiVaDhcu5pdQM0Dw1pxrSIHb6faNmSLL5
# v0brhgJGujWt6wAc2c3ASMf8qpWkBrlVfHybodOB2cUDcRgNk85M/s41PnGShqBZ
# Qq7VW9zR4sejwof9dTwYKuwsNzxzFdS2nLwPPkud5aDngrLsNn0=
# =jZpa
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue 16 Sep 2025 09:23:46 AM PDT
# gpg:                using RSA key F9B7ABDBBCACDF95BE76CBD07DEF8106AAFC390E
# gpg: Good signature from "John Snow (John Huston) <js...@redhat.com>" 
[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: FAEB 9711 A12C F475 812F  18F2 88A9 064D 1835 61EB
#      Subkey fingerprint: F9B7 ABDB BCAC DF95 BE76  CBD0 7DEF 8106 AAFC 390E

* tag 'python-pull-request' of https://gitlab.com/jsnow/qemu:
  iotests/check: always enable all python warnings
  iotests/151: ensure subprocesses are cleaned up
  iotests/147: ensure temporary sockets are closed before exiting
  python: ensure QEMUQtestProtocol closes its socket
  iotests: drop compat for old version context manager
  python: synchronize qemu.qmp documentation
  python: backport 'avoid creating additional event loops per thread'
  python: backport 'Remove deprecated get_event_loop calls'
  python: backport 'qmp-tui: Do not crash if optional dependencies are not met'
  python: backport 'qmp-shell-wrap: handle missing binary gracefully'
  python: backport 'make require() preserve async-ness'
  python: backport 'feat: allow setting read buffer limit'
  python: backport 'qmp-shell: add common_parser()'
  python: backport 'Use @asynciocontextmanager'
  python: backport 'drop Python3.6 workarounds'
  python: backport 'protocol: adjust logging name when changing client name'
  python: backport 'kick event queue on legacy event_pull()'
  python: backport 'EventListener: add __repr__ method'
  python: backport 'Change error classes to have better repr methods'

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


  Commit: 2e66fb24a0ca9750df0d1d5b35197ff89c4bbd46
      
https://github.com/qemu/qemu/commit/2e66fb24a0ca9750df0d1d5b35197ff89c4bbd46
  Author: Richard Henderson <richard.hender...@linaro.org>
  Date:   2025-09-16 (Tue, 16 Sep 2025)

  Changed paths:
    M .gitmodules
    M tests/functional/x86_64/test_memlock.py

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

.gitmodules: move u-boot mirrors to qemu-project-mirrors
tests/functional/x86_64: Accept a few locked pages in test_memlock.py

# -----BEGIN PGP SIGNATURE-----
#
# iQFRBAABCgA7FiEEekgeeIaLTbaoWgXAZN846K9+IV8FAmjJmVwdHHJpY2hhcmQu
# aGVuZGVyc29uQGxpbmFyby5vcmcACgkQZN846K9+IV+RMQf/e2ScmOiJaD/5ba5i
# RPZneCUOV0AkVSpAwxKX9M1Gsroz/NZefVp9yh2wPdcoAPnLjoFJaJuEv1jEPPVh
# /RApI2NehuqWTzndY0dci6vV6YzxLoMZsQWoBRz0l3SfzVq0YuePSlV+YkTMSfgX
# z9ocwPwGG0AEYvEllVPq5UVHZlEoE4BE23QyHtyuXRwjqo3BHjJKQXBK4hA5vAYQ
# gbWiFs3QJ+fsKQk7Z2KJDc6k4H/Oql4T2bILGjQRb9DG4yR1TIvwIsbOj2dFHVrs
# 6HdP5e6PweuHGc8mdFEHJFgZrdA8exxwT0lq/5vYxvjf86nick+z3XrhOXWoHq6G
# L6OgLg==
# =YBDc
# -----END PGP SIGNATURE-----
# gpg: Signature made Tue 16 Sep 2025 10:07:40 AM PDT
# gpg:                using RSA key 7A481E78868B4DB6A85A05C064DF38E8AF7E215F
# gpg:                issuer "richard.hender...@linaro.org"
# gpg: Good signature from "Richard Henderson <richard.hender...@linaro.org>" 
[ultimate]

* tag 'pull-misc-20250916' of https://gitlab.com/rth7680/qemu:
  .gitmodules: move u-boot mirrors to qemu-project-mirrors
  tests/functional/x86_64: Accept a few locked pages in test_memlock.py

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


Compare: https://github.com/qemu/qemu/compare/190d5d7fd725...2e66fb24a0ca

To unsubscribe from these emails, change your notification settings at 
https://github.com/qemu/qemu/settings/notifications

Reply via email to