[PATCH] nvme: allow lightnvm to have visibility over AER events

[sagi@grimberg.me (Sagi Grimberg)]

Javier,

>> We currently do have some logic in the core to say which events are
>> sent to user space for handling and others that are handled internally.
>> There's currently just two events with kernel specifc handling:
>> namespace inventory change, and firmware activation.
>>
>> The example in your patch looks like one of the scenarios envisioned
>> to be handled by a udev rule. Is that not going to work for you here?
>>
>> If you do have an event that needs special handling, I think you'd want
>> to filter that out of the user space notification and invoke the kernel
>> callback specific to it your event.
> 
> Can I plug a udev rule to an in-kernel driver? A concrete example of the
> events we will handle is pblk having to remap data from a chunk that is
> becoming unreliable.

You can plug user-space action and kernel interface for it. It looks
pretty stateless..

Does pblk expose a char device? I think that user-space can issue
the log page and then pass the information to the kernel..

Given that I do see also that nvmet would be a potential consumer for
AER, maybe user-space would be a good place to handle all this...