qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH memory v3 6/9] memory: MemoryRegion: QOMify
Date: Tue, 3 Jun 2014 08:39:56 +1000	[thread overview]
Message-ID: <CAEgOgz6UyEk6D4Eu3T6EnDF6tU5P1cok_93QUqAMkkLeCLH64Q@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9=TfeKv19ykxbkyH_NA-ryJAtCwzyP0NfKDS0fHdic3Q@mail.gmail.com>

On Mon, Jun 2, 2014 at 10:18 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 2 June 2014 05:17, Peter Crosthwaite <peter.crosthwaite@xilinx.com> wrote:
>> QOMify memory regions as an Object. The former init() and destroy()
>> routines become instance_init() and instance_finalize() resp.
>>
>> memory_region_init() is re-implemented to be:
>> object_initialize() + set fields
>
>> +static void memory_region_initfn(Object *obj)
>> +{
>> +    MemoryRegion *mr = MEMORY_REGION(obj);
>> +
>> +    mr->ops = &unassigned_mem_ops;
>>      mr->enabled = true;
>> -    mr->terminates = false;
>> -    mr->ram = false;
>>      mr->romd_mode = true;
>> -    mr->readonly = false;
>> -    mr->rom_device = false;
>>      mr->destructor = memory_region_destructor_none;
>> -    mr->priority = 0;
>> -    mr->may_overlap = false;
>> -    mr->alias = NULL;
>>      QTAILQ_INIT(&mr->subregions);
>>      memset(&mr->subregions_link, 0, sizeof mr->subregions_link);
>
> We rely on QOM objects being zero-initialized for other
> fields, so why leave the explicit memset for this one?
>

It slipped through the cracks in my scan for 0s. Will Fix.

Regards,
Peter

> thanks
> -- PMM
>

  reply	other threads:[~2014-06-02 22:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02  4:13 [Qemu-devel] [PATCH memory v3 0/9] Memory Region QOMification Peter Crosthwaite
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 [this message]
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=CAEgOgz6UyEk6D4Eu3T6EnDF6tU5P1cok_93QUqAMkkLeCLH64Q@mail.gmail.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).