Hi Thierry,
What is the use case for the mailbox driver? What kind of entity will be
there consuming sent messages and sending messages to kernel?
--Pekka
On 10/26/2018 02:16 PM, Thierry Reding wrote:
From: Thierry Reding
Hi everyone,
this is a reworked version of Mikko's earlier proposal
Hi Thierry,
There is typically one entity (aux cpu or a VM running on CCPLEX) owning
the "empty" or producer side of mailbox (iow, waking up on empty) and
another entity owning the "full" or consumer side of mailbox (waking up
on full). An entity should not muck with the interrupts used by the
a dedicated
"shared" interrupt and disabling that in GIC could be a lighter
operation, we used to do that in Parker.
--Pekka
On 10/29/2018 12:39 PM, Thierry Reding wrote:
On Mon, Oct 29, 2018 at 12:04:22PM +0200, Pekka Pessi wrote:
Hi Thierry,
There is typically one entity (aux cpu or
errupts? How the consumer
indicates that it is interested in receiving messages? mbox_peek_data()?
--Pekka
On 10/29/2018 03:16 PM, Thierry Reding wrote:
On Mon, Oct 29, 2018 at 02:25:42PM +0200, Pekka Pessi wrote:
Hi Thierry,
From the 0/9:
Are you aware of any others that we need to tak
4 matches
Mail list logo
