qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, afaerber@suse.de, peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH memory v3 0/9]  Memory Region QOMification
Date: Sun,  1 Jun 2014 21:13:59 -0700	[thread overview]
Message-ID: <cover.1401681566.git.peter.crosthwaite@xilinx.com> (raw)

Hi Paolo, Andreas,

This patch series QOMifies Memory regions. This is the Memory API
specific subset of patches forming part of the Memory/GPIO/Sysbus
QOMification.

I think Paolo already has P1 enqeued. Including for ease of review.
some QOM patches in P2-3 that cut down on later boilerplate. TBH I can
live without them, if they not liked but they make life better IMO.

For fuller context please see:

http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg03265.html

Changed since v2:
Use object unref to finalize MR (Paolo review)
Fixed priority prop getter
Changed prioirty to signed type in QOM getters/setterts
Changed since v1:
Split into subset series.
Converted container link into low level link.
Misc finer tweaks and patch re-orderings.


Peter Crosthwaite (9):
  memory: Simplify mr_add_subregion() if-else
  qom: object: Ignore refs/unrefs of NULL
  qom: Publish object_resolve_link
  memory: Coreify subregion add functionality
  memory: MemoryRegion: factor out memory region re-adder
  memory: MemoryRegion: QOMify
  memory: MemoryRegion: Add container and addr props
  memory: MemoryRegion: Add may-overlap and priority props
  memory: MemoryRegion: Add size property

 include/exec/memory.h |   8 +-
 include/qom/object.h  |  16 +++
 memory.c              | 307 +++++++++++++++++++++++++++++++++++++++++++-------
 qom/object.c          |  27 ++---
 4 files changed, 298 insertions(+), 60 deletions(-)

-- 
2.0.0

             reply	other threads:[~2014-06-02  4:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  4:13 Peter Crosthwaite [this message]
2014-06-02  4:14 ` [Qemu-devel] [PATCH memory v3 1/9] memory: Simplify mr_add_subregion() if-else Peter Crosthwaite
2014-06-02  4:15 ` [Qemu-devel] [PATCH memory v3 2/9] qom: object: Ignore refs/unrefs of NULL Peter Crosthwaite
2014-06-02  4:15 ` [Qemu-devel] [PATCH memory v3 3/9] qom: Publish object_resolve_link Peter Crosthwaite
2014-06-02  4:16 ` [Qemu-devel] [PATCH memory v3 4/9] memory: Coreify subregion add functionality Peter Crosthwaite
2014-06-02  4:16 ` [Qemu-devel] [PATCH memory v3 5/9] memory: MemoryRegion: factor out memory region re-adder Peter Crosthwaite
2014-06-02  4:17 ` [Qemu-devel] [PATCH memory v3 6/9] memory: MemoryRegion: QOMify Peter Crosthwaite
2014-06-02 12:18   ` Peter Maydell
2014-06-02 22:39     ` Peter Crosthwaite
2014-06-02  4:17 ` [Qemu-devel] [PATCH memory v3 7/9] memory: MemoryRegion: Add container and addr props Peter Crosthwaite
2014-06-02  4:18 ` [Qemu-devel] [PATCH memory v3 8/9] memory: MemoryRegion: Add may-overlap and priority props Peter Crosthwaite
2014-06-02  4:19 ` [Qemu-devel] [PATCH memory v3 9/9] memory: MemoryRegion: Add size property Peter Crosthwaite
2014-06-02 14:26 ` [Qemu-devel] [PATCH memory v3 0/9] Memory Region QOMification Peter Maydell
2014-06-02 22:37   ` Peter Crosthwaite

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.1401681566.git.peter.crosthwaite@xilinx.com \
    --to=peter.crosthwaite@xilinx.com \
    --cc=afaerber@suse.de \
    --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).