Home
last modified time | relevance | path

Searched full:doing (Results 1 – 25 of 2299) sorted by relevance

12345678910>>...92

/Linux-v6.1/arch/microblaze/
DKconfig133 Unless you know what you are doing, say N here.
161 Say N here unless you know what you are doing.
187 Say N here unless you know what you are doing.
201 Say N here unless you know what you are doing.
215 Say N here unless you know what you are doing.
/Linux-v6.1/Documentation/driver-api/nvdimm/
Dsecurity.rst71 When doing an update, it is expected that the existing key is removed from
74 keyid when doing the update operation. It is also expected that the new key
98 The command format for doing a secure erase is:
106 The command format for doing an overwrite is:
120 The command format for doing a master update is:
131 The command format for doing a master erase is:
/Linux-v6.1/Documentation/x86/
Dtlb.rst23 entire TLB than doing 2^48/PAGE_SIZE individual flushes.
25 be no collateral damage caused by doing the global flush, and
41 You may be doing too many individual invalidations if you see the
61 Essentially, you are balancing the cycles you spend doing invlpg
/Linux-v6.1/kernel/
Dparams.c117 const char *doing, in parse_one() argument
124 const char *doing, void *arg)) in parse_one()
152 pr_debug("doing %s: %s='%s'\n", doing, param, val); in parse_one()
153 return handle_unknown(param, val, doing, arg); in parse_one()
161 char *parse_args(const char *doing, in parse_args() argument
169 const char *doing, void *arg)) in parse_args()
177 pr_debug("doing %s, parsing ARGS: '%s'\n", doing, args); in parse_args()
188 ret = parse_one(param, val, doing, params, num, in parse_args()
192 doing, param); in parse_args()
198 pr_err("%s: Unknown parameter `%s'\n", doing, param); in parse_args()
[all …]
/Linux-v6.1/Documentation/driver-api/driver-model/
Dporting.rst25 doing so, they will exported via the sysfs filesystem. sysfs can be
26 mounted by doing::
60 as a module) by doing::
107 the struct to discourage programmers from doing mindless casts
168 with the driver model core by doing::
172 It can later be unregistered by doing::
246 When the driver registers with the bus (e.g. doing pci_register_driver()),
260 core by doing::
/Linux-v6.1/arch/nios2/
DKconfig149 Say N here unless you know what you are doing.
163 Say N here unless you know what you are doing.
175 Say N here unless you know what you are doing.
/Linux-v6.1/drivers/net/mdio/
Dmdio-cavium.c51 * doing reads. in cavium_mdiobus_c45_addr()
90 * doing reads. in cavium_mdiobus_read()
135 * doing reads. in cavium_mdiobus_write()
/Linux-v6.1/Documentation/core-api/
Dkref.rst146 Don't assume you know what you are doing and use the above construct.
147 First of all, you may not know what you are doing. Second, you may
148 know what you are doing (there are some situations where locking is
150 know what they are doing may change the code or copy the code. It's
234 same lock. Note that doing everything in the release routine is still
/Linux-v6.1/drivers/thunderbolt/
DKconfig27 Only enable this if you know what you are doing! Never enable
53 are doing. Normal users and distro kernels should say N here.
/Linux-v6.1/Documentation/admin-guide/nfs/
Dnfsd-admin-interfaces.rst14 Before doing that, NFSD can be told which sockets to listen on by
22 If nfsd is started without doing any of these, then it will create one
/Linux-v6.1/Documentation/sh/
Dregister-banks.rst28 registers when doing exception handling).
32 - Used by do_IRQ() and friends for doing irq mapping based off
/Linux-v6.1/Documentation/ABI/testing/
Dprocfs-diskstats22 13 time spent doing I/Os (ms)
23 14 weighted time spent doing I/Os (ms)
Dsysfs-class-fpga-manager34 * write complete = Doing post programming steps
35 * write complete error = Error while doing post programming
/Linux-v6.1/arch/powerpc/include/asm/
Dxive-regs.h20 * When doing an EOI, the Q bit will indicate if the interrupt
28 * Additionally, some ESB pages support doing an EOI via a
29 * store at 0 and some ESBs support doing a trigger via a
/Linux-v6.1/Documentation/mm/
Dpage_frags.rst21 advantage to doing this is that multiple calls to get_page can be avoided
41 page via a single call. The advantage to doing this is that it allows for
/Linux-v6.1/tools/testing/selftests/arm64/abi/
Dsyscall-abi-asm.S60 // Set SVCR if we're doing SME
95 // Load FPRs if we're not doing SVE
116 // Load the SVE registers if we're doing SVE/SME
222 // Save SVCR if we're doing SME
312 // Clear SVCR if we were doing SME so future tests don't have ZA
/Linux-v6.1/arch/powerpc/
DKconfig813 want. Only change this if you know what you are doing.
826 Say N here unless you know what you are doing.
1025 Say Y unless you know what you are doing and the filter is causing
1132 Unless you know what you are doing, say N here.
1147 Say N here unless you know what you are doing.
1163 Say N here unless you know what you are doing.
1199 Say N here unless you know what you are doing.
1214 Say N here unless you know what you are doing.
1228 Say N here unless you know what you are doing.
1251 Say N here unless you know what you are doing.
/Linux-v6.1/arch/openrisc/kernel/
Dunwinder.c40 * Create a stack trace doing scanning which is frame pointer aware. We can
90 * Create a stack trace by doing a simple scan treating all text addresses
/Linux-v6.1/tools/perf/util/
Dpath.c3 * I'm tired of doing "vsnprintf()" etc just to open a
8 * useful for doing things like
/Linux-v6.1/tools/testing/selftests/vm/
Dprotection_keys.c710 dprintf1("doing %s(size=%ld, prot=0x%x, pkey=%d)\n", __func__, in malloc_pkey_with_mprotect()
729 dprintf1("doing %s(size=%ld, prot=0x%x, pkey=%d)\n", __func__, in malloc_pkey_anon_huge()
813 dprintf1("doing %s(%ld, %x, %x)\n", __func__, size, prot, pkey); in malloc_pkey_hugetlb()
831 dprintf1("doing %s(size=%ld, prot=0x%x, pkey=%d)\n", __func__, in malloc_pkey_mmap_dax()
1027 dprintf1("disabling write access to PKEY[1], doing read\n"); in test_read_of_write_disabled_region()
1037 dprintf1("disabling access to PKEY[%02d], doing read @ %p\n", pkey, ptr); in test_read_of_access_disabled_region()
1050 dprintf1("disabling access to PKEY[%02d], doing read @ %p\n", in test_read_of_access_disabled_region_with_page_already_mapped()
1067 "to PKEY[%02d], doing write\n", pkey); in test_write_of_write_disabled_region_with_page_already_mapped()
1075 dprintf1("disabling write access to PKEY[%02d], doing write\n", pkey); in test_write_of_write_disabled_region()
1082 dprintf1("disabling access to PKEY[%02d], doing write\n", pkey); in test_write_of_access_disabled_region()
[all …]
/Linux-v6.1/drivers/md/bcache/
Dclosure.h18 * progress" - in flight bios, some other thread that's doing something else -
75 * closure - _always_ use continue_at(). Doing so consistently will help
98 * as doing a tail call.
126 * continue_at() and closure_return() clear it for you, if you're doing
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
Duncore-memory.json191 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
201 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
211 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
221 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
231 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
241 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
251 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
261 …E ON mode at one time, the counter will ONLY increment by one rather than doing accumulation. Mul…
/Linux-v6.1/Documentation/admin-guide/
Drtc.rst66 A user process can monitor these interrupts by doing a read(2) or a
91 the process of doing this, the kernel briefly turns off RTC periodic
92 interrupts, so be aware of this if you are doing serious work. If you
/Linux-v6.1/drivers/gpio/
DTODO55 driver infrastructure for doing simpler MMIO GPIO devices and there was
68 #include <linux/gpio/consumer.h> and stop doing custom parsing of the
73 gpiolib-of.c: in some cases subsystems are doing custom flags and
/Linux-v6.1/include/linux/
Dasync.h82 * context for where to run the function. By doing this we can try to
101 * context for where to run the function. By doing this we can try to

12345678910>>...92