...
Crypto / Security- Trusted Execution Environments
- NXP accelerator blocks?
- Firmware framework for Cortex-A, OPTEE, how to access secure computing from the general application, ...
Ethernet AvB / Time Sensitive Networking- NXP accelerator blocks?
Automotive networks, in particular CAN- Accelerators
Tensor-Processing Units- Will be used for some safety critical features? Is it feasible to virtualize?
- DSPs (is that discussion done in AVPS or is there more?)
- Camera
-
Next-gen PCI and future interconnects. Used for example for inter-chip communication and peripherals - Graphics (again...)
...
- IPC and Inter-Chip Communication
- Communication between different guests or hardware parts. Does it affect the Virtual Platform or is it just run transparently on virtual socket?
- One specific use case is inter-cpu communication. Particularly in the case of converged SoCs, e.g. comms between app on RT and general purpose CPU.
- Are there standard choices? Are there many vendor-specific proposals, like IC-COM? (Is that an AUTOSAR standard?)
RPMSG → https://www.kernel.org/doc/html/latest/staging/rpmsg.html
NXP has some framework? - Impact and design of security.
- Go through operating system kernel special needs for each popular OS choice.
- e.g. Is VIRTIO reasonably supported for RTOSes or other requirements?
- e.g. What is the impact of new RTOS initiatives, as well as migration of legacy code from dedicated hardware to a virtualized environment (because the hardware goes out of production or similar). Thread-X, AUTOSAR (OSEK), Zaphyr, FreeRTOS, Arm MBed, (and no-RTOS bare-metal VMs).
- Clock synchronization, real-time clock abstraction (probably a good topic for the AVPS)
- Discussed today for the purpose of synchronized logs... but are not there more reasons? E.g. systems that can do load-balancing, redundancy (offloading, transferring tasks), don't they need a common time?
- Timer paravirtualization
- CPU scheduling reporting HV<->VM, e.g. kernels do not get accurate information about system load. Steal time reporting. The time while a VM was not scheduled, even though it should run (= Steal time).
- A spec from Arm ("Arm para-virtualized time" DEN0057A ) covers how to report steal time.
- General topic: Needs for (easier, better) virtualization support in future SoCs.
- Still examples of how IP-block diversity and limitations causes issues (32 bit device in an otherwise 64-bit architecture)
- Is virtualization truly a top priority for SoC vendors?
- Agreed definition of virtualization. Non-MMU systems seem to use the term even if the implementation is rather hardware separation.
...
Someone on NXP for TEE and Networking?
Bernard (Arm) on various topics, including
- Security, firmware framework for Arm-A (link) , optee
- CCIX, CXL ...
- Real-time aspects. ARMv8-R device virtualization specification? (early draft circulated, might be available to us around September)
- Clock synchronization
Ask Linaro representatives
- working on implementation (on Xen) of various VIRTIO areas. Reach out to Francois to understand most challenging areas?
Fulup checking with team who might be best suited to each topic.
(Monday 10 AM is not a good time slot)