A recent RFC patch set [1] suggests some additional functionality may be needed around kunit resources. It seems to require 1. support for resources without allocation 2. support for lookup of such resources 3. support for access to resources across multiple kernel threads The proposed changes here are designed to address these needs. The idea is we first generalize the API to support adding resources with static data; then from there we support named resources. The latter support is needed because if we are in a different thread context and only have the "struct kunit *" to work with, we need a way to identify a resource in lookup. [1] https://lkml.org/lkml/2020/2/26/1286 Alan Maguire (2): kunit: generalize kunit_resource API beyond allocated resources kunit: add support for named resources include/kunit/test.h | 145 ++++++++++++++++++++++------ lib/kunit/kunit-test.c | 103 ++++++++++++++++---- lib/kunit/string-stream.c | 14 ++- lib/kunit/test.c | 234 +++++++++++++++++++++++++++++++++------------- 4 files changed, 375 insertions(+), 121 deletions(-) -- 1.8.3.1
