From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: David Hildenbrand <david@redhat.com>
Subject: [GIT PULL 00/12] Host Memory Backends and Memory devices queue 2023-09-19
Date: Tue, 19 Sep 2023 12:30:17 +0200 [thread overview]
Message-ID: <20230919103029.235736-1-david@redhat.com> (raw)
The following changes since commit 13d6b1608160de40ec65ae4c32419e56714bbadf:
Merge tag 'pull-crypto-20230915' of https://gitlab.com/rth7680/qemu into staging (2023-09-18 11:04:21 -0400)
are available in the Git repository at:
https://github.com/davidhildenbrand/qemu.git tags/mem-2023-09-19
for you to fetch changes up to 544cff46c018036cd66e98ffb224dd9f098065c8:
memory: avoid updating ioeventfds for some address_space (2023-09-19 10:44:44 +0200)
----------------------------------------------------------------
Hi,
"Host Memory Backends" and "Memory devices" queue ("mem"):
- Support and document VM templating with R/O files using a new "rom"
parameter for memory-backend-file
- Some cleanups and fixes around NVDIMMs and R/O file handling for guest
RAM
- Optimize ioeventfd updates by skipping address spaces that are not
applicable
----------------------------------------------------------------
David Hildenbrand (11):
nvdimm: Reject writing label data to ROM instead of crashing QEMU
softmmu/physmem: Distinguish between file access mode and mmap
protection
backends/hostmem-file: Add "rom" property to support VM templating
with R/O files
softmmu/physmem: Remap with proper protection in qemu_ram_remap()
softmmu/physmem: Bail out early in ram_block_discard_range() with
readonly files
softmmu/physmem: Fail creation of new files in file_ram_open() with
readonly=true
softmmu/physmem: Never return directories from file_ram_open()
docs: Don't mention "-mem-path" in multi-process.rst
docs: Start documenting VM templating
softmmu/physmem: Hint that "readonly=on,rom=off" exists when opening
file R/W for private mapping fails
machine: Improve error message when using default RAM backend id
hongmianquan (1):
memory: avoid updating ioeventfds for some address_space
MAINTAINERS | 1 +
backends/hostmem-file.c | 61 ++++++++++++++++-
docs/devel/multi-process.rst | 5 +-
docs/system/index.rst | 1 +
docs/system/vm-templating.rst | 125 ++++++++++++++++++++++++++++++++++
hw/acpi/nvdimm.c | 11 ++-
hw/core/machine.c | 11 ++-
hw/mem/nvdimm.c | 10 ++-
hw/ppc/spapr_nvdimm.c | 3 +-
include/exec/memory.h | 15 ++--
include/exec/ram_addr.h | 8 +--
include/hw/mem/nvdimm.h | 6 ++
qapi/qom.json | 17 ++++-
qemu-options.hx | 16 ++++-
softmmu/memory.c | 20 ++++--
softmmu/physmem.c | 93 +++++++++++++++++++------
16 files changed, 354 insertions(+), 49 deletions(-)
create mode 100644 docs/system/vm-templating.rst
--
2.41.0
next reply other threads:[~2023-09-19 10:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 10:30 David Hildenbrand [this message]
2023-09-19 10:30 ` [GIT PULL 01/12] nvdimm: Reject writing label data to ROM instead of crashing QEMU David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 02/12] softmmu/physmem: Distinguish between file access mode and mmap protection David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 03/12] backends/hostmem-file: Add "rom" property to support VM templating with R/O files David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 04/12] softmmu/physmem: Remap with proper protection in qemu_ram_remap() David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 05/12] softmmu/physmem: Bail out early in ram_block_discard_range() with readonly files David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 06/12] softmmu/physmem: Fail creation of new files in file_ram_open() with readonly=true David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 07/12] softmmu/physmem: Never return directories from file_ram_open() David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 08/12] docs: Don't mention "-mem-path" in multi-process.rst David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 09/12] docs: Start documenting VM templating David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 10/12] softmmu/physmem: Hint that "readonly=on, rom=off" exists when opening file R/W for private mapping fails David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 11/12] machine: Improve error message when using default RAM backend id David Hildenbrand
2023-09-19 10:30 ` [GIT PULL 12/12] memory: avoid updating ioeventfds for some address_space David Hildenbrand
2023-09-19 19:13 ` [GIT PULL 00/12] Host Memory Backends and Memory devices queue 2023-09-19 Stefan Hajnoczi
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=20230919103029.235736-1-david@redhat.com \
--to=david@redhat.com \
--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).