From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:57517)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1TBQ43-0005Ll-V7
	for qemu-devel@nongnu.org; Tue, 11 Sep 2012 08:59:45 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1TBQ3u-0005ez-Gt
	for qemu-devel@nongnu.org; Tue, 11 Sep 2012 08:59:39 -0400
Message-ID: <504F35AE.5020105@suse.de>
Date: Tue, 11 Sep 2012 14:59:26 +0200
From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1344948607-23291-1-git-send-email-Bharat.Bhushan@freescale.com>
	<502AFB70.2070101@freescale.com>
	<6A3DF150A5B70D4F9B66A25E3F7C888D06453361@039-SN2MPN1-022.039d.mgd.msft.net>
	<50492EA9.3050605@freescale.com>
	<C0C007E9-E2CF-4185-9D8E-1AB7C06599C4@suse.de>
	<504A43EC.6030004@freescale.com> <504F2D41.6000404@suse.de>
	<504F2E1A.8090200@suse.de>
In-Reply-To: <504F2E1A.8090200@suse.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH: RFC] Adding BAR0 for e500 PCI
 controller
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: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>, Wood Scott-B07421 <B07421@freescale.com>, "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, Bhushan Bharat-R65777 <R65777@freescale.com>

Am 11.09.2012 14:27, schrieb Alexander Graf:
> On 09/11/2012 02:23 PM, Andreas F=C3=A4rber wrote:
>> For a reference to another object a QOM link<> property would be
>> preferred over a static qdev property.
>=20
> How does that work? Can we do RPC to other objects to access its CCSR
> and/or enumerate the CCSR size? Or maybe even receive its memory api bl=
ock?

What I had in mind was something like:

typedef struct CCSRState {
    Object *parent; /* or DeviceState or whatever */

    MemoryRegion *ccsr_region;
} CCSRState;

#define CCSR(obj) OBJECT_CHECK(CCSRState, (obj), TYPE_CCSR)

MemoryRegion pci_ccsr_region;
CCSRState *ccsr =3D CCSR(pointer_from_link_property_or_path);

memory_region_init_alias(&pci_ccsr_region, "pci-ccsr",
ccsr->ccsr_region, 0, memory_region_size(ccsr->ccsr_region));

Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=C3=B6rffer; HRB 16746 AG N=C3=BC=
rnberg