From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:49687)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1ScyR6-00075y-Pg
	for qemu-devel@nongnu.org; Fri, 08 Jun 2012 08:37:06 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1ScyR0-0005g3-E6
	for qemu-devel@nongnu.org; Fri, 08 Jun 2012 08:37:04 -0400
Received: from david.siemens.de ([192.35.17.14]:26900)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jan.kiszka@siemens.com>) id 1ScyR0-0005fn-3Z
	for qemu-devel@nongnu.org; Fri, 08 Jun 2012 08:36:58 -0400
Message-ID: <4FD1F1E5.5090501@siemens.com>
Date: Fri, 08 Jun 2012 14:36:53 +0200
From: Jan Kiszka <jan.kiszka@siemens.com>
MIME-Version: 1.0
References: <1337742502-28565-1-git-send-email-afaerber@suse.de>
	<1337742502-28565-5-git-send-email-afaerber@suse.de>
	<20120608082006.GA22512@thinkpad.mammed.net>
	<4FD1C1AF.2020208@suse.de>
	<20120608120508.GC22512@thinkpad.mammed.net>
	<4FD1F160.9050402@suse.de>
In-Reply-To: <4FD1F160.9050402@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH qom-next 04/59] pc: Add CPU as
	/machine/cpu[n]
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Igor Mammedov <niallain@gmail.com>, Paolo Bonzini <pbonzini@redhat.com>

On 2012-06-08 14:34, Andreas F=E4rber wrote:
> Am 08.06.2012 14:05, schrieb Igor Mammedov:
>> On Fri, Jun 08, 2012 at 11:11:11AM +0200, Andreas F=E4rber wrote:
>>> Another factor that is making this slightly difficult is that there a=
re
>>> three APIC subclasses. Currently they all have an instance_size of
>>> sizeof(APICCommonState) so it could be created in-place if it actuall=
y
>>> is a part (child<>) of the CPU wrt hot-plug. Creating objects with
>>> object_new() in QOM instance_init is forbidden.
>> Any particular reason why object_new() in intifn is not acceptable?
>=20
> It allocates memory, which may fail. The initfn must not fail, the
> realizefn may return an Error object.

Since when do we fail gracefully on OOM again?

Jan

--=20
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux