From: "Andreas Färber" <afaerber@suse.de>
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>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH: RFC] Adding BAR0 for e500 PCI controller
Date: Tue, 11 Sep 2012 14:59:26 +0200 [thread overview]
Message-ID: <504F35AE.5020105@suse.de> (raw)
In-Reply-To: <504F2E1A.8090200@suse.de>
Am 11.09.2012 14:27, schrieb Alexander Graf:
> On 09/11/2012 02:23 PM, Andreas Färber wrote:
>> For a reference to another object a QOM link<> property would be
>> preferred over a static qdev property.
>
> 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 block?
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 = 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
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-09-11 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 12:50 [Qemu-devel] [PATCH: RFC] Adding BAR0 for e500 PCI controller Bharat Bhushan
2012-08-15 1:29 ` [Qemu-devel] [Qemu-ppc] " Scott Wood
2012-08-15 2:40 ` Bhushan Bharat-R65777
2012-09-03 6:44 ` Bhushan Bharat-R65777
2012-09-06 23:15 ` Scott Wood
2012-09-07 8:08 ` Alexander Graf
2012-09-07 18:58 ` Scott Wood
2012-09-11 11:33 ` Alexander Graf
2012-09-11 19:05 ` Scott Wood
2012-09-11 20:58 ` Alexander Graf
2012-09-11 12:23 ` Andreas Färber
2012-09-11 12:27 ` Alexander Graf
2012-09-11 12:59 ` Andreas Färber [this message]
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=504F35AE.5020105@suse.de \
--to=afaerber@suse.de \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.com \
/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.