From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Baumann <Andrew.Baumann@microsoft.com>,
Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: "Grégory ESTRADE" <gregory.estrade@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Jan Petrouš" <jan.petrous@tieto.com>,
"Sai Pavan Boddu" <saipava@xilinx.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-arm] [Qemu-devel] RFC: raspberry pi / pi2 / Windows-on-ARM support
Date: Thu, 26 Nov 2015 17:53:39 +0100 [thread overview]
Message-ID: <56573913.2020407@redhat.com> (raw)
In-Reply-To: <BLUPR0301MB2034372751CF518EE0A3067B9E050@BLUPR0301MB2034.namprd03.prod.outlook.com>
On 25/11/2015 19:14, Andrew Baumann wrote:
> How does this work out with object_property_add_alias? It can fail
> and returns an error, so it should be called from realize, but it
> adds a new property on the object, so the property won't be useful if
> it can only be set after realize has added it.
If you know it cannot fail, just pass &error_abort and call it from
instance_init.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Baumann <Andrew.Baumann@microsoft.com>,
Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: "Grégory ESTRADE" <gregory.estrade@gmail.com>,
"Stefan Weil" <sw@weilnetz.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Jan Petrouš" <jan.petrous@tieto.com>,
"Sai Pavan Boddu" <saipava@xilinx.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>
Subject: Re: [Qemu-devel] RFC: raspberry pi / pi2 / Windows-on-ARM support
Date: Thu, 26 Nov 2015 17:53:39 +0100 [thread overview]
Message-ID: <56573913.2020407@redhat.com> (raw)
In-Reply-To: <BLUPR0301MB2034372751CF518EE0A3067B9E050@BLUPR0301MB2034.namprd03.prod.outlook.com>
On 25/11/2015 19:14, Andrew Baumann wrote:
> How does this work out with object_property_add_alias? It can fail
> and returns an error, so it should be called from realize, but it
> adds a new property on the object, so the property won't be useful if
> it can only be set after realize has added it.
If you know it cannot fail, just pass &error_abort and call it from
instance_init.
Paolo
next prev parent reply other threads:[~2015-11-29 8:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 22:22 [Qemu-devel] RFC: raspberry pi / pi2 / Windows-on-ARM support Andrew Baumann
2015-11-17 6:01 ` Stefan Weil
2015-11-18 7:51 ` [Qemu-arm] " Peter Crosthwaite
2015-11-18 7:51 ` Peter Crosthwaite
2015-11-18 18:16 ` [Qemu-arm] " Andrew Baumann
2015-11-18 18:16 ` Andrew Baumann
2015-11-18 19:35 ` Peter Crosthwaite
2015-11-25 0:00 ` [Qemu-arm] " Andrew Baumann
2015-11-25 0:00 ` Andrew Baumann
2015-11-25 6:04 ` Peter Crosthwaite
2015-11-25 9:11 ` [Qemu-arm] " Peter Maydell
2015-11-25 9:11 ` Peter Maydell
2015-11-25 18:14 ` [Qemu-arm] " Andrew Baumann
2015-11-25 18:14 ` Andrew Baumann
2015-11-26 16:53 ` Paolo Bonzini [this message]
2015-11-26 16:53 ` Paolo Bonzini
2015-11-25 18:02 ` Andrew Baumann
2015-11-26 19:38 ` [Qemu-arm] " Peter Crosthwaite
2015-11-26 19:38 ` Peter Crosthwaite
2015-11-26 20:49 ` Andrew Baumann
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=56573913.2020407@redhat.com \
--to=pbonzini@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=crosthwaitepeter@gmail.com \
--cc=gregory.estrade@gmail.com \
--cc=jan.petrous@tieto.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=saipava@xilinx.com \
--cc=sw@weilnetz.de \
/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.