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>,
	"Max Filippov" <jcmvbkbc@gmail.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PATCH v5 0/7] Implement memory_region_new_* functions
Date: Mon, 25 May 2026 17:47:44 +0200 (CEST)	[thread overview]
Message-ID: <cover.1779723483.git.balaton@eik.bme.hu> (raw)

Allow creating memory regions that are managed by QOM and freed with
their owner as it is already documented and implemented but there was
no way to use it.

v5:
- rebase on master
- add patch to export memory_region_set_ops (needed for ati-vga endian
switch)

v4:
- rebase on latest version of clean up series:
Based-on: cover.1772924151.git.balaton@eik.bme.hu

v3:
- based on split off clean up series
- convert xtfpga from nomigrate as this has no migration compatibility
issue

v2:
- rebase on master
- update documentation
- use these function to fix some leaks (there may be more, e.g. in
hw/pci-host/bonito but I leave that for later and/or others)

BALATON Zoltan (7):
  memory: Export memory_region_set_ops()
  memory: Add memory_region_new* functions
  memory: Update documentation for memory_region_new*()
  hw/ide/sii3112: Use memory_region_new to avoid leaking regions
  hw/pci-host/articia: Map PCI memory windows in realize
  hw/pci-host/articia: Add variable for common type cast
  hw/xtensa/xtfpga: Fix leaking memory region

 docs/devel/memory.rst   |  21 ++---
 hw/ide/sii3112.c        |  30 +++----
 hw/pci-host/articia.c   |  22 +++--
 hw/ppc/amigaone.c       |  28 ++----
 hw/ppc/pegasos.c        |  13 ---
 hw/xtensa/xtfpga.c      |   5 +-
 include/system/memory.h | 192 ++++++++++++++++++++++++++++++++++++++++
 system/memory.c         | 186 +++++++++++++++++++++++++++++++++++++-
 8 files changed, 421 insertions(+), 76 deletions(-)

-- 
2.41.3



             reply	other threads:[~2026-05-25 15:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 15:47 BALATON Zoltan [this message]
2026-05-25 15:47 ` [PATCH v5 1/7] memory: Export memory_region_set_ops() BALATON Zoltan
2026-05-25 20:01   ` Peter Maydell
2026-05-25 20:57     ` BALATON Zoltan
2026-05-28 13:39       ` Peter Xu
2026-05-25 15:47 ` [PATCH v5 2/7] memory: Add memory_region_new* functions BALATON Zoltan
2026-05-25 15:47 ` [PATCH v5 3/7] memory: Update documentation for memory_region_new*() BALATON Zoltan
2026-05-25 15:47 ` [PATCH v5 4/7] hw/ide/sii3112: Use memory_region_new to avoid leaking regions BALATON Zoltan
2026-05-25 15:47 ` [PATCH v5 5/7] hw/pci-host/articia: Map PCI memory windows in realize BALATON Zoltan
2026-05-25 15:47 ` [PATCH v5 6/7] hw/pci-host/articia: Add variable for common type cast BALATON Zoltan
2026-05-25 15:47 ` [PATCH v5 7/7] hw/xtensa/xtfpga: Fix leaking memory region BALATON Zoltan
2026-05-25 16:06 ` [PATCH v5 0/7] Implement memory_region_new_* functions Paolo Bonzini
2026-05-25 16:58   ` 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.1779723483.git.balaton@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=jcmvbkbc@gmail.com \
    --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.