From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: Kushwaha Prabhakar-B32579 <B32579@freescale.com>
Cc: Meador Inge <meador_inge@mentor.com>,
"openmcapi-dev@googlegroups.com" <openmcapi-dev@googlegroups.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] powerpc: add support for MPIC message register API
Date: Fri, 29 Apr 2011 09:54:53 -0700 [thread overview]
Message-ID: <4DBAED5D.4060906@mentor.com> (raw)
In-Reply-To: <071A08F2C6A57E4E94D980ECA553F8741959CA@039-SN1MPN1-004.039d.mgd.msft.net>
On 04/28/2011 10:00 PM, Kushwaha Prabhakar-B32579 wrote:
> Hi,
>
> I have no comments about coding and architecture. It looks fine.
>
> Only have a query about its use case..
> "Any application intended to use message interrupt requires to know reg_num because of struct mpic_msgr* mpic_msgr_get(unsigned int reg_num) API"
>
> It will be good to search available unit internally and provide its pointer. It will make application more flexible.
>
The problem is that you fundamentally cannot implement an allocator for
MSG registers if you're going to communicate with another kernel (how
would both kernels' allocators be synchronized?). So the message
register allocation must be decided at design time, not run time.
Hollis Blanchard
Mentor Graphics, Embedded Systems Division
next prev parent reply other threads:[~2011-04-29 16:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 16:59 [PATCH 0/2] powerpc: define and implement MPIC message register support Meador Inge
2011-04-19 16:59 ` [PATCH 1/2] powerpc: document the FSL MPIC message register binding Meador Inge
2011-04-19 17:52 ` Scott Wood
2011-04-19 18:26 ` Meador Inge
2011-04-19 18:33 ` Scott Wood
2011-04-21 19:26 ` Meador Inge
2011-04-21 19:35 ` Scott Wood
2011-04-19 16:59 ` [PATCH 2/2] powerpc: add support for MPIC message register API Meador Inge
2011-04-29 5:00 ` Kushwaha Prabhakar-B32579
2011-04-29 16:54 ` Hollis Blanchard [this message]
2011-04-29 17:27 ` Kushwaha Prabhakar-B32579
2011-04-29 17:30 ` Scott Wood
2011-05-02 3:41 ` Kushwaha Prabhakar-B32579
2011-05-02 16:03 ` Hollis Blanchard
2011-05-03 15:19 ` Scott Wood
2011-05-05 21:41 ` Meador Inge
2011-05-06 19:29 ` Scott Wood
2011-05-06 23:51 ` Meador Inge
2012-02-17 2:49 [PATCH 1/2] powerpc: document the FSL MPIC message register binding Jia Hongtao
2012-02-17 2:49 ` [PATCH 2/2] powerpc: add support for MPIC message register API Jia Hongtao
2012-03-21 17:21 ` Kumar Gala
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=4DBAED5D.4060906@mentor.com \
--to=hollis_blanchard@mentor.com \
--cc=B32579@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=meador_inge@mentor.com \
--cc=openmcapi-dev@googlegroups.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).