From: Philippe Bergheaud <felix@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
mrochs@linux.vnet.ibm.com, manoj@linux.vnet.ibm.com,
imunsie@au1.ibm.com
Subject: Re: [v5, 1/2] cxl: Add mechanism for delivering AFU driver specific events
Date: Thu, 16 Jun 2016 15:59:15 +0200 [thread overview]
Message-ID: <5762B0B3.5030902@linux.vnet.ibm.com> (raw)
In-Reply-To: <3rVkCP66Gbz9t0G@ozlabs.org>
Michael Ellerman wrote:
> 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?
>
I am about to send a v6.
Philippe
prev parent reply other threads:[~2016-06-16 13:58 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
2016-06-16 13:59 ` Philippe Bergheaud [this message]
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=5762B0B3.5030902@linux.vnet.ibm.com \
--to=felix@linux.vnet.ibm.com \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=manoj@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=mrochs@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.