From: Michael Ellerman <mpe@ellerman•id.au>
To: Philippe Bergheaud <felix@linux•vnet.ibm.com>,
linuxppc-dev@lists•ozlabs.org
Cc: mikey@neuling•org, mrochs@linux•vnet.ibm.com,
manoj@linux•vnet.ibm.com, imunsie@au1•ibm.com,
Philippe Bergheaud <felix@linux•vnet.ibm.com>
Subject: Re: [v5, 1/2] cxl: Add mechanism for delivering AFU driver specific events
Date: Thu, 16 Jun 2016 23:05:53 +1000 (AEST) [thread overview]
Message-ID: <3rVkCP66Gbz9t0G@ozlabs.org> (raw)
In-Reply-To: <1464007742-1941-1-git-send-email-felix@linux.vnet.ibm.com>
On Mon, 2016-23-05 at 12:49:01 UTC, Philippe Bergheaud wrote:
> This adds an afu_driver_ops structure with deliver_event() and
> event_delivered() callbacks. An AFU driver such as cxlflash can fill
> this out and associate it with a context to enable passing custom
> AFU specific events to userspace.
>
> This also adds a new kernel API function cxl_context_pending_events(),
> that the AFU driver can use to notify the cxl driver that new specific
> events are ready to be delivered, and wake up anyone waiting on the
> context wait queue.
...
>
> Signed-off-by: Philippe Bergheaud <felix@linux•vnet.ibm.com>
It looks like the discussion has settled down on this one, and everyone was OK
with it, except maybe the naming?
So can we either get some ACKs, or a v6 with new naming?
cheers
next prev parent reply other threads:[~2016-06-16 13:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 12:49 [v5, 1/2] cxl: Add mechanism for delivering AFU driver specific events Philippe Bergheaud
2016-05-23 12:49 ` [v4,2/2] cxl: Add set and get private data to context struct Philippe Bergheaud
2016-05-24 6:59 ` [v5, 1/2] cxl: Add mechanism for delivering AFU driver specific events Vaibhav Jain
2016-05-24 14:44 ` Matthew R. Ochs
2016-05-25 7:22 ` Vaibhav Jain
2016-06-14 14:47 ` Matthew R. Ochs
2016-06-14 15:21 ` Matthew R. Ochs
2016-06-16 13:05 ` Michael Ellerman [this message]
2016-06-16 13:59 ` Philippe Bergheaud
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=3rVkCP66Gbz9t0G@ozlabs.org \
--to=mpe@ellerman$(echo .)id.au \
--cc=felix@linux$(echo .)vnet.ibm.com \
--cc=imunsie@au1$(echo .)ibm.com \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=manoj@linux$(echo .)vnet.ibm.com \
--cc=mikey@neuling$(echo .)org \
--cc=mrochs@linux$(echo .)vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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