qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH memory v4 00/10] Memory Region QOMification
Date: Fri, 06 Jun 2014 11:36:28 +0200	[thread overview]
Message-ID: <53918B9C.4080408@redhat.com> (raw)
In-Reply-To: <cover.1402034413.git.peter.crosthwaite@xilinx.com>

Il 06/06/2014 08:11, Peter Crosthwaite ha scritto:
> 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-4 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
>
> and
>
> http://lists.gnu.org/archive/html/qemu-devel/2014-06/msg00359.html

I'm okay with the gist of the series.  I still have to understand how 
exactly the reference counts work, but the idea is fine.

However, I'd rather have the concept bake for a bit by starting with 
read-only properties.  I think there are some concepts in the 
"container" property that can be generalized.

Would you be okay with that?

Paolo

  parent reply	other threads:[~2014-06-06  9:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-06  6:11 [Qemu-devel] [PATCH memory v4 00/10] Memory Region QOMification Peter Crosthwaite
2014-06-06  6:12 ` [Qemu-devel] [PATCH memory v4 01/10] memory: Simplify mr_add_subregion() if-else Peter Crosthwaite
2014-06-06  6:13 ` [Qemu-devel] [PATCH memory v4 02/10] qom: add a generic mechanism to resolve paths Peter Crosthwaite
2014-06-06  6:13 ` [Qemu-devel] [PATCH memory v4 03/10] qom: object: Ignore refs/unrefs of NULL Peter Crosthwaite
2014-06-06  6:14 ` [Qemu-devel] [PATCH memory v4 04/10] qom: Publish object_resolve_link Peter Crosthwaite
2014-06-06  6:14 ` [Qemu-devel] [PATCH memory v4 05/10] memory: Coreify subregion add functionality Peter Crosthwaite
2014-06-06  6:15 ` [Qemu-devel] [PATCH memory v4 06/10] memory: MemoryRegion: factor out memory region re-adder Peter Crosthwaite
2014-06-06  6:15 ` [Qemu-devel] [PATCH memory v4 07/10] memory: MemoryRegion: QOMify Peter Crosthwaite
2014-06-06  6:16 ` [Qemu-devel] [PATCH memory v4 08/10] memory: MemoryRegion: Add container and addr props Peter Crosthwaite
2014-06-06  6:17 ` [Qemu-devel] [PATCH memory v4 09/10] memory: MemoryRegion: Add may-overlap and priority props Peter Crosthwaite
2014-06-06  6:17 ` [Qemu-devel] [PATCH memory v4 10/10] memory: MemoryRegion: Add size property Peter Crosthwaite
2014-06-06  9:36 ` Paolo Bonzini [this message]
2014-06-06 13:36   ` [Qemu-devel] [PATCH memory v4 00/10] Memory Region QOMification Peter Crosthwaite
2014-06-06 14:52     ` Paolo Bonzini
2014-06-06 23:50       ` Peter Crosthwaite
2014-06-07 11:30         ` Paolo Bonzini

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=53918B9C.4080408@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=peter.crosthwaite@xilinx.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).