All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: qemu-devel@nongnu.org
Cc: "Peter Xu" <peterx@redhat.com>,
	"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Max Filippov" <jcmvbkbc@gmail.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v2 0/7] memory: Remove most _nomigrate variants
Date: Mon, 02 Feb 2026 15:28:11 +0100 (CET)	[thread overview]
Message-ID: <cover.1770042013.git.balaton@eik.bme.hu> (raw)

v2 of the memory region API clean ups. The _nomigrate variants are
rarely needed, some of them are already unused so remove them
standardising on memory_region_init_ram_flags_nomigrate() for the few
cases where this is really needed. The Sun machines are kept to use
global vmstate and added a few more clean up patches from my previous
series.

BALATON Zoltan (7):
  memory: Remove memory_region_init_rom_device_nomigrate()
  hw/display/{cg3,tcx}: Do not use memory_region_init_rom_nomigrate()
  memory: Remove memory_region_init_rom_nomigrate()
  memory: Remove memory_region_init_ram_nomigrate()
  memory: Add internal memory_region_set_ops helper function
  memory: Factor out common ram region initialization
  memory: Add internal memory_region_register_ram function

 docs/devel/memory.rst                         |  10 +-
 hw/display/cg3.c                              |   6 +-
 hw/display/tcx.c                              |  11 +-
 hw/display/vga.c                              |   4 +-
 hw/sparc/sun4m.c                              |  15 +-
 hw/sparc64/sun4u.c                            |   9 +-
 hw/xtensa/xtfpga.c                            |   4 +-
 include/system/memory.h                       |  76 -----
 .../memory-region-housekeeping.cocci          |  42 +--
 system/memory.c                               | 271 ++++++------------
 10 files changed, 114 insertions(+), 334 deletions(-)

-- 
2.41.3



             reply	other threads:[~2026-02-02 14:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-02 14:28 BALATON Zoltan [this message]
2026-02-02 14:28 ` [PATCH v2 1/7] memory: Remove memory_region_init_rom_device_nomigrate() BALATON Zoltan
2026-02-02 14:28 ` [PATCH v2 2/7] hw/display/{cg3,tcx}: Do not use memory_region_init_rom_nomigrate() BALATON Zoltan
2026-02-02 19:33   ` Mark Cave-Ayland
2026-02-02 14:28 ` [PATCH v2 3/7] memory: Remove memory_region_init_rom_nomigrate() BALATON Zoltan
2026-02-02 14:28 ` [PATCH v2 4/7] memory: Remove memory_region_init_ram_nomigrate() BALATON Zoltan
2026-02-02 14:28 ` [PATCH v2 5/7] memory: Add internal memory_region_set_ops helper function BALATON Zoltan
2026-02-02 15:30   ` Philippe Mathieu-Daudé
2026-02-02 14:28 ` [PATCH v2 6/7] memory: Factor out common ram region initialization BALATON Zoltan
2026-02-04 20:59   ` Peter Xu
2026-02-02 14:28 ` [PATCH v2 7/7] memory: Add internal memory_region_register_ram function BALATON Zoltan

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=cover.1770042013.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=jcmvbkbc@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=philmd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.