From: Peter Xu <peterx@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"David Hildenbrand" <david@redhat.com>,
peterx@redhat.com, "Daniel P . Berrangé" <berrange@redhat.com>
Subject: [PULL v2 00/14] Mem next patches
Date: Wed, 12 Feb 2025 12:38:21 -0500 [thread overview]
Message-ID: <20250212173823.214429-1-peterx@redhat.com> (raw)
The following changes since commit ffaf7f0376f8040ce9068d71ae9ae8722505c42e:
Merge tag 'pull-10.0-testing-and-gdstub-updates-100225-1' of https://gitlab.com/stsquad/qemu into staging (2025-02-10 13:26:17 -0500)
are available in the Git repository at:
https://gitlab.com/peterx/qemu.git tags/mem-next-pull-request
for you to fetch changes up to 13057e064a3edae7abf9ca2c207cdf48b82c5aad:
overcommit: introduce mem-lock=on-fault (2025-02-12 11:36:13 -0500)
----------------------------------------------------------------
Memory pull request for 10.0
v2 changelog:
- Fix Mac (and possibly some other) build issues for two patches
- os: add an ability to lock memory on_fault
- memory: pass MemTxAttrs to memory_access_is_direct()
List of features:
- William's fix on ram hole punching when with file offset
- Daniil's patchset to introduce mem-lock=on-fault
- William's hugetlb hwpoison fix for size report & remap
- David's series to allow qemu debug writes to MMIOs
----------------------------------------------------------------
Daniil Tatianin (4):
os: add an ability to lock memory on_fault
system/vl: extract overcommit option parsing into a helper
system: introduce a new MlockState enum
overcommit: introduce mem-lock=on-fault
David Hildenbrand (7):
physmem: factor out memory_region_is_ram_device() check in
memory_access_is_direct()
physmem: factor out RAM/ROMD check in memory_access_is_direct()
physmem: factor out direct access check into
memory_region_supports_direct_access()
physmem: disallow direct access to RAM DEVICE in
address_space_write_rom()
memory: pass MemTxAttrs to memory_access_is_direct()
hmp: use cpu_get_phys_page_debug() in hmp_gva2gpa()
physmem: teach cpu_memory_rw_debug() to write to more memory regions
William Roche (3):
system/physmem: take into account fd_offset for file fallocate
system/physmem: handle hugetlb correctly in qemu_ram_remap()
system/physmem: poisoned memory discard on reboot
meson.build | 6 ++
include/exec/cpu-common.h | 2 +-
include/exec/memattrs.h | 5 +-
include/exec/memory.h | 35 ++++++++---
include/system/os-posix.h | 2 +-
include/system/os-win32.h | 2 +-
include/system/system.h | 12 +++-
accel/kvm/kvm-all.c | 2 +-
hw/core/cpu-system.c | 13 ++--
hw/core/loader.c | 2 +-
hw/remote/vfio-user-obj.c | 2 +-
hw/virtio/virtio-mem.c | 2 +-
migration/postcopy-ram.c | 4 +-
monitor/hmp-cmds-target.c | 3 +-
os-posix.c | 15 ++++-
system/globals.c | 12 +++-
system/physmem.c | 121 ++++++++++++++++++++++++--------------
system/vl.c | 52 ++++++++++++----
system/memory_ldst.c.inc | 18 +++---
hw/display/apple-gfx.m | 3 +-
qemu-options.hx | 14 +++--
21 files changed, 229 insertions(+), 98 deletions(-)
--
2.47.0
next reply other threads:[~2025-02-12 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 17:38 Peter Xu [this message]
2025-02-12 17:38 ` [PULL v2 06/14] memory: pass MemTxAttrs to memory_access_is_direct() Peter Xu
2025-02-12 17:38 ` [PULL v2 11/14] os: add an ability to lock memory on_fault Peter Xu
2025-02-12 17:48 ` Daniel P. Berrangé
2025-02-12 17:56 ` Peter Xu
2025-02-12 18:03 ` Daniel P. Berrangé
2025-02-12 21:33 ` Peter Xu
2025-02-18 16:36 ` Daniel P. Berrangé
2025-02-18 22:06 ` Peter Xu
2025-02-19 2:48 ` [PULL v2 00/14] Mem next patches 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=20250212173823.214429-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=berrange@redhat.com \
--cc=david@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).