Re: [RFC PATCH v2 00/13] SCMI Notifications Core Support
From: Cristian Marussi
Date: Wed Feb 19 2020 - 12:43:43 EST
Hi Jim
and thanks for the feedback first of all.
On 18/02/2020 20:19, Jim Quinlan wrote:
> Hi Cristian,
>
> This looks very robust and general but I'm wondering about the
> "notification -> user" latency. It appears there are at least five or
> so memcpy()s of the notification message as it works its way to the
> user, and added to that is the work queue deferral latency. Is there
> a concern on your end for low latency notifications, perhaps for
> emergency notifications or do you consider this to be quick enough?
>
I have to say user-latency was a primary concern when I first started
looking into this, so that at first I had thought about exposing a
dedicated additional method to let the users register callbacks which
would have been called straight away from the RX ISR using an
atomic notification chain.
Reasoning about that, though:
- me being really nervous about letting users register something that I'm
going to call on behalf of them in atomic context (...not bold enough I know :D)
since can potentially be misused and cause slowdowns to the notification
delivery or to the system as a whole
- if something like that must be allowed it must be policed somehow from the
core....what if dozens of callbacks are allowed to be registered in this way
instead of the blocking mode ? they will slow down each other anyway..and
what about relative priorities amongst callbacks inside the same notification
chain ? (potentially registered from different users)
- let's say we allow this and you can register your own atomic callback (which it would
be policed), what you can do with that at the end ? What are the benefits of this
scenario ? AICS there are two possible scenarios (but if you can propose more scenarios
that I've missed you're more than welcome):
1. you can do the smallest-amount-possible-of-work-in-irq-as-usual and defer,
probably attaching a timestamp of arrival to the stuff you push for
deferred processing (and this is what I'm doing already for you..even if
with too much memcpying around probably :D....more on this later...)
OR
2. you can immediately signal the condition just received to an external
processing unit...say like raising a line which will trigger an interrupt
in those agent...and this is a scenario in which I can imagine the atomic
notification chain can benefit (in fact that's the reason I'm still thinking
about it as a controlled/policed alternative)...but, anyway, in this scenario,
you are going to route as quickly as possible a critical SCMI notification to
some external processor for immediate processing...and so you want it to be
propagated as fast as possible...fine..but why passing through the richOS at all ?
if it's so critical shouldn't have been already handled by the platform to the
processing entity bypassing the richOS as a whole and all its inherent latencies ?
(beside my own memcpys :D)
So for this last consideration I gave up thinking about some more performant
atomic delivery of notifications ? But if you can make a case where some sort of
alternative quick atomic (policed) delivery makes sense, I'll be happy to think
about it again.
> Note that we (BrcmSTB) have implemented our own SCMI notification
> system for a proprietary protocol and we designed it to deliver
> notifications as quickly as possible. Our system is more or less a
> disposable hack and would not stand up to heavy or general usage. We
> fully intend to move to the approved Linux notification system. On
> that note, I'm just wondering if you had any comment on the
> possibility of "slimming down" your RFC, e.g. perhaps somehow
> collapsing some memcpy()s.
>
Having said all of the above, I'll certainly review the memcopying to see if I can
redesign an shrink a bit their number. (the only thing that I want to avoid is placing
a spinlock into the ISR side of the dispatching...since now is all lock-free on that side
thanks to the kfifo, the 1-reader-1-writer scnario, and an additional memcpy)
In these regards what I had started to do (but no more), it was to sort of "profiling" a bit
the latency from event RX up to the point immediately before the report is delivered to the users
callbacks, and see if I can improve a bit this path in term of performance reshuffling the code.
In V3 I'm reviewing a lot notification init/exit logic (which was a bit dirty and faulty ...)
and handling of possible different platform instances (which were not handled), I'll see if I
can stick some meaningful fix about memcopies (if not it will be V4)
Moreover on this theme, given your low latencies requirements: as of now I'm using as a backend
the normal Kernel notification chains, which means though, that:
- users are in control of callbacks relative priorities, so that registering a high-pri slow one
could waste any gain and slow-down some other user registered callbacks on the same notification
chain (no matter if atomic or blocking)
- users (maliciously ?) could simply register a callback that return NOTIFY_STOP and to cut the chain
- users can (maliciously or not) mangle the event report fed to your callback along the way,
so that one user can trash potentially the event seen by the next user on the same chain
Do you think the above issues are worth considering to be addressed (for performance/security issues) ?
Because in v1 I had a patch for anti-tampering (now dropped to simplify the code) that could address
all of the above, but I did not know if such policying/anti-tampering attempt was worth an valid.
(even though, I think that if I'd end up adding some emergency/critical fast support, that would need
some sort of callbacks priority policying at least)
Thanks
Regards
Cristian
> Thanks,
> Jim
> PS I'm going on vacation so I won't be able to email for a week.
>
>
> On Fri, Feb 14, 2020 at 10:36 AM Cristian Marussi
> <cristian.marussi@xxxxxxx> wrote:
>>
>> Hi all,
>>
>> this series wants to introduce SCMI Notification Support, built on top of
>> the standard Kernel notification chain subsystem.
>>
>> At initialization time each SCMI Protocol takes care to register with the
>> new SCMI notification core the set of its own events which it intends to
>> support.
>>
>> Using a possibly proposed API in include/linux/scmi_protocol.h (not
>> finalized though, NO EXPORTs_) a Kernel user can register its own
>> notifier_t callback (via a notifier_block as usual) against any registered
>> event as identified by the tuple:
>>
>> (proto_id, event_id, src_id)
>>
>> where src_id represents a generic source identifier which is protocol
>> dependent like domain_id, performance_id, sensor_id and so forth.
>> (users can anyway do NOT provide any src_id, and subscribe instead to ALL
>> the existing (if any) src_id sources for that proto_id/evt_id combination)
>>
>> Each of the above tuple-specified event will be served on its own dedicated
>> blocking notification chain.
>>
>> Upon a notification delivery all the users' registered notifier_t callbacks
>> will be in turn invoked and fed with the event_id as @action param and a
>> generated custom per-event struct _report as @data param.
>> (as in include/linux/scmi_protocol.h)
>>
>> The final step of notification delivery via users' callback invocation is
>> instead delegated to a pool of deferred workers (Kernel cmwq): each
>> SCMI protocol has its own dedicated worker and dedicated queue to push
>> events from the rx ISR to the worker.
>>
>> The series is marked as RFC mainly because:
>>
>> - the API as said is tentative and not EXPORTed; currently consisting of a
>> generic interface like:
>>
>> scmi_register_event_notifier(proto_id, evt_id, *src_id, *nb)
>>
>> as found in scmi_protocol.h, or using the equivalent 'handle' operations
>> in scmi_notify_ops if used by an scmi_driver.
>>
>> It's open for discussion.
>>
>> - no Event priorization has been considered: each protocol has its own
>> queue and deferred worker instance, so as to avoid that one protocol
>> flood can overrun a single queue and influence other protocols'
>> notifications' delivery.
>> But that's it, all the workers are unbound, low_pri cmwq workers.
>>
>> Should we enforce some sort of built-in prio amongst the events ?
>> Should this priority instead be compile time configurable ?
>>
>> Again, open for discussion.
>>
>> - no configuration is possible: it can be imagined that on a real platform
>> events' priority (if any) and events queues' depth could be something
>> somehow compile-time configurable, but this is not addressed by this
>> series at all.
>>
>> Based on scmi-next 5.6 [1], on top of:
>>
>> commit 5c8a47a5a91d ("firmware: arm_scmi: Make scmi core independent of
>> the transport type")
>>
>> This series has been tested on JUNO with an experimental firmware only
>> supporting Perf Notifications.
>>
>> Any thoughts ?
>>
>> Thanks
>>
>> Cristian
>> ----
>>
>> v1 --> v2:
>> - dropped anti-tampering patch
>> - rebased on top of scmi-for-next-5.6, which includes Viresh series that
>> make SCMI core independent of transport (5c8a47a5a91d)
>> - add a few new SCMI transport methods on top of Viresh patch to address
>> needs of SCMI Notifications
>> - reviewed/renamed scmi_handle_xfer_delayed_resp()
>> - split main SCMI Notification core patch (~1k lines) into three chunks:
>> protocol-registration / callbacks-registration / dispatch-and-delivery
>> - removed awkward usage of IDR maps in favour of pure hashtables
>> - added enable/disable refcounting in notification core (was broken in v1)
>> - removed per-protocol candidate API: a single generic API is now proposed
>> instead of scmi_register_<proto>_event_notifier(evt_id, *src_id, *nb)
>> - added handle->notify_ops as an alternative notification API
>> for scmi_driver
>> - moved ALL_SRCIDs enabled handling from protocol code to core code
>> - reviewed protocol registration/unregistration logic to use devres
>> - reviewed cleanup phase on shutdown
>> - fixed ERROR: reference preceded by free as reported by kbuild test robot
>>
>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git
>>
>> Cristian Marussi (10):
>> firmware: arm_scmi: Add notifications support in transport layer
>> firmware: arm_scmi: Add notification protocol-registration
>> firmware: arm_scmi: Add notification callbacks-registration
>> firmware: arm_scmi: Add notification dispatch and delivery
>> firmware: arm_scmi: Enable notification core
>> firmware: arm_scmi: Add Power notifications support
>> firmware: arm_scmi: Add Perf notifications support
>> firmware: arm_scmi: Add Sensor notifications support
>> firmware: arm_scmi: Add Reset notifications support
>> firmware: arm_scmi: Add Base notifications support
>>
>> Sudeep Holla (3):
>> firmware: arm_scmi: Add receive buffer support for notifications
>> firmware: arm_scmi: Update protocol commands and notification list
>> firmware: arm_scmi: Add support for notifications message processing
>>
>> drivers/firmware/arm_scmi/Makefile | 2 +-
>> drivers/firmware/arm_scmi/base.c | 121 +++
>> drivers/firmware/arm_scmi/bus.c | 11 +
>> drivers/firmware/arm_scmi/common.h | 12 +
>> drivers/firmware/arm_scmi/driver.c | 118 ++-
>> drivers/firmware/arm_scmi/mailbox.c | 17 +
>> drivers/firmware/arm_scmi/notify.c | 1102 +++++++++++++++++++++++++++
>> drivers/firmware/arm_scmi/notify.h | 78 ++
>> drivers/firmware/arm_scmi/perf.c | 140 +++-
>> drivers/firmware/arm_scmi/power.c | 133 +++-
>> drivers/firmware/arm_scmi/reset.c | 100 ++-
>> drivers/firmware/arm_scmi/sensors.c | 77 +-
>> drivers/firmware/arm_scmi/shmem.c | 15 +
>> include/linux/scmi_protocol.h | 114 +++
>> 14 files changed, 2009 insertions(+), 31 deletions(-)
>> create mode 100644 drivers/firmware/arm_scmi/notify.c
>> create mode 100644 drivers/firmware/arm_scmi/notify.h
>>
>> --
>> 2.17.1
>>