| /kernel/linux/linux-4.19/drivers/staging/erofs/ |
| D | xattr.c | 25 static inline void xattr_iter_end(struct xattr_iter *it, bool atomic) in xattr_iter_end() argument
29 kunmap(it->page); in xattr_iter_end()
31 kunmap_atomic(it->kaddr); in xattr_iter_end()
33 unlock_page(it->page); in xattr_iter_end()
34 put_page(it->page); in xattr_iter_end()
37 static inline void xattr_iter_end_final(struct xattr_iter *it) in xattr_iter_end_final() argument
39 if (!it->page) in xattr_iter_end_final()
42 xattr_iter_end(it, true); in xattr_iter_end_final()
48 struct xattr_iter it; in init_inode_xattrs() local
69 * 1) it is not enough to contain erofs_xattr_ibody_header then in init_inode_xattrs()
[all …]
|
| /kernel/linux/linux-5.10/fs/erofs/ |
| D | xattr.c | 19 static inline void xattr_iter_end(struct xattr_iter *it, bool atomic) in xattr_iter_end() argument
23 kunmap(it->page); in xattr_iter_end()
25 kunmap_atomic(it->kaddr); in xattr_iter_end()
27 unlock_page(it->page); in xattr_iter_end()
28 put_page(it->page); in xattr_iter_end()
31 static inline void xattr_iter_end_final(struct xattr_iter *it) in xattr_iter_end_final() argument
33 if (!it->page) in xattr_iter_end_final()
36 xattr_iter_end(it, true); in xattr_iter_end_final()
42 struct xattr_iter it; in init_inode_xattrs() local
70 * 1) it is not enough to contain erofs_xattr_ibody_header then in init_inode_xattrs()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | hpfs.txt | 9 is taken from it
16 Set owner/group/mode for files that do not have it specified in extended
25 - there is a list of text extensions (I thing it's better to not convert
27 change it in the source. Original readonly HPFS contained some strange
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
36 used for debugging (for example it checks if file is allocated in
37 bitmaps when accessing it).
41 When to mark filesystem dirty so that OS/2 checks it.
63 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | path-lookup.md | 20 exploration is needed to discover, is that it is complex. There are
23 acquainted with such complexity and has tools to help manage it. One
49 It is tempting to describe the second kind as starting with a
51 slashes and components, it can be empty, in other words. This is
53 in Linux permit it when the `AT_EMPTY_PATH` flag is given. For
55 can execute it by calling [`execveat()`] passing the file descriptor,
60 it must identify a directory that already exists, otherwise an error
64 calls interpret it quite differently (e.g. some create it, some do
65 not), but it might not even exist: neither the empty pathname nor the
66 pathname that is just slashes have a final component. If it does
[all …]
|
| D | porting | 51 informative error value to report). Call it foo_fill_super(). Now declare
80 it by internal locking (most of filesystems couldn't care less) - you
88 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
98 individual fs sb_op functions. If you don't need it, remove it.
104 free to drop it...
116 an existing filesystem, set it according to ->fs_flags:
120 FS_LITTER is gone - just remove it from fs_flags.
126 went in - and hadn't been documented ;-/). Just remove it from fs_flags
144 Briefly it allows for the definition of decode_fh and encode_fh operations
149 It is planned that this will be required for exporting once the code
[all …]
|
| /kernel/linux/linux-5.10/drivers/accessibility/speakup/ |
| D | Kconfig | 8 This is the Speakup screen reader. Think of it as a
10 kernel, it can speak everything on the text console from
54 synthesizer. You can say y to build it into the kernel,
55 or m to build it as a module. See the configuration
63 synthesizer. You can say y to build it into the kernel,
64 or m to build it as a module. See the configuration
71 synthesizer. You can say y to build it into the kernel,
72 or m to build it as a module. See the configuration
79 You can say y to build it into the kernel, or m to
80 build it as a module. See the configuration help on the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
14 to do with reality. It started as a lark, but that doesn't mean that it
17 Btw, when talking about "kernel manager", it's all about the technical
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
60 It helps to realize that the key difference between a big decision and a
75 It turns out that since nobody would be stupid enough to ever really let
76 a kernel manager have huge fiscal responsibility **anyway**, it's usually
83 you made a year ago wasn't a big decision after all, since it could be
[all …]
|
| /kernel/linux/linux-4.19/Documentation/process/ |
| D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
13 to do with reality. It started as a lark, but that doesn't mean that it
16 Btw, when talking about "kernel manager", it's all about the technical
23 People", and NOT read it. Burn it, it's a great symbolic gesture.
26 making it painfully obvious to the questioner that we don't have a clue
38 manager must be to make it. That's very deep and obvious, but it's not
59 It helps to realize that the key difference between a big decision and a
74 It turns out that since nobody would be stupid enough to ever really let
75 a kernel manager have huge fiscal responsibility **anyway**, it's usually
82 you made a year ago wasn't a big decision after all, since it could be
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 20 a program is suspended and instructions belonging to it are not fetched from
25 it is an opportunity to save energy.
39 (program) from memory and executing them, but it need not work this way
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
52 enter an idle state, that applies to the core that asked for it in the first
53 place, but it also may apply to a larger unit (say a "package" or a "cluster")
54 that the core belongs to (in fact, it may apply to an entire hierarchy of larger
57 remaining core asks the processor to enter an idle state, that may trigger it
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
[all …]
|
| D | cpufreq.rst | 28 In some situations it is desirable or even necessary to run the program as fast
31 available). In some other cases, however, it may not be necessary to execute
33 relatively long time without utilizing it entirely may be regarded as wasteful.
34 It also may not be physically possible to maintain maximum CPU capacity for too
44 to as CPU performance scaling or CPU frequency scaling (because it involves
56 interfaces for all platforms that support CPU performance scaling. It defines
71 platform-independent form in the majority of cases, so it should be possible
79 interface it comes from and may not be easily represented in an abstract,
90 control the P-state of multiple CPUs at the same time and writing to it affects
111 It is only possible to register one scaling driver at a time, so the scaling
[all …]
|
| /kernel/linux/linux-4.19/drivers/staging/speakup/ |
| D | Kconfig | 7 This is the Speakup screen reader. Think of it as a
9 kernel, it can speak everything on the text console from
48 synthesizer. You can say y to build it into the kernel,
49 or m to build it as a module. See the configuration
57 synthesizer. You can say y to build it into the kernel,
58 or m to build it as a module. See the configuration
65 synthesizer. You can say y to build it into the kernel,
66 or m to build it as a module. See the configuration
73 You can say y to build it into the kernel, or m to
74 build it as a module. See the configuration help on the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 5 It is a read only file. It contains status of the watchdog
6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
13 It is a read only file. It contains identity string of
20 It is a read/write file. While reading, it gives '1'
22 it gives '0'. Writing a '1' to the file enables the
32 It is a read only file. It gives active/inactive status of
39 It is a read only file. It contains watchdog device's
40 internal status bits. It is equivalent to WDIOC_GETSTATUS
47 It is a read only file. It contains value of time left for
48 reset generation. It is equivalent to WDIOC_GETTIMELEFT of
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | hpfs.rst | 15 is taken from it
24 Set owner/group/mode for files that do not have it specified in extended
33 - there is a list of text extensions (I thing it's better to not convert
35 change it in the source. Original readonly HPFS contained some strange
36 heuristic algorithm that I removed. I thing it's danger to let the
42 danger. I tried to write it so that it won't crash if check=normal on
44 used for debugging (for example it checks if file is allocated in
45 bitmaps when accessing it).
49 When to mark filesystem dirty so that OS/2 checks it.
72 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | path-lookup.rst | 12 It has subsequently been updated to reflect changes in the kernel
22 exploration is needed to discover, is that it is complex. There are
25 acquainted with such complexity and has tools to help manage it. One
51 It is tempting to describe the second kind as starting with a
53 slashes and components, it can be empty, in other words. This is
55 in Linux permit it when the ``AT_EMPTY_PATH`` flag is given. For
57 can execute it by calling `execveat() <execveat_>`_ passing
62 it must identify a directory that already exists, otherwise an error
66 calls interpret it quite differently (e.g. some create it, some do
67 not), but it might not even exist: neither the empty pathname nor the
[all …]
|
| D | porting.rst | 58 informative error value to report). Call it foo_fill_super(). Now declare::
89 it by internal locking (most of filesystems couldn't care less) - you
98 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
109 individual fs sb_op functions. If you don't need it, remove it.
116 free to drop it...
130 an existing filesystem, set it according to ->fs_flags::
136 FS_LITTER is gone - just remove it from fs_flags.
143 went in - and hadn't been documented ;-/). Just remove it from fs_flags
163 Briefly it allows for the definition of decode_fh and encode_fh operations
168 It is planned that this will be required for exporting once the code
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 5 It is a read only file. It contains status of the watchdog
6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
13 It is a read only file. It contains identity string of
20 It is a read only file. While reading, it gives '1' if that
21 device supports nowayout feature else, it gives '0'.
27 It is a read only file. It gives active/inactive status of
34 It is a read only file. It contains watchdog device's
35 internal status bits. It is equivalent to WDIOC_GETSTATUS
42 It is a read only file. It contains value of time left for
43 reset generation. It is equivalent to WDIOC_GETTIMELEFT of
[all …]
|
| /kernel/linux/linux-5.10/net/netfilter/ipvs/ |
| D | Kconfig | 24 If you want to compile it in kernel, say Y. To compile it as a
59 performance on it. You can adapt the table size yourself, according
60 to your virtual server application. It is good to set the table size
65 should be not far less than 200x200, it is good to set the table
120 If you want to compile it in kernel, say Y. To compile it as a
133 If you want to compile it in kernel, say Y. To compile it as a
143 If you want to compile it in kernel, say Y. To compile it as a
153 If you want to compile it in kernel, say Y. To compile it as a
163 If you want to compile it in kernel, say Y. To compile it as a
174 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 25 In some situations it is desirable or even necessary to run the program as fast
28 available). In some other cases, however, it may not be necessary to execute
30 relatively long time without utilizing it entirely may be regarded as wasteful.
31 It also may not be physically possible to maintain maximum CPU capacity for too
41 to as CPU performance scaling or CPU frequency scaling (because it involves
53 interfaces for all platforms that support CPU performance scaling. It defines
68 platform-independent form in the majority of cases, so it should be possible
76 interface it comes from and may not be easily represented in an abstract,
87 control the P-state of multiple CPUs at the same time and writing to it affects
108 It is only possible to register one scaling driver at a time, so the scaling
[all …]
|
| /kernel/linux/linux-4.19/drivers/misc/vmw_vmci/ |
| D | vmci_route.c | 6 * This program is free software; you can redistribute it and/or modify it
10 * This program is distributed in the hope that it will be useful, but
26 * devices. Will set the source context if it is invalid.
41 * which comes from the VMX, so we know it is coming from a in vmci_route()
58 * cannot send it to the hypervisor. It must come in vmci_route()
77 * respect it (both context and resource are invalid). in vmci_route()
80 * should set the real context here before passing it in vmci_route()
95 * If it is not from a guest but we are acting as a in vmci_route()
96 * guest, then we need to send it down to the host. in vmci_route()
107 * itself, but it will never send datagrams to in vmci_route()
[all …]
|
| /kernel/linux/linux-4.19/net/netfilter/ipvs/ |
| D | Kconfig | 23 If you want to compile it in kernel, say Y. To compile it as a
59 performance on it. You can adapt the table size yourself, according
60 to your virtual server application. It is good to set the table size
65 should be not far less than 200x200, it is good to set the table
120 If you want to compile it in kernel, say Y. To compile it as a
133 If you want to compile it in kernel, say Y. To compile it as a
143 If you want to compile it in kernel, say Y. To compile it as a
153 If you want to compile it in kernel, say Y. To compile it as a
163 If you want to compile it in kernel, say Y. To compile it as a
174 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | matroxfb.txt | 11 * It provides a nice large console (128 cols + 48 lines with 1024x768)
22 How to use it?
82 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
97 Driver contains SVGALib compatibility code. It is turned on by choosing textual
98 mode for console. You can do it at boot time by using videomode
101 Switching to another console and back fixes it. I hope that it is SVGALib's
115 it always probe for memory. Default is to use whole detected
120 configuration, you can override it by this (you cannot override
121 `off'). It is default.
122 noaccel - do not use acceleration engine. It does not work on Alphas.
[all …]
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/ |
| D | vmm.c | 98 nvkm_vmm_trace(struct nvkm_vmm_iter *it, char *buf) in nvkm_vmm_trace() argument
101 for (lvl = it->max; lvl >= 0; lvl--) { in nvkm_vmm_trace()
102 if (lvl >= it->lvl) in nvkm_vmm_trace()
103 buf += sprintf(buf, "%05x:", it->pte[lvl]); in nvkm_vmm_trace()
120 nvkm_vmm_flush_mark(struct nvkm_vmm_iter *it) in nvkm_vmm_flush_mark() argument
122 it->flush = min(it->flush, it->max - it->lvl); in nvkm_vmm_flush_mark()
126 nvkm_vmm_flush(struct nvkm_vmm_iter *it) in nvkm_vmm_flush() argument
128 if (it->flush != NVKM_VMM_LEVELS_MAX) { in nvkm_vmm_flush()
129 if (it->vmm->func->flush) { in nvkm_vmm_flush()
130 TRA(it, "flush: %d", it->flush); in nvkm_vmm_flush()
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 24 If you choose to build it as a module, it will be called rtl8192ce
35 If you choose to build it as a module, it will be called rtl8192se
46 If you choose to build it as a module, it will be called rtl8192de
59 If you choose to build it as a module, it will be called rtl8723ae
72 If you choose to build it as a module, it will be called rtl8723be
83 If you choose to build it as a module, it will be called rtl8188ee
95 If you choose to build it as a module, it will be called rtl8192ee
107 If you choose to build it as a module, it will be called rtl8821ae
119 If you choose to build it as a module, it will be called rtl8192cu
|
| /kernel/linux/linux-5.10/drivers/misc/vmw_vmci/ |
| D | vmci_route.c | 18 * devices. Will set the source context if it is invalid.
33 * which comes from the VMX, so we know it is coming from a in vmci_route()
50 * cannot send it to the hypervisor. It must come in vmci_route()
69 * respect it (both context and resource are invalid). in vmci_route()
72 * should set the real context here before passing it in vmci_route()
87 * If it is not from a guest but we are acting as a in vmci_route()
88 * guest, then we need to send it down to the host. in vmci_route()
99 * itself, but it will never send datagrams to in vmci_route()
116 /* Send it from local client down to the host. */ in vmci_route()
122 * Otherwise we already received it from a guest and in vmci_route()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | pci.txt | 31 Usually, a device is put into a low-power state when it is underutilized or
32 completely inactive. However, when it is necessary to use the device once
33 again, it has to be put back into the "fully functional" state (full-power
50 to put the device that sent it into the full-power state. However, the PCI Bus
53 It is assumed that the platform firmware will perform this task and therefore,
54 even though a PCI device is set up to generate PMEs, it also may be necessary to
60 preparing the device to generate wakeup signals. In that case, however, it
71 introduced between the PCI 2.1 and PCI 2.2 Specifications. It defined a
76 but it is mandatory for PCI Express devices. If a device supports the PCI PM
77 Spec, it has an 8 byte power management capability field in its PCI
[all …]
|