Searched full:modeled (Results 1 – 25 of 80) sorted by relevance
1234
| /Linux-v6.6/tools/memory-model/scripts/ |
| D | judgelitmus.sh | 69 echo '!!! Predicted data race not modeled' $litmus
74 echo '!!! Unexpected data race modeled' $litmus
|
| /Linux-v6.6/tools/memory-model/Documentation/ |
| D | litmus-tests.txt | 60 appears often in the Linux kernel. For example, a flag (modeled by "y"
61 below) indicates that a buffer (modeled by "x" below) is now completely
935 1. Compiler optimizations are not accurately modeled. Of course,
986 3. Exceptions and interrupts are not modeled. In some cases,
1008 b. The "unless" RMW operations are not currently modeled:
1016 modeled by herd7 therefore it can be used in litmus tests.
1018 c. The call_rcu() function is not modeled. As was shown above,
1025 d. The rcu_barrier() function is not modeled. It can be
1031 e. Reader-writer locking is not modeled. It can be
|
| /Linux-v6.6/drivers/net/ethernet/intel/e1000e/ |
| D | e1000e_trace.h | 3 /* Modeled on trace-events-sample.h */
|
| /Linux-v6.6/include/linux/spi/ |
| D | mmc_spi.h | 12 * card slot. (Modeled after PXA mmc glue; see that for usage examples.)
|
| /Linux-v6.6/drivers/media/usb/gspca/m5602/ |
| D | m5602_s5k83a.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_sensor.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_ov7660.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_s5k4aa.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_mt9m111.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_po1030.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_ov9650.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| D | m5602_bridge.h | 11 * v4l2 interface modeled after the V4L2 driver
|
| /Linux-v6.6/Documentation/devicetree/bindings/display/ |
| D | truly,nt35597.txt | 21 are modeled using the OF graph bindings specified in
|
| /Linux-v6.6/Documentation/devicetree/bindings/mfd/ |
| D | tc3589x.txt | 46 keys. The linux-specific properties are modeled on those already existing
|
| /Linux-v6.6/drivers/gpu/drm/renesas/rcar-du/ |
| D | rcar_du_group.c | 16 * This would be modeled as two separate DU device instances if it wasn't for
19 * modeled as a single device with three CRTCs, two sets of "semi-global"
|
| /Linux-v6.6/Documentation/mm/ |
| D | multigen_lru.rst | 104 modeled after the PID controller monitors refaults over all the tiers
213 A feedback loop modeled after the Proportional-Integral-Derivative
|
| /Linux-v6.6/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,gsbi.yaml | 15 The GSBI controller is modeled as a node with zero or more child nodes, each
|
| D | qcom,geni-se.yaml | 17 Wrapper controller is modeled as a node with zero or more child nodes each
|
| /Linux-v6.6/Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos7885-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| D | samsung,exynosautov9-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| D | samsung,exynos850-clock.yaml | 18 clocks for different domains. Those CMU units are modeled as separate device
|
| /Linux-v6.6/Documentation/devicetree/bindings/soc/samsung/ |
| D | exynos-usi.yaml | 16 protocol can be chosen at a time. USI is modeled as a node with zero or more
|
| /Linux-v6.6/Documentation/virt/hyperv/ |
| D | vmbus.rst | 15 VMbus is modeled in Linux as a bus, with the expected /sys/bus/vmbus
182 may receive VMbus interrupts, so they are best modeled as per-CPU
|
| /Linux-v6.6/drivers/net/ethernet/intel/iavf/ |
| D | iavf_trace.h | 4 /* Modeled on trace-events-sample.h */
|
| /Linux-v6.6/include/uapi/linux/ |
| D | rtc.h | 51 * This is modeled after the RTC used in Q40/Q60 computers but
|
1234
