From: Scott Wood <scottwood@freescale.com>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
Gala Kumar-B11780 <B11780@freescale.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/fsl: add MSI support for the Freescale hypervisor
Date: Mon, 12 Dec 2011 18:39:45 -0600 [thread overview]
Message-ID: <4EE69ED1.6040302@freescale.com> (raw)
In-Reply-To: <4EE69BEB.8020208@freescale.com>
On 12/12/2011 06:27 PM, Tabi Timur-B04825 wrote:
> Scott Wood wrote:
>> 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.
>
> I'll change the comment to reflect this.
>
> Why can't we have the hypervisor always put MSIIR at the end of DDR, and
> not make it configurable?
"...but won't work if we're limiting the partition's memory to end at an
unusual address." We have to live with PAMU's iova limitations. PAMU
setup is user-controlled in general under Topaz.
How's the hypervisor even going to know if the mem= kernel command line
argument is used to change the end of main memory (assuming that's been
taken into account by this point in the boot sequence)?
What if the user put a shared memory region immediately after the main
partition memory?
-Scott
next prev parent reply other threads:[~2011-12-13 0:39 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
2011-12-13 0:27 ` Tabi Timur-B04825
2011-12-13 0:39 ` Scott Wood [this message]
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=4EE69ED1.6040302@freescale.com \
--to=scottwood@freescale.com \
--cc=B04825@freescale.com \
--cc=B07421@freescale.com \
--cc=B11780@freescale.com \
--cc=linuxppc-dev@ozlabs.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).