The OpenHCL resolver pattern (how device configs from VTL0 settings get mapped to concrete device implementations) is used by multiple subsystems -- NVMe VFIO, StorVSC usermode, and potentially future backends.
Currently the pattern is only documented in context-specific places:
nvme_manager/mod.rs module docs (NVMe-specific)- StorVSC design docs (storvsc-specific comparison)
A standalone Guide page covering the resolver architecture generically would be useful:
- What
ResourceResolver does and how resolvers register
- The config -> resolver -> resolved-device pipeline
- How managers (NvmeManager, StorvscManager) coordinate with resolvers
- Pattern for adding new resolver types
The OpenHCL resolver pattern (how device configs from VTL0 settings get mapped to concrete device implementations) is used by multiple subsystems -- NVMe VFIO, StorVSC usermode, and potentially future backends.
Currently the pattern is only documented in context-specific places:
nvme_manager/mod.rsmodule docs (NVMe-specific)A standalone Guide page covering the resolver architecture generically would be useful:
ResourceResolverdoes and how resolvers register