Home
last modified time | relevance | path

Searched full:hypothetical (Results 1 – 25 of 26) sorted by relevance

12

/linux/Documentation/driver-api/
H A Dio_ordering.rst15 A more concrete example from a hypothetical device driver::
H A Dclk.rst35 hardware-specific bits for the hypothetical "foo" hardware.
/linux/Documentation/devicetree/bindings/firmware/
H A Dnvidia,tegra186-bpmp.yaml55 provide (e.g. a future hypothetical SPI bus service). As such, child
/linux/Documentation/arch/arm/
H A Dvlocks.rst97 if necessary, as in the following hypothetical example for 4096 CPUs::
/linux/Documentation/devicetree/bindings/powerpc/
H A Dibm,powerpc-cpu-features.txt231 vsx2 (hypothetical) {
/linux/Documentation/driver-api/driver-model/
H A Ddriver.rst28 driver. This declaration is hypothetical only; it relies on the driver
/linux/Documentation/
H A Datomic_t.txt258 This should not happen; but a hypothetical atomic_inc_acquire() --
/linux/Documentation/gpu/amdgpu/display/
H A Dmpo-overview.rst59 hypothetical hardware that we are using as an example, we have an absolute
/linux/LICENSES/deprecated/
H A DGPL-1.0243 The hypothetical commands `show w' and `show c' should show the
/linux/tools/lib/bpf/
H A Dbtf.c3640 /* Hypothetical mapping, used during type graph equivalence checks */
3645 /* Whether hypothetical mapping, if successful, would need to adjust
4528 * a `cand_id` is recoded in hypothetical mapping (`btf_dedup->hypot_map`).
4533 * already have some mapping in hypothetical map, we check for two possible
4539 * hypothetical mapping, because same graph in canonical graph corresponds
4550 * flag) and their names match, hypothetical mapping is updated to point from
4576 * anymore and will make it harder to detect contradictions using hypothetical
4592 * because hypothetical mapping maps from canonical to candidate types, it's
4759 * Use hypothetical mapping, produced by successful type graph equivalence
4858 * BTF_KIND_FWD resolution is allowed, then hypothetical mappin
[all...]
H A Dbpf_helpers.h356 * that can be used pretty naturally. E.g., for some hypothetical cgroup
/linux/tools/usb/usbip/
H A DCOPYING321 The hypothetical commands `show w' and `show c' should show the appropriate
/linux/LICENSES/preferred/
H A DGPL-2.0338 The hypothetical commands `show w' and `show c' should show the appropriate
/linux/Documentation/scheduler/
H A Dsched-capacity.rst59 Consider an hypothetical dual-core asymmetric CPU capacity system where
/linux/Documentation/security/
H A Dipe.rst156 what is being written. In a hypothetical binary policy design, a serializer
/linux/include/uapi/linux/
H A Drtnetlink.h293 It will be used by hypothetical multiple routing daemons.
/linux/tools/include/uapi/linux/
H A Drtnetlink.h293 It will be used by hypothetical multiple routing daemons.
/linux/Documentation/i2c/
H A Di2c-topology.rst107 intent with such a topology would in this hypothetical example
/linux/fs/xfs/scrub/
H A Dialloc.c354 * Check that the holemask and freemask of a hypothetical inode cluster match
/linux/arch/x86/mm/
H A Dtlb.c683 * opens a hypothetical hole vs. mm_struct reuse, which is more or in cond_mitigation()
800 * hypothetical buggy code that directly switches to swapper_pg_dir in switch_mm_irqs_off()
/linux/fs/btrfs/tests/
H A Dextent-io-tests.c478 * something repetitive that could miss some hypothetical off-by-n bug. in __test_eb_bitmaps()
/linux/drivers/net/wireless/intel/iwlegacy/
H A D4965-calib.c111 * hypothetical listening period of 200 time units (TU), 204.8 msec: in il4965_sens_energy_cck()
/linux/drivers/net/wireless/intel/iwlwifi/dvm/
H A Dcalib.c127 * hypothetical listening period of 200 time units (TU), 204.8 msec: in iwl_sens_energy_cck()
/linux/kernel/kcsan/
H A Dcore.c1300 * couldn't optimize much anyway. The result of a hypothetical architecture
/linux/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-codec.rst1332 decoded. The standard describes it as "Part of a hypothetical

12