Home
last modified time | relevance | path

Searched full:involves (Results 1 – 25 of 204) sorted by relevance

123456789

/linux/Documentation/admin-guide/hw-vuln/
H A Dattack_vector_controls.rst34 The user-to-kernel attack vector involves a malicious userspace program
54 The user-to-user attack vector involves a malicious userspace program attempting
74 The guest-to-host attack vector involves a malicious VM attempting to leak
88 The guest-to-guest attack vector involves a malicious VM attempting to influence
107 The cross-thread attack vector involves a malicious userspace program or
H A Dcore-scheduling.rst16 A cross-HT attack involves the attacker and victim running on different Hyper
27 core involves additional overhead - especially when the system is lightly
/linux/Documentation/process/
H A Dadding-syscalls.rst26 - If the new functionality involves operations where the kernel notifies
130 If your new :manpage:`xyzzy(2)` system call involves a filename argument::
150 If your new :manpage:`xyzzy(2)` system call involves a parameter describing an
154 If your new :manpage:`xyzzy(2)` system call involves privileged functionality,
302 way (see below), this involves a "common" entry (for x86_64 and x32) in
360 If the system call involves a structure that is laid out differently on 32-bit
488 This is arch-specific, but typically involves defining assembly entry points
548 involves a new userspace-visible structure, the corresponding header will need
/linux/drivers/hwmon/pmbus/
H A Dltc4286.c41 * Thus, the MBR setting which involves rsense should be shifted by 6 digits.
49 * Thus, the MBR setting which involves rsense should be shifted by 6 digits.
/linux/Documentation/locking/
H A Dpi-futex.rst7 - in the user-space fastpath a PI-enabled futex involves no kernel work
79 mutexes involves no kernel work at all - they behave quite similarly to
/linux/Documentation/dev-tools/
H A Dpropeller.rst23 AutoFDO/AutoFDO+ThinLTO/iFDO. The whole build process involves
34 The Propeller optimization process involves the following steps:
/linux/arch/powerpc/platforms/embedded6xx/
H A Dhlwd-pic.c27 * Enabling/disabling an interrupt line involves asserting/clearing
28 * the corresponding bit in IMR. ACK'ing a request simply involves
/linux/Documentation/ABI/removed/
H A Dsysfs-bus-nfit11 involves determining the ARS capabilities of a given address
/linux/Documentation/userspace-api/media/drivers/
H A Dvgxy61.rst22 - This involves subtracting the short exposure frame from the long
/linux/drivers/staging/media/deprecated/atmel/
H A DTODO4 The move to media controller involves several changes which are
/linux/arch/hexagon/mm/
H A Dcopy_to_user.S8 /* The right way to do this involves valignb
H A Dcopy_from_user.S9 * The right way to do this involves valignb
/linux/Documentation/infiniband/
H A Dopa_vnic.rst12 involves one or more virtual Ethernet switches overlaid on the Omni-Path
114 It involves HW resource allocation/management for VNIC functionality.
/linux/drivers/infiniband/hw/hfi1/
H A Dopfn.h19 * OPFN involves the communication between two QPs on the HFI
/linux/Documentation/networking/device_drivers/fddi/
H A Ddefza.rst30 The board only supports DMA on the receive side. Transmission involves
/linux/arch/arm64/include/asm/
H A Drqspinlock.h9 * version based on [0]. In rqspinlock code, our conditional expression involves
/linux/Documentation/devicetree/bindings/mailbox/
H A Dqcom-ipcc.yaml14 to route interrupts across various subsystems. It involves a three-level
/linux/Documentation/power/
H A Ddrivers-testing.rst15 cases involves slightly different operations and different interactions with
/linux/Documentation/userspace-api/media/v4l/
H A Ddev-meta.rst53 involves devices that receive the data from a different devices such as a camera
/linux/Documentation/driver-api/nvdimm/
H A Dfirmware-activate.rst10 involves a reboot because it has implications for in-flight memory
/linux/drivers/thermal/intel/int340x_thermal/
H A Dprocessor_thermal_power_floor.c22 * Callback for interrupt processing in thread context. This involves
/linux/Documentation/gpu/nova/core/
H A Ddevinit.rst57 The initialization process involves careful privilege management. For example, before
/linux/drivers/slimbus/
H A Dsched.c18 * The sequence involves sending 3 broadcast messages (reconfiguration
/linux/Documentation/trace/coresight/
H A Dpanic.rst57 Coresight metadata involves all additional data that are required for a
58 successful trace decode in addition to the trace data. This involves
/linux/Documentation/filesystems/
H A Ddnotify.rst11 The basic mechanism involves the application registering for notification

123456789