From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org, kumar.gala@freescale.com
Subject: Re: [PATCH] powerpc/fsl: add MSI support for the Freescale hypervisor
Date: Mon, 12 Dec 2011 17:52:41 -0600 [thread overview]
Message-ID: <4EE693C9.3080009@freescale.com> (raw)
In-Reply-To: <1323733052-21495-1-git-send-email-timur@freescale.com>
On 12/12/2011 05:37 PM, Timur Tabi wrote:
> @@ -205,6 +207,29 @@ static void __init setup_pci_atmu(struct pci_controller *hose,
>
> /* Setup inbound mem window */
> mem = memblock_end_of_DRAM();
> +
> + /*
> + * The msi-address-64 property, if it exists, indicates the physical
> + * address of the MSIIR register. Normally, this register is located
> + * inside CCSR, so the ATMU that covers all of CCSR is used for MSIs.
> + * But if this property exists, then we'll normally need to create a
> + * new ATMU for it. For now, however, we cheat. The only entity that
> + * creates this property is the Freescale hypervisor, and it
> + * always locates MSIIR in the page immediately after the end of DDR.
> + * So we can avoid allocating a new ATMU by just extending the DDR
> + * ATMU by one page.
> + */
Technically, it's up to the hv config file where MSIIR gets mapped.
After main memory is just a common way of configuring it, but won't work
if we're limiting the partition's memory to end at an unusual address.
Might also want to comment that the reason for this weird remapping is
hardware limitations in the IOMMU.
-Scott
next prev parent reply other threads:[~2011-12-12 23:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 23:37 [PATCH] powerpc/fsl: add MSI support for the Freescale hypervisor Timur Tabi
2011-12-12 23:52 ` Scott Wood [this message]
2011-12-13 0:27 ` Tabi Timur-B04825
2011-12-13 0:39 ` Scott Wood
2011-12-13 0:43 ` Tabi Timur-B04825
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=4EE693C9.3080009@freescale.com \
--to=scottwood@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@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 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).