Thread (19 messages) 19 messages, 8 authors, 2011-02-16

Re: [RFC] Inter-processor Mailboxes Drivers

flat view

From: Blanchard, Hollis <hidden>
Date: 2011-02-15 23:38:25
Also in: linux-arm-kernel

On 02/15/2011 01:58 PM, Meador Inge wrote:
On 02/14/2011 04:01 AM, Jamie Iles wrote:
quoted
On Fri, Feb 11, 2011 at 03:19:51PM -0600, Meador Inge wrote:
quoted
     1. Hardware specific bits somewhere under '.../arch/*'.  =
Drivers
quoted
quoted
        for the MPIC message registers on Power and OMAP4 mailboxes, =
quoted
quoted
for
        example.
     2. A higher level driver under '.../drivers/mailbox/*'.  That =
the
quoted
quoted
        pieces in (1) would register with.  This piece would expose =
the
quoted
quoted
        main kernel API.
     3. Userspace interfaces for accessing the mailboxes.  A
        '/dev/mailbox1', '/dev/mailbox2', etc... mapping, for =
example.
quoted
How about using virtio for all of this and having the mailbox as a
notification/message passing driver for the virtio backend?  There =
are
quoted
already virtio console and network drivers that could be useful for =
the
quoted
userspace part of it.  drivers/virtio/virtio_ring.c might be a good
starting point if you thought there was some mileage in this =
approach.
To be honest, I am not that familiar with 'virtio', but I will take a=20
look.  Thanks for the pointer.  Maybe Hollis can speak to this idea =
more.
My opinion is that virtio is (over?) complicated.

I've looked into it in the past, and I'm definitely open to using it if=20
somebody can demonstrate how easy it is, but adopting it wouldn't have=20
helped OpenMCAPI with our use cases, and would have incurred extra pain, =

so we didn't.

Hollis Blanchard
Mentor Graphics, Embedded Systems Division
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help