From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: 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] [PATCH 2/2] Adding BAR0 for e500 PCI controller
Date: Thu, 04 Oct 2012 19:02:28 +0200 [thread overview]
Message-ID: <506DC124.60508@redhat.com> (raw)
In-Reply-To: <CE55DB7B-FE14-486D-BFE0-AEAAD1840AB5@suse.de>
On 10/04/2012 06:50 PM, Alexander Graf wrote:
>>>
>>> No, it also meets (2). The PCI address space is identical to the CPU memory
>>> space in our mapping right now. So if the guest maps BAR0 somewhere, it
>>> automatically maps CCSR into CPU address space, which exposes it to PCI address
>>> space.
>>
>> Really? I think on powerpc the pci address space is defined as: it maps the outbound window just below 0x1_0000_0000, then CCSR and then inbound window. So inbound window is 1:1 map if guest physical starts from 0x0. But I do not think CCSR is 1:1 map in pci address space and cpu address space.
>
> In QEMU, we map everything 1:1 today.
An unmerged patch set entitled "Integrate DMA into the memory API"
changes that. I'll be happy to work with you to make use of it to
emulate the hardware properly, it will give me a nice test case.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-04 17:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 11:49 [Qemu-devel] [PATCH 0/2] e500: creating CCSR region and registering bar0 Bharat Bhushan
2012-10-03 11:49 ` [Qemu-devel] [PATCH 1/2] e500: Adding CCSR memory region Bharat Bhushan
2012-10-03 12:08 ` Alexander Graf
2012-10-03 12:16 ` Bhushan Bharat-R65777
2012-10-03 12:18 ` Alexander Graf
2012-10-03 11:50 ` [Qemu-devel] [PATCH 2/2] Adding BAR0 for e500 PCI controller Bharat Bhushan
2012-10-03 12:11 ` Alexander Graf
2012-10-03 12:23 ` Bhushan Bharat-R65777
2012-10-04 12:31 ` Avi Kivity
2012-10-04 13:46 ` Bhushan Bharat-R65777
2012-10-04 14:58 ` Avi Kivity
2012-10-04 16:03 ` Bhushan Bharat-R65777
2012-10-04 16:07 ` Alexander Graf
2012-10-04 16:48 ` Bhushan Bharat-R65777
2012-10-04 16:50 ` Alexander Graf
2012-10-04 17:02 ` Avi Kivity [this message]
2012-10-05 7:11 ` Bhushan Bharat-R65777
2012-10-05 11:59 ` Alexander Graf
2012-10-07 9:48 ` Avi Kivity
2012-10-07 11:57 ` Alexander Graf
2012-10-07 12:41 ` Avi Kivity
2012-10-08 8:23 ` Bhushan Bharat-R65777
2012-10-08 8:50 ` Alexander Graf
2012-10-08 13:57 ` Andreas Färber
2012-10-04 15:54 ` Andreas Färber
2012-10-04 16:01 ` Alexander Graf
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=506DC124.60508@redhat.com \
--to=avi@redhat.com \
--cc=B07421@freescale.com \
--cc=R65777@freescale.com \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).