From: Ohad Ben-Cohen <ohad@wizery.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Meador Inge <meador_inge@mentor.com>,
Hiroshi DOYU <Hiroshi.DOYU@nokia.com>,
"Blanchard, Hollis" <Hollis_Blanchard@mentor.com>,
openmcapi-dev@googlegroups.com, linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] Inter-processor Mailboxes Drivers
Date: Mon, 14 Feb 2011 12:03:59 +0200 [thread overview]
Message-ID: <AANLkTinu9VMuFgHeFZGXptDYZyJL6P4qxAA9MA8UewpU@mail.gmail.com> (raw)
In-Reply-To: <20110214100104.GC4371@pulham.picochip.com>
On Mon, Feb 14, 2011 at 12:01 PM, Jamie Iles <jamie@jamieiles.com> wrote:
> On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
>> =A0 =A0 1. Hardware specific bits somewhere under '.../arch/*'. =A0Drive=
rs
>> =A0 =A0 =A0 =A0for the MPIC message registers on Power and OMAP4 mailbox=
es, for
>> =A0 =A0 =A0 =A0example.
>> =A0 =A0 2. A higher level driver under '.../drivers/mailbox/*'. =A0That =
the
>> =A0 =A0 =A0 =A0pieces in (1) would register with. =A0This piece would ex=
pose the
>> =A0 =A0 =A0 =A0main kernel API.
>> =A0 =A0 3. Userspace interfaces for accessing the mailboxes. =A0A
>> =A0 =A0 =A0 =A0'/dev/mailbox1', '/dev/mailbox2', etc... mapping, for exa=
mple.
>
> How about using virtio for all of this and having the mailbox as a
> notification/message passing driver for the virtio backend?
This is exactly what we are doing now, and it looks promising. expect
patches soon.
next prev parent reply other threads:[~2011-02-14 10:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 21:19 [RFC] Inter-processor Mailboxes Drivers Meador Inge
2011-02-12 6:28 ` Sundar
2011-02-13 21:16 ` Linus Walleij
2011-02-14 7:32 ` Hiroshi DOYU
2011-02-14 8:39 ` Linus Walleij
2011-02-14 8:55 ` Hiroshi DOYU
2011-02-14 9:00 ` Linus Walleij
2011-02-14 9:06 ` Hiroshi DOYU
2011-02-13 21:24 ` Linus Walleij
2011-02-14 23:05 ` Blanchard, Hollis
2011-02-16 21:54 ` Linus Walleij
2011-02-14 7:21 ` Hiroshi DOYU
2011-02-14 10:01 ` Jamie Iles
2011-02-14 10:03 ` Ohad Ben-Cohen [this message]
2011-02-14 16:53 ` Ira W. Snyder
2011-02-15 21:58 ` Meador Inge
2011-02-15 23:38 ` Blanchard, Hollis
2011-02-16 6:22 ` Hiroshi DOYU
2011-02-16 20:22 ` [openmcapi-dev] " Blanchard, Hollis
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=AANLkTinu9VMuFgHeFZGXptDYZyJL6P4qxAA9MA8UewpU@mail.gmail.com \
--to=ohad@wizery.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=Hollis_Blanchard@mentor.com \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.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).