From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: [PULL 0/6] Host Memory Backends and Memory devices queue 2024-09-24
Date: Tue, 24 Sep 2024 12:03:23 +0200 [thread overview]
Message-ID: <20240924100329.248738-1-david@redhat.com> (raw)
Hi,
due to reset changes this contains a bit of churn that touches various
architectures, but it's all fairly minimal and straight-forward.
The following changes since commit 01dc65a3bc262ab1bec8fe89775e9bbfa627becb:
Merge tag 'pull-target-arm-20240919' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2024-09-19 14:15:15 +0100)
are available in the Git repository at:
https://github.com/davidhildenbrand/qemu.git tags/mem-2024-09-24
for you to fetch changes up to 78c8f780d3f0d6d17aa93d6f99ff72960080fdd7:
hostmem: Apply merge property after the memory region is initialized (2024-09-24 11:33:35 +0200)
----------------------------------------------------------------
Hi,
"Host Memory Backends" and "Memory devices" queue ("mem"):
- Kconfig fix for virtio-based memory devices
- virtio-mem support for suspend+wake-up with plugged memory
- hostmem fix when specifying "merge=off"
----------------------------------------------------------------
Gavin Shan (1):
hostmem: Apply merge property after the memory region is initialized
Juraj Marcin (4):
reset: Use ResetType for qemu_devices_reset() and MachineClass::reset()
reset: Add RESET_TYPE_WAKEUP
virtio-mem: Use new Resettable framework instead of LegacyReset
virtio-mem: Add support for suspend+wake-up with plugged memory
Paolo Bonzini (1):
virtio: kconfig: memory devices are PCI only
backends/hostmem.c | 2 +-
docs/devel/reset.rst | 12 ++++++++++-
hw/arm/aspeed.c | 4 ++--
hw/arm/mps2-tz.c | 4 ++--
hw/core/reset.c | 5 +----
hw/hppa/machine.c | 4 ++--
hw/i386/microvm.c | 4 ++--
hw/i386/pc.c | 6 +++---
hw/ppc/pegasos2.c | 4 ++--
hw/ppc/pnv.c | 4 ++--
hw/ppc/spapr.c | 6 +++---
hw/s390x/s390-virtio-ccw.c | 4 ++--
hw/virtio/Kconfig | 11 ++++++++++
hw/virtio/virtio-mem.c | 48 ++++++++++++++++++++++++++++++------------
hw/virtio/virtio-qmp.c | 3 +++
include/hw/boards.h | 3 ++-
include/hw/resettable.h | 2 ++
include/hw/virtio/virtio-mem.h | 4 ++++
include/sysemu/reset.h | 5 +++--
system/runstate.c | 13 ++++++++++--
20 files changed, 103 insertions(+), 45 deletions(-)
--
2.46.1
next reply other threads:[~2024-09-24 10:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 10:03 David Hildenbrand [this message]
2024-09-24 10:03 ` [PULL 1/6] virtio: kconfig: memory devices are PCI only David Hildenbrand
2024-09-24 10:03 ` [PULL 2/6] reset: Use ResetType for qemu_devices_reset() and MachineClass::reset() David Hildenbrand
2024-09-24 10:03 ` [PULL 3/6] reset: Add RESET_TYPE_WAKEUP David Hildenbrand
2024-09-24 10:03 ` [PULL 4/6] virtio-mem: Use new Resettable framework instead of LegacyReset David Hildenbrand
2024-09-24 10:03 ` [PULL 5/6] virtio-mem: Add support for suspend+wake-up with plugged memory David Hildenbrand
2024-09-24 10:03 ` [PULL 6/6] hostmem: Apply merge property after the memory region is initialized David Hildenbrand
2024-09-27 9:32 ` [PULL 0/6] Host Memory Backends and Memory devices queue 2024-09-24 Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240924100329.248738-1-david@redhat.com \
--to=david@redhat.com \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).