Home
last modified time | relevance | path

Searched full:ever (Results 1 – 25 of 2302) sorted by relevance

12345678910>>...93

/kernel/linux/linux-6.6/arch/alpha/include/uapi/asm/
Dsigcontext.h8 * stack layout as OSF/1, just in case we ever want to try
11 * This is the basic layout, but I don't know if we'll ever
/kernel/linux/linux-5.10/arch/alpha/include/uapi/asm/
Dsigcontext.h8 * stack layout as OSF/1, just in case we ever want to try
11 * This is the basic layout, but I don't know if we'll ever
/kernel/linux/linux-6.6/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/
Drammap.h19 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
24 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
/kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/include/nvkm/subdev/bios/
Drammap.h19 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
24 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx,
/kernel/linux/linux-5.10/Documentation/locking/
Dlockdep-design.rst25 dependency just means the order ever happened. The validator maintains a
46 - 'ever held in STATE context'
47 - 'ever held as readlock in STATE context'
48 - 'ever held with STATE enabled'
49 - 'ever held as readlock with STATE enabled'
59 - 'ever used' [ == !unused ]
94 For a given STATE, whether the lock is ever acquired in that STATE
102 | ever in irq | '?' | '-' |
117 A lock is irq-safe means it was ever used in an irq context, while a lock
118 is irq-unsafe means it was ever acquired with irq enabled.
[all …]
Dlockstat.rst56 - shortest (non-0) time we ever had to wait for a lock
58 - longest time we ever had to wait for a lock
69 - shortest (non-0) time we ever held the lock
71 - longest time we ever held the lock
/kernel/linux/linux-6.6/Documentation/locking/
Dlockdep-design.rst25 dependency just means the order ever happened. The validator maintains a
46 - 'ever held in STATE context'
47 - 'ever held as readlock in STATE context'
48 - 'ever held with STATE enabled'
49 - 'ever held as readlock with STATE enabled'
59 - 'ever used' [ == !unused ]
94 For a given STATE, whether the lock is ever acquired in that STATE
102 | ever in irq | '?' | '-' |
117 A lock is irq-safe means it was ever used in an irq context, while a lock
118 is irq-unsafe means it was ever acquired with irq enabled.
[all …]
Dlockstat.rst56 - shortest (non-0) time we ever had to wait for a lock
58 - longest time we ever had to wait for a lock
69 - shortest (non-0) time we ever held the lock
71 - longest time we ever held the lock
/kernel/linux/linux-6.6/Documentation/gpu/rfc/
Di915_small_bar.h19 * Note that it should not be possible to ever encounter a zero value
20 * here, also note that no current region type will ever return -1 here.
156 * resort, if userspace ever CPU faults this object, but this might be
/kernel/linux/linux-6.6/Documentation/scheduler/
Dsched-arch.rst29 2. need_resched/TIF_NEED_RESCHED is only ever set, and will never
31 threads need only ever query need_resched, and may never set or
/kernel/linux/linux-5.10/Documentation/scheduler/
Dsched-arch.rst29 2. need_resched/TIF_NEED_RESCHED is only ever set, and will never
31 threads need only ever query need_resched, and may never set or
/kernel/linux/linux-5.10/security/keys/
DKconfig82 if the boot PCRs and other criteria match. Userspace will only ever
101 Userspace only ever sees/stores encrypted blobs.
/kernel/linux/linux-5.10/drivers/staging/pi433/
Dpi433_if.h49 * If the contents of 'pi433_tx_config' ever change
97 * If the contents of 'pi433_rx_config' ever change
/kernel/linux/linux-6.6/drivers/staging/pi433/
Dpi433_if.h46 * If the contents of 'pi433_tx_cfg' ever change
94 * If the contents of 'pi433_rx_cfg' ever change
/kernel/linux/linux-5.10/include/linux/
Ddynamic_queue_limits.h45 unsigned int num_queued; /* Total ever queued */
52 unsigned int num_completed; /* Total ever completed */
/kernel/linux/linux-6.6/security/keys/
DKconfig78 Userspace will only ever see encrypted blobs.
101 blobs are ever output to Userspace.
/kernel/linux/linux-6.6/include/linux/
Ddynamic_queue_limits.h45 unsigned int num_queued; /* Total ever queued */
52 unsigned int num_completed; /* Total ever completed */
/kernel/linux/linux-5.10/drivers/gpu/drm/nouveau/nvkm/subdev/bios/
Drammap.c147 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, u8 *ver, u8 *hdr) in nvbios_rammapSe() argument
151 *ver = ever; in nvbios_rammapSe()
191 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, in nvbios_rammapSp() argument
194 data = nvbios_rammapSe(bios, data, ever, ehdr, ecnt, elen, idx, ver, hdr); in nvbios_rammapSp()
/kernel/linux/linux-6.6/drivers/gpu/drm/nouveau/nvkm/subdev/bios/
Drammap.c147 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, u8 *ver, u8 *hdr) in nvbios_rammapSe() argument
151 *ver = ever; in nvbios_rammapSe()
191 u8 ever, u8 ehdr, u8 ecnt, u8 elen, int idx, in nvbios_rammapSp() argument
194 data = nvbios_rammapSe(bios, data, ever, ehdr, ecnt, elen, idx, ver, hdr); in nvbios_rammapSp()
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-class-devlink15 This file indicates if the device link will ever be
101 above. If this is ever the value, there's a bug in the kernel.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-devlink15 This file indicates if the device link will ever be
101 above. If this is ever the value, there's a bug in the kernel.
/kernel/linux/linux-5.10/tools/include/linux/
Dbug.h7 e.g. in a structure initializer (or where-ever else comma expressions
/kernel/linux/linux-6.6/tools/include/linux/
Dbug.h7 e.g. in a structure initializer (or where-ever else comma expressions
/kernel/linux/linux-6.6/arch/x86/configs/
Dxen.config26 # move to generic config if it ever does.
/kernel/linux/linux-5.10/arch/powerpc/include/asm/
Dcrashdump-ppc64.h8 * If ever the below macros are to be changed, please be judicious.

12345678910>>...93