zephyr/samples/kernel/metairq_dispatch/sample.yaml

sample:
  description: Sample demonstrating dispatch of hardware events from a
    MetaIRQ thread
  name: MetaIRQ Dispatch
common:
    harness: console
    harness_config:
      type: one_line
      regex:
        - "MetaIRQ Test Complete"

# Note that native_posix architectures are filtered, they require
# instrumentation (e.g. a k_busy_wait()) inside the worker threads
# "busy" loops in order for the interrupts to fire on time, and the
# sample is designed to demonstrate completely arbitrary CPU work.
tests:
  sample.kernel.metairq_dispatch:
    tags: introduction
    filter: not CONFIG_ARCH_POSIX
samples: Add MetaIRQ dispatch sample MetaIRQs are described in docs and exercised in tests, but there's no sample explaining how they are intended to be used to perform interrupt bottom half processing. This simple tool spawns a set of worker threads at different priorities (some cooperative) which process "messages" (which require CPU time to handle) received from a fake "device" implemented with timer interrupts. The device hands off the events directly to a MetaIRQ thread which is expected to parse and dispatch them to the worker threads. The test demonstrates that no matter the state of the system, the MetaIRQ thread always runs synchronously when woken by the ISR and is able to preempt all worker threads to do its job. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2020-01-30 04:56:23 +08:00			`sample:`
			`description: Sample demonstrating dispatch of hardware events from a`
			`MetaIRQ thread`
			`name: MetaIRQ Dispatch`
			`common:`
			`harness: console`
			`harness_config:`
			`type: one_line`
			`regex:`
			`- "MetaIRQ Test Complete"`

			`# Note that native_posix architectures are filtered, they require`
			`# instrumentation (e.g. a k_busy_wait()) inside the worker threads`
			`# "busy" loops in order for the interrupts to fire on time, and the`
			`# sample is designed to demonstrate completely arbitrary CPU work.`
			`tests:`
samples: clean test identifiers Use a complete identifier, first two parts are section.subsection, then at least another part for the specifics being tested. Signed-off-by: Anas Nashif <anas.nashif@intel.com> 2020-05-05 20:31:15 +08:00			`sample.kernel.metairq_dispatch:`
samples: Add MetaIRQ dispatch sample MetaIRQs are described in docs and exercised in tests, but there's no sample explaining how they are intended to be used to perform interrupt bottom half processing. This simple tool spawns a set of worker threads at different priorities (some cooperative) which process "messages" (which require CPU time to handle) received from a fake "device" implemented with timer interrupts. The device hands off the events directly to a MetaIRQ thread which is expected to parse and dispatch them to the worker threads. The test demonstrates that no matter the state of the system, the MetaIRQ thread always runs synchronously when woken by the ISR and is able to preempt all worker threads to do its job. Signed-off-by: Andy Ross <andrew.j.ross@intel.com> 2020-01-30 04:56:23 +08:00			`tags: introduction`
			`filter: not CONFIG_ARCH_POSIX`