Home
last modified time | relevance | path

Searched full:actually (Results 1 – 25 of 5391) sorted by relevance

12345678910>>...216

/kernel/linux/linux-5.10/Documentation/core-api/
Dbus-virt-phys-mapping.rst24 However, on many setups, there are actually **three** different ways of looking
25 at memory addresses, and in this case we actually want the third, the
41 happily most hardware designers aren't actually actively trying to make
59 address 0 actually shows up as address 2 GB for any IO master.
64 So, for example, depending on how the kernel is actually mapped on the
71 where all the addresses actually point to the same thing. It's just seen
94 You want the **virtual** address when you are actually going to access that
153 so on x86 it actually works to just deference a pointer, but it's not
214 actually looks better afterwards::
220 I think the second version actually is more readable, no?
Dpadata.rst72 user-supplied masks; these are the cpumasks padata actually uses. So it is
83 Actually submitting work to the padata instance requires the creation of a
107 is updated to point to the CPU actually chosen). The return value from
131 When a job does complete, parallel() (or whatever function actually finishes
/kernel/linux/linux-5.10/arch/x86/math-emu/
Dload_store.c167 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
177 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
187 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
213 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
220 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
227 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
234 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
289 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
303 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
317 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
/kernel/linux/linux-6.6/arch/x86/math-emu/
Dload_store.c167 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
177 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
187 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
213 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
220 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
227 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
234 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
289 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
303 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
317 pop_0(); /* pop only if the number was actually stored in FPU_load_store()
/kernel/linux/linux-5.10/arch/mips/include/uapi/asm/
Dstat.h32 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
70 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
111 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
/kernel/linux/linux-6.6/arch/mips/include/uapi/asm/
Dstat.h32 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
70 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
111 * Actually this should be timestruc_t st_atime, st_mtime and st_ctime
/kernel/linux/linux-6.6/arch/s390/include/asm/
Duser.h18 contents of them. Actually, you can read in the core file and look at
54 struct user_regs_struct regs; /* Where the registers are actually stored */
61 This is actually the bottom of the stack,
/kernel/linux/linux-5.10/arch/h8300/include/asm/
Duser.h12 contents of them. Actually, you can read in the core file and look at
52 struct user_regs_struct regs; /* Where the registers are actually stored */
60 This is actually the bottom of the stack,
/kernel/linux/linux-5.10/arch/s390/include/asm/
Duser.h18 contents of them. Actually, you can read in the core file and look at
54 struct user_regs_struct regs; /* Where the registers are actually stored */
61 This is actually the bottom of the stack,
/kernel/linux/linux-6.6/arch/m68k/include/asm/
Duser.h10 contents of them. Actually, you can read in the core file and look at
60 struct user_regs_struct regs; /* Where the registers are actually stored */
71 This is actually the bottom of the stack,
/kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/
Dextended-controls.rst24 of the resulting MPEG stream, not how the video is actually encoded into
76 ``V4L2_CTRL_FLAG_NEXT_COMPOUND`` when enumerating controls to actually
89 necessary to check whether the control you want to set actually is
143 and are not actually part of the ID. The remaining 28 bits form the
Dselection-api-intro.rst15 cropping target determine the area actually sampled. The sink is an
17 of the buffer is actually written to by the hardware.
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dextended-controls.rst24 of the resulting MPEG stream, not how the video is actually encoded into
76 ``V4L2_CTRL_FLAG_NEXT_COMPOUND`` when enumerating controls to actually
89 necessary to check whether the control you want to set actually is
143 and are not actually part of the ID. The remaining 28 bits form the
Dselection-api-intro.rst15 cropping target determine the area actually sampled. The sink is an
17 of the buffer is actually written to by the hardware.
/kernel/linux/linux-5.10/arch/m68k/include/asm/
Duser.h10 contents of them. Actually, you can read in the core file and look at
60 struct user_regs_struct regs; /* Where the registers are actually stored */
71 This is actually the bottom of the stack,
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/
Duncore-memory.json463 … is not to be confused with actually performing the write to DRAM. Therefore, the average latency…
472 … is not to be confused with actually performing the write to DRAM. Therefore, the average latency…
499actually performing the write to DRAM. Therefore, the average latency for this queue is actually
507actually performing the write to DRAM. Therefore, the average latency for this queue is actually
/kernel/linux/linux-5.10/security/smack/
Dsmackfs.c426 * @file: file pointer, not actually used
651 * @file: file pointer, not actually used
820 * @file: file pointer, not actually used
942 * @file: file pointer, not actually used
1016 * @file: file pointer, not actually used
1135 * @file: file pointer, not actually used
1398 * @file: file pointer, not actually used
1563 * @filp: file pointer, not actually used
1587 * @file: file pointer, not actually used
1629 * @filp: file pointer, not actually used
[all …]
/kernel/linux/linux-6.6/security/smack/
Dsmackfs.c427 * @file: file pointer, not actually used
652 * @file: file pointer, not actually used
821 * @file: file pointer, not actually used
947 * @file: file pointer, not actually used
1021 * @file: file pointer, not actually used
1140 * @file: file pointer, not actually used
1402 * @file: file pointer, not actually used
1567 * @filp: file pointer, not actually used
1591 * @file: file pointer, not actually used
1633 * @filp: file pointer, not actually used
[all …]
/kernel/linux/linux-5.10/include/asm-generic/bitops/
Dinstrumented-non-atomic.h91 * can appear to succeed but actually fail.
105 * can appear to succeed but actually fail.
119 * can appear to succeed but actually fail.
/kernel/linux/linux-5.10/arch/arm/include/asm/
Duser.h12 contents of them. Actually, you can read in the core file and look at
56 struct pt_regs regs; /* Where the registers are actually stored */
66 This is actually the bottom of the stack,
/kernel/linux/linux-6.6/arch/arm/include/asm/
Duser.h12 contents of them. Actually, you can read in the core file and look at
56 struct pt_regs regs; /* Where the registers are actually stored */
66 This is actually the bottom of the stack,
/kernel/linux/linux-5.10/arch/xtensa/include/asm/
Dasm-uaccess.h60 * <at> destroyed (actually, current)
85 * <at> destroyed (actually, current->thread.current_ds)
117 * <at> destroyed (actually, (TASK_SIZE + 1 - size))
/kernel/linux/linux-5.10/arch/mips/include/asm/
Dsync.h13 * 1) Completion barriers, which ensure that a memory operation has actually
27 * actually need to complete - they just need to get far enough that all
120 * 1) A memory access appearing prior to the LL in program order may actually
168 * The main event. Here we actually emit a sync instruction of a given type, if
/kernel/linux/linux-6.6/Documentation/core-api/
Dpadata.rst72 user-supplied masks; these are the cpumasks padata actually uses. So it is
83 Actually submitting work to the padata instance requires the creation of a
107 is updated to point to the CPU actually chosen). The return value from
131 When a job does complete, parallel() (or whatever function actually finishes
/kernel/linux/linux-6.6/arch/mips/include/asm/
Dsync.h13 * 1) Completion barriers, which ensure that a memory operation has actually
27 * actually need to complete - they just need to get far enough that all
120 * 1) A memory access appearing prior to the LL in program order may actually
168 * The main event. Here we actually emit a sync instruction of a given type, if

12345678910>>...216