Searched full:will (Results 401 – 425 of 20917) sorted by relevance
1...<<11121314151617181920>>...837
| /linux-6.15/init/ |
| D | Kconfig | 11 When the compiler is updated, Kconfig will be invoked.
17 will touch it and then every file will be rebuilt.
158 make this work, an arch will need to remove all thread_info fields
161 One subtle change that will be needed is to use try_get_task_stack()
183 bool "Compile also drivers which will not load"
227 This will show up when you type uname, for example.
228 The string you set here will be appended after the contents of
238 This will try to automatically determine if the current tree is a
242 A string of the format -gxxxxxxxx will be added to the localversion
243 if a git-based tree is found. The string generated by this will be
[all …]
|
| /linux-6.15/Documentation/admin-guide/cgroup-v1/ |
| D | memory.rst | 103 do file will not have any effect same as if
213 Some pages which are never reclaimable and will not be on the LRU
217 for earlier. A file page will be accounted for as Page Cache when it's
228 Since page's memcg recorded into swap whatever memsw enabled, the page will
242 page will eventually get charged for it (once it is uncharged from
243 the cgroup that brought it in -- this will happen on memory pressure).
260 (by mistake) under 2G memory limitation will use all swap.
261 In this case, setting memsw.limit_in_bytes=3G will prevent bad use of swap.
278 in this cgroup. Then, swap-out will not be done by cgroup routine and file
302 When panic_on_oom is set to "2", the whole system will panic.
[all …]
|
| /linux-6.15/Documentation/arch/s390/ |
| D | vfio-ap.rst | 28 assigned to the LPAR in which a linux host is running will be available to
38 4 and 10 (0x0a) are assigned to the LPAR, the AP bus will create the following
44 Symbolic links to these devices will also be created in the AP bus devices
73 (see AP Queue section below). The domain number of each control domain will be
88 The AP bus will create a sysfs device for each APQN that can be derived from
91 domains 6 and 71 (0x47) are assigned to the LPAR, the AP bus will create the
99 The following symbolic links to these devices will be created in the AP bus
154 (1,5), (1,6), (2,5) and (2,6) will be valid for the guest.
252 2. The vfio-ap driver during its initialization will register a single 'matrix'
253 device with the device core. This will serve as the parent device for
[all …]
|
| /linux-6.15/Documentation/admin-guide/LSM/ |
| D | Smack.rst | 68 If smackutil is installed the startup script will take care
86 the label given to a new filesystem object will be the label
91 this attribute set will run with this attribute's value.
137 this file. The next read will indicate whether the access
138 would be permitted. The text will be either "1" indicating
145 this file. The next read will indicate whether the access
146 would be permitted. The text will be either "1" indicating
162 "rwxat-". If a rule for a given subject and object exists it will be
164 those in the fourth string. If there is no such rule it will be
212 If label is "-DELETE" a matched entry will be deleted.
[all …]
|
| /linux-6.15/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | kconfig.rst | 19 | This will provide the ability to add representors of mlx5 uplink and VF
27 | This will provide mlx5 core driver for mlx5 ulps to interface with (mlx5e, mlx5_ib).
32 | Choosing this option will allow basic ethernet netdevice support with all of the standard rx/t…
33 … mlx5e is the mlx5 ulp driver which provides netdevice kernel interface, when chosen, mlx5e will be
98 | If you select this option, the mlx5_core driver will include the Innova FPGA core and allow
118 | will enable support for creating subfunction devices.
157 | of virtio net datapath such that descriptors put on the ring will
169 - CONFIG_MLXFW: When chosen, mlx5 firmware flashing support will be enabled (via devlink and ethtoo…
170 - CONFIG_PTP_1588_CLOCK: When chosen, mlx5 ptp support will be enabled
171 - CONFIG_VXLAN: When chosen, mlx5 vxlan support will be enabled.
|
| /linux-6.15/include/drm/ |
| D | drm_modeset_lock.h | 154 * @ctx: local modeset acquire context, will be dereferenced
162 * Any code run between BEGIN and END will be holding the modeset locks.
164 * This must be paired with DRM_MODESET_LOCK_ALL_END(). We will jump back and
187 * @ctx: local modeset acquire context, will be dereferenced
190 * The other side of DRM_MODESET_LOCK_ALL_BEGIN(). It will bounce back to BEGIN
197 * ret will be untouched unless it is -EDEADLK on entry. That means that if you
198 * successfully acquire the locks, ret will be whatever your code sets it to. If
199 * there is a deadlock or other failure with acquire or backoff, ret will be set
200 * to that failure. In both of these cases the code between BEGIN/END will not
201 * be run, so the failure will reflect the inability to grab the locks.
|
| /linux-6.15/sound/soc/codecs/ |
| D | rt-sdw-common.c | 28 * A value of zero will be returned on success, a negative errno will
54 * A value of zero will be returned on success, a negative errno will
81 * A value of zero will be returned on success, a negative errno will
105 * A button type will be returned regarding to buffer,
137 * A headset jack type will be returned, a negative errno will
188 * A button type will be returned regarding to buffer,
|
| /linux-6.15/fs/ocfs2/ |
| D | reservations.h | 33 #define OCFS2_RESV_FLAG_TMP 0x02 /* Temporary reservation, will be
67 * After this function is called, the reservation will be empty, and
91 * This function will call ocfs2_trunc_resv against all existing
92 * reservations. A future version will recalculate existing
111 * Using the reservation data from resv, this function will compare
114 * this function will try to allocate a window for it.
135 * Internally, the reservations code will use this information to mark the
136 * reservations bitmap. If resv is passed, it's next allocation window will be
|
| /linux-6.15/Documentation/trace/ |
| D | hwlat_detector.rst | 40 redefine the threshold in microseconds (us) above which latency spikes will
55 for every 1,000,000 usecs (1s) the hwlat detector will spin for 500,000 usecs
56 (0.5s). If tracing_thresh contains zero when hwlat tracer is enabled, it will
58 observed then the data will be written to the tracing ring buffer.
64 If tracing_thresh was zero when hwlat detector was started, it will be set
66 tracing_thresh that hwlat detector had will be saved and this value will
81 By default, one hwlat detector's kernel thread will migrate across each CPU
|
| /linux-6.15/Documentation/ABI/testing/ |
| D | sysfs-bus-fcoe | 11 <ifname> to this file will allocate and populate sysfs with a
19 fcoe_ctlr_device's sysfs name to this file will log the
21 FCoE devices. It will also free all kernel memory allocated
40 this value will change the dev_loss_tmo for all
55 to this file will enable or disable the FCoE controller.
105 0 indicates that the switch will not be used.
131 used to identify the discovered FCF. FCFs will exist in a
137 Users: The first user of this interface will be the fcoeadm application,
|
| D | sysfs-platform-wilco-ec | 16 Output will a MM/DD/YY string.
23 Output will a version string be similar to the example below:
31 Output will a version string be similar to the example below:
43 - In S0, the port will always provide power.
44 - In S0ix, if usb_charge is enabled, then power will be
47 - In S5, if usb_charge is enabled, then power will be supplied
|
| /linux-6.15/drivers/net/arcnet/ |
| D | Kconfig | 19 To compile this driver as a module, choose M here. The module will
61 actually appear on the network. After transmit the driver will send
68 Received packets are also stuffed with the extra 4 bytes but it will
80 To compile this driver as a module, choose M here. The module will
91 To compile this driver as a module, choose M here. The module will
102 To compile this driver as a module, choose M here. The module will
113 To compile this driver as a module, choose M here. The module will
131 To compile this driver as a module, choose M here: the module will be
|
| /linux-6.15/sound/usb/ |
| D | Kconfig | 26 will be called snd-usb-audio.
50 will be called snd-ua101.
63 will be called snd-usb-usx2y.
90 will be called snd-usb-caiaq.
118 will be called snd-usb-us122l.
130 You will need firmware files in order to be able to use the device
164 will be called snd-usb-hiface.
177 will be called snd-bcd2000.
|
| /linux-6.15/include/linux/ |
| D | connector.h | 83 * If non-zero the message will be sent to the given port,
86 * If @portid and @group is zero, then appropriate group will
88 * message will be delivered to the group which was created
90 * If @group is not zero, then message will be delivered
111 * If non-zero the message will be sent to the given port,
114 * If @portid and @group is zero, then appropriate group will
116 * message will be delivered to the group which was created
118 * If @group is not zero, then message will be delivered
|
| /linux-6.15/Documentation/networking/devlink/ |
| D | devlink-params.rst | 41 support reloading via the ``devlink-reload`` command. This command will
64 enabled, the adapter will ignore ARI capability even when the
65 platform has support enabled. The device will create the same number
102 - When enabled, the device driver will instantiate Ethernet specific
106 - When enabled, the device driver will instantiate RDMA specific
110 - When enabled, the device driver will instantiate VDPA networking
117 - When enabled, the device driver will reset the device on internal
131 will NACK any attempt of other host to reset the device. This parameter
|
| /linux-6.15/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 94 is 0x15 and the full version number is 0x234, this file will contain
105 file will contain the value 564 = 0x234.
128 This is the pid which will be signalled on reboot (notably, by
130 correspond to a running process will result in ``-ESRCH``.
156 and ``core_uses_pid`` is set, then .PID will be appended to
183 * If the first character of the pattern is a '|', the kernel will treat
184 the rest of the pattern as a command to run. The core dump will be
209 captured in parallel, but that no waiting will take place (i.e. the
219 ``core_sort_vma`` to 1, VMAs will be written from smallest size
232 and ``core_uses_pid`` is set, then .PID will be appended to
[all …]
|
| /linux-6.15/drivers/media/pci/ivtv/ |
| D | Kconfig | 30 module will be called ivtv.
46 module will be called ivtv-alsa.
59 module will be called ivtvfb.
67 For this reason, the driver will by default disable itself
75 With this setting enabled, the framebuffer will initialize on
76 PAT-enabled systems but the framebuffer memory will be uncached.
|
| /linux-6.15/Documentation/translations/zh_CN/arch/arm64/ |
| D | tagged-pointers.txt | 9 Maintainer: Will Deacon <will.deacon@arm.com>
18 英文版维护者： Will Deacon <will.deacon@arm.com>
28 作者: Will Deacon <will.deacon@arm.com>
|
| /linux-6.15/drivers/net/ethernet/intel/fm10k/ |
| D | fm10k_tlv.c | 30 * This function will reorder a string to be CPU endian and store it in
31 * the attribute buffer. It will return success if provided with a valid
80 * This function pulls the string back out of the attribute and will place
81 * it in the array pointed by string. It will return success if provided
108 * This function will reorder a MAC address to be CPU endian and store it
109 * in the attribute buffer. It will return success if provided with a
145 * This function pulls the MAC address back out of the attribute and will
146 * place it in the array pointed by mac_addr. It will return success
167 * This function will simply add an attribute header, the fact
169 * it is false. The function will return success if provided with a
[all …]
|
| /linux-6.15/drivers/leds/ |
| D | Kconfig | 76 will be called leds-an30259a.
90 module will be called leds-apu.
118 will be called leds-aw200xx.
129 will be called leds-aw2013.
158 will be called leds-cht-wcove.
180 will be called leds-cr0014114.
195 will be called leds-cros_ec.
208 will be called leds-el15203000.
407 module will be called leds-lp3944.
420 module will be called leds-lp3952.
[all …]
|
| /linux-6.15/tools/testing/selftests/tc-testing/plugin-lib/ |
| D | README-PLUGINS | 1 tdc.py will look for plugins in a directory plugins off the cwd.
14 tdc.py will find them and use them.
22 This plugin will write files to the cwd, called vgnd-xxx.log. These will contain
23 the valgrind output for test xxx. Any file matching the glob 'vgnd-*.log' will be
|
| /linux-6.15/drivers/usb/core/ |
| D | urb.c | 238 * describing that request to the USB subsystem. Request completion will
248 * the particular kind of transfer, although they will not initialize
252 * will be called exactly once, when the USB core and Host Controller Driver
267 * Not all isochronous transfer scheduling policies will work, but most
281 * usb_iso_packet_descriptor's status field will return -EXDEV. If this
320 * configuration/alt setting request will fail. Therefore, submissions to
388 * will be required to set urb->ep directly and we will eliminate in usb_submit_urb()
594 * Successful cancellation means termination of @urb will be expedited
595 * and the completion handler will be called with a status code
608 * Success is indicated by returning -EINPROGRESS, at which time the URB will
[all …]
|
| /linux-6.15/Documentation/dev-tools/kunit/ |
| D | running_tips.rst | 162 the kernel, run the ``./linux`` binary), this section will focus on testing
169 When setting tests to ``=y``, the tests will run as part of boot and print
210 This will then cause it to print TAP output to stdout.
213 The ``modprobe`` will *not* have a non-zero exit code if any test
217 You can set ``CONFIG_KUNIT=m`` as well, however, some features will not
221 As of 5.13, the only difference is that ``current->kunit_test`` will
247 The results for each suite will be exposed under
257 # After removing the module, the corresponding files will go away
282 test. These attributes will later be printed in test output and can be used to
324 attributes will remain uninitialized and act as though the attribute is set
[all …]
|
| /linux-6.15/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 58 to put the whole larger unit into an idle state which also will affect the
95 tasks assigned to it, the CPU will load the given task's context and run its
98 simultaneously, they will be subject to prioritization and time sharing in order
108 available idle states from being used, the CPU will simply execute more or less
140 latency, in turn, is the maximum time it will take a CPU asking the processor
150 when they will trigger, and it is the maximum time the hardware that the given
155 was idle after it has been woken up (that time will be referred to as the *idle
180 the ``acpi_idle`` driver will be used if ``intel_idle`` is disabled for some
206 Thus, if the tick is allowed to trigger on idle CPUs, it will not make sense
209 will never exceed the tick period length and the energy used for entering and
[all …]
|
| /linux-6.15/drivers/net/usb/ |
| D | Kconfig | 32 module will be called catc.
71 module will be called kaweth.
86 module will be called pegasus.
97 module will be called rtl8150.
113 module will be called r8152.
132 module will be called lan78xx.
158 The link will appear with a name like "usb0", when the link is
166 module will be called usbnet.
292 To compile this driver as a module, choose M here: the module will be
311 module will be called cdc_mbim.
[all …]
|
1...<<11121314151617181920>>...837