/linux/fs/erofs/ |
H A D | xattr.c | 31 struct erofs_xattr_iter it; in erofs_init_inode_xattrs() local 57 * 1) it is not enough to contain erofs_xattr_ibody_header then in erofs_init_inode_xattrs() 58 * ->xattr_isize should be 0 (it means no xattr); in erofs_init_inode_xattrs() 59 * 2) it is just to contain erofs_xattr_ibody_header, which is on-disk in erofs_init_inode_xattrs() 79 it.buf = __EROFS_BUF_INITIALIZER; in erofs_init_inode_xattrs() 80 ret = erofs_init_metabuf(&it.buf, sb, erofs_inode_in_metabox(inode)); in erofs_init_inode_xattrs() 83 it.pos = erofs_iloc(inode) + vi->inode_isize; in erofs_init_inode_xattrs() 86 it.kaddr = erofs_bread(&it.buf, it.pos, true); in erofs_init_inode_xattrs() 87 if (IS_ERR(it.kaddr)) { in erofs_init_inode_xattrs() 88 ret = PTR_ERR(it.kaddr); in erofs_init_inode_xattrs() [all …]
|
/linux/tools/lib/bpf/ |
H A D | btf_iter.c | 16 int btf_field_iter_init(struct btf_field_iter *it, struct btf_type *t, in btf_field_iter_init() argument 19 it->p = NULL; in btf_field_iter_init() 20 it->m_idx = -1; in btf_field_iter_init() 21 it->off_idx = 0; in btf_field_iter_init() 22 it->vlen = 0; in btf_field_iter_init() 32 it->desc = (struct btf_field_desc) {}; in btf_field_iter_init() 44 it->desc = (struct btf_field_desc) { 1, {offsetof(struct btf_type, type)} }; in btf_field_iter_init() 47 it->desc = (struct btf_field_desc) { in btf_field_iter_init() 54 it->desc = (struct btf_field_desc) { in btf_field_iter_init() 61 it->desc = (struct btf_field_desc) { in btf_field_iter_init() [all …]
|
/linux/drivers/usb/typec/mux/ |
H A D | it5205.c | 71 struct it5205 *it = typec_switch_get_drvdata(sw); in it5205_switch_set() local 75 regmap_update_bits(it->regmap, IT5205_REG_MUXCR, in it5205_switch_set() 79 regmap_update_bits(it->regmap, IT5205_REG_MUXCR, in it5205_switch_set() 85 regmap_write(it->regmap, IT5205_REG_MUXCR, 0); in it5205_switch_set() 94 struct it5205 *it = typec_mux_get_drvdata(mux); in it5205_mux_set() local 120 return regmap_update_bits(it->regmap, IT5205_REG_MUXCR, in it5205_mux_set() 126 struct it5205 *it = data; in it5205_irq_handler() local 130 ret = regmap_read(it->regmap, IT5205_REG_ISR, &val); in it5205_irq_handler() 135 dev_warn(&it->client->dev, "Overvoltage detected!\n"); in it5205_irq_handler() 138 regmap_update_bits(it->regmap, IT5205_REG_CSBUSR, in it5205_irq_handler() [all …]
|
/linux/Documentation/ABI/testing/ |
H A 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 options of watchdog device. 19 It is a read only file. It contains firmware version of 26 It is a read only file. It contains identity string of 33 It is a read/write file. While reading, it gives '1' 35 it gives '0'. Writing a '1' to the file enables the 45 It is a read only file. It gives active/inactive status of 52 It is a read only file. It contains watchdog device's 53 internal status bits. It is equivalent to WDIOC_GETSTATUS [all …]
|
/linux/Documentation/process/ |
H A 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 …]
|
H A D | handling-regressions.rst | 8 Linux kernel development" means in practice for developers. It complements 10 user's point of view; if you never read that text, go and at least skim over it 20 * When receiving a mailed report that did not CC the list, bring it into the 72 it into the loop by sending at least a brief "Reply-all" with the list CCed; 73 try to ensure it gets CCed again in case you reply to a reply that omitted 76 * If a report submitted in a bug tracker hits your Inbox, forward or bounce it 94 Note the caret (^) before the "introduced": it tells regzbot to treat the 132 All this is expected from you and important when it comes to regression, as 151 than three weeks after the regression's culprit was identified. Ideally it 152 should be less than two. And it ought to be just a few days, if the issue is [all …]
|
/linux/drivers/accessibility/speakup/ |
H A 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 55 synthesizer. You can say y to build it into the kernel, 56 or m to build it as a module. See the configuration 64 synthesizer. You can say y to build it into the kernel, 65 or m to build it as a module. See the configuration 72 synthesizer. You can say y to build it into the kernel, 73 or m to build it as a module. See the configuration 80 You can say y to build it into the kernel, or m to 81 build it as a module. See the configuration help on the [all …]
|
/linux/Documentation/filesystems/caching/ |
H A D | netfs-api.rst | 63 blob into something it can use and may employ hash tables, trees or whatever to 67 A filesystem would typically have a cookie for each inode, and would acquire it 68 in iget and relinquish it when evicting the cookie. 70 Once it has a cookie, the filesystem needs to mark the cookie as being in use. 76 unuse it in file release and it needs to use the cookie around calls to 77 truncate the cookie locally. It *also* needs to use the cookie when the 78 pagecache becomes dirty and unuse it when writeback is complete. This is 79 slightly tricky, and provision is made for it. 88 actually required and it can use the fscache I/O API directly. 95 volume it wants to access:: [all …]
|
/linux/net/netfilter/ipvs/ |
H A D | Kconfig | 24 If you want to compile it in kernel, say Y. To compile it as a 60 small, otherwise you will lose performance on it. You can adapt the 62 It is good to set the table size not far less than the number of 67 less than 200x200, it is good to set the table size 32768 (2**15). 121 If you want to compile it in kernel, say Y. To compile it as a 134 If you want to compile it in kernel, say Y. To compile it as a 144 If you want to compile it in kernel, say Y. To compile it as a 154 If you want to compile it in kernel, say Y. To compile it as a 164 If you want to compile it in kernel, say Y. To compile it as a 175 If you want to compile it in kernel, say Y. To compile it as a [all …]
|
/linux/Documentation/translations/it_IT/process/ |
H A D | programming-language.rst | 4 :Translator: Federico Vaga <federico.vaga@vaga.pv.it> 11 Il kernel è scritto nel linguaggio di programmazione C [it-c-language]_. 12 Più precisamente, il kernel viene compilato con ``gcc`` [it-gcc]_ usando 13 l'opzione ``-std=gnu11`` [it-gcc-c-dialect-options]_: il dialetto GNU 15 Linux supporta anche ``clang`` [it-clang]_, leggete la documentazione 18 Questo dialetto contiene diverse estensioni al linguaggio [it-gnu-extensions]_, 25 [it-gcc-attribute-syntax]_. Gli attributi permettono di aggiungere una semantica, 28 linguaggio stesso (come l'aggiunta di nuove parole chiave) [it-n2049]_. 46 [it-rust-language]_ abilitando l'opzione di configurazione ``CONFIG_RUST``. Il 47 codice verrà compilato usando ``rustc`` [it-rustc]_ con l'opzione [all …]
|
/linux/Documentation/admin-guide/pm/ |
H A 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 …]
|
H A D | sleep-states.rst | 21 Depending on its configuration and the capabilities of the platform it runs on, 32 referred to as S2I or S2Idle). It allows more energy to be saved relative to 43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the 44 deeper system suspend variants to provide reduced resume latency. It is always 55 go back to where it left off easily enough. 60 are suspended during transitions into this state. For this reason, it should 65 reduced relative to :ref:`suspend-to-idle <s2idle>` and it may be necessary to 69 option is set and the support for it is registered by the platform with the 94 platform firmware to resume the system from it. This may be the case on other 98 relative to :ref:`suspend-to-idle <s2idle>` and :ref:`standby <standby>` and it [all …]
|
H A D | intel_pstate.rst | 18 (``CPUFreq``). It is a scaling driver for the Sandy Bridge and later 20 may not be supported. [To understand ``intel_pstate`` it is necessary to know 31 frequencies are involved in the user space interface exposed by it, so 33 (fortunately, that mapping is unambiguous). At the same time, it would not be 35 available frequencies due to the possible size of it, so the driver does not do 44 it goes back online. 46 ``intel_pstate`` is not modular, so it cannot be unloaded, which means that the 47 only way to pass early-configuration-time parameters to it is via the kernel 49 great extent. In some configurations it even is possible to unregister it via 58 active mode, it uses its own internal performance scaling governor algorithm or [all …]
|
/linux/drivers/net/wireless/realtek/rtlwifi/ |
H A 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 47 If you choose to build it as a module, it will be called rtl8192de 60 If you choose to build it as a module, it will be called rtl8723ae 73 If you choose to build it as a module, it will be called rtl8723be 84 If you choose to build it as a module, it will be called rtl8188ee 96 If you choose to build it as a module, it will be called rtl8192ee 108 If you choose to build it as a module, it will be called rtl8821ae 120 If you choose to build it as a module, it will be called rtl8192cu 132 If you choose to build it as a module, it will be called rtl8192du
|
/linux/drivers/misc/vmw_vmci/ |
H A 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 …]
|
/linux/Documentation/fb/ |
H A D | matroxfb.rst | 10 * It provides a nice large console (128 cols + 48 lines with 1024x768) 21 How to use it? 90 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel 105 Driver contains SVGALib compatibility code. It is turned on by choosing textual 106 mode for console. You can do it at boot time by using videomode 109 Switching to another console and back fixes it. I hope that it is SVGALib's 124 it always probe for memory. Default is to use whole detected 129 configuration, you can override it by this (you cannot override 130 `off`). It is default. 131 noaccel do not use acceleration engine. It does not work on Alphas. [all …]
|
/linux/Documentation/userspace-api/media/dvb/ |
H A D | frontend-stat-properties.rst | 16 It should be noted, however, that new OFDM delivery systems like ISDB 36 - ``scale`` - Scale for the value. It can be: 39 frontend, but it was not possible to collect it (could be a 63 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the 82 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the 103 In order to get the BER (Bit Error Rate) measurement, it should be 108 bit count measurements. The frontend may reset it when a 113 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the 130 It should be noted that this measurement can be smaller than the total 136 bit count measurements. The frontend may reset it when a [all …]
|
/linux/Documentation/security/keys/ |
H A D | request-key.rst | 46 does not need to link the key to a keyring to prevent it from being immediately 48 it's up to the caller to destroy the key. 50 The request_key_tag() call is like the in-kernel request_key(), except that it 59 The request_key_rcu() call is like the request_key_tag() call, except that it 82 a suitable key there. If there is, it returns the key. If there isn't, 86 3) request_key() sees that A doesn't have the desired key yet, so it creates 104 Kerberos TGT key). It just requests the appropriate key, and the keyring 107 This will permit it to then search the keyrings of process A with the 108 UID, GID, groups and security info of process A as if it was process A, 111 8) The program then does what it must to get the data with which to [all …]
|
/linux/Documentation/filesystems/xfs/ |
H A D | xfs-self-describing-metadata.rst | 14 adequate for supporting PB scale filesystems with billions of inodes, however it 24 For example, it is entirely possible to manually use xfs_db and a bit of 26 determine the root cause of a corruption problem, but it is still mainly a 28 weren't the ultimate cause of a corruption event. It may take a few hours to a 44 magic number in the metadata block, we have no other way of identifying what it 45 is supposed to be. We can't even identify if it is the right place. Put simply, 46 you can't look at a single metadata block in isolation and say "yes, it is 54 went wrong, but it is impossible to tell what order the blocks were linked into 74 numbers in the metadata objects. That is, if it has the current magic number, 75 the metadata isn't self identifying. If it contains a new magic number, it is [all …]
|
/linux/Documentation/filesystems/ |
H A D | porting.rst | 64 informative error value to report). Call it foo_fill_super(). Now declare:: 95 it by internal locking (most of filesystems couldn't care less) - you 104 and ->readdir() are called without BKL now. Grab it on entry, drop upon return 115 individual fs sb_op functions. If you don't need it, remove it. 122 free to drop it... 136 an existing filesystem, set it according to ->fs_flags:: 142 FS_LITTER is gone - just remove it from fs_flags. 149 went in - and hadn't been documented ;-/). Just remove it from fs_flags 169 Briefly it allows for the definition of decode_fh and encode_fh operations 174 It is planned that this will be required for exporting once the code [all …]
|
H A D | configfs.rst | 22 is discovered) and it is registered with sysfs. Its attributes then 24 readdir(3)/read(2). It may allow some attributes to be modified via 30 mkdir(2). It is destroyed via rmdir(2). The attributes appear at 44 it by doing:: 50 subsystems. Once a client subsystem is loaded, it will appear as a 73 write_bin_attribute method will be invoked on the final close, therefore it is 79 When an item needs to be destroyed, remove it with rmdir(2). An 80 item cannot be destroyed if any other item has a link to it (via 87 access remote block devices. Call it FakeNBD. FakeNBD uses configfs 90 the driver about it. Here's where configfs comes in. [all …]
|
/linux/Documentation/driver-api/usb/ |
H A D | persist.rst | 20 required to behave as though the device has been unplugged. It's a 23 device is still attached or perhaps it was removed and a different 29 though they had disconnected. This is always safe and it is the 35 system woke up, who cares? It'll still work the same when you type on 36 it. 52 it's as though you had unplugged all the USB devices. Yes, it's 64 the system can't be suspended at all. (All right, it _can_ be 65 suspended -- but it will crash as soon as it wakes up, which isn't 72 The kernel includes a feature called USB-persist. It tries to work 76 It works like this. If the kernel sees that a USB host controller is [all …]
|
/linux/Documentation/power/ |
H A D | swsusp.rst | 21 it may cause some problems, too. If you change kernel command line 22 between suspend and resume, it may do something wrong. If you change 23 your hardware while system is suspended... well, it was not good idea; 24 but it will probably only crash. 26 ( ) suspend/resume support is needed to make it safe. 36 line or specify it using /sys/power/resume. 40 resume_offset=<number> on the kernel command line or specify it 52 to RAM (provided your platform supports it), you can try:: 66 before suspend (it is limited to around 2/5 of available RAM by default). 69 if found, it then checks the contents for the hibernation image signature. [all …]
|
/linux/net/netfilter/ |
H A D | Kconfig | 93 Address Translation. It can also be used to enhance packet 96 To compile it as a module, choose M here. If unsure, say N. 103 It supports IPv4, IPV6, ARP and common transport protocols such 183 the flow-stop time (once it has been destroyed) via Connection 192 to connection tracking entries. It can be used with xtables connlabel 236 To compile it as a module, choose M here. If unsure, say N. 248 To compile it as a module, choose M here. If unsure, say N. 256 important VoIP protocols, it is widely used by voice hardware and 268 To compile it as a module, choose M here. If unsure, say N. 283 To compile it as a module, choose M here. If unsure, say N. [all …]
|
/linux/tools/testing/ktest/ |
H A D | sample.conf | 6 # called "ktest.conf", but you can name it anything you like and specify 28 # to it followed by the number of times you want that test 75 # DEFAULTS tag and add it to the second. Be careful, options 89 # been defined previously. It will only override options that 105 # otherwise if it evaluates to zero, it will act the same 146 # It returns true if the given config variable or option has been defined 279 # typing it again in that option you can simply use the option 436 # it sends the mail if "$FOO" format is used. If "${FOO}" format is used, 457 # It is possible that the log may be very large, in which case, 469 # This is a label and not really an option (it takes no value). [all …]
|