Searched full:might (Results 1 – 25 of 3786) sorted by relevance
12345678910>>...152
| /Linux-v5.15/Documentation/admin-guide/ |
| D | reporting-issues.rst | 9 (for example by the kernel's build system) might contain content taken from
30 In all other cases try your best guess which kernel part might be causing the
64 developers. It might be all that's needed for people already familiar with
98 kernel modules on-the-fly, which solutions like DKMS might be doing locally
102 that made the kernel set this flag might be causing the issue you face.
120 thoroughly for reports that might match your issue. If you find anything,
128 situations; during the merge window that actually might be even the best
158 link to it. Include or upload all other information that might be relevant,
197 the issue might have already been fixed there. If you first noticed the
221 might not get the issue solved in older releases: the fix might be too big
[all …]
|
| /Linux-v5.15/Documentation/livepatch/ |
| D | cumulative-patches.rst | 5 There might be dependencies between livepatches. If multiple patches need
10 This might become a maintenance nightmare. Especially when more patches
36 As a result, the livepatch authors might maintain sources only for one
42 actually in use. Also the livepatch might then be seen as a "normal"
83 As a result, it might be dangerous to replace newer cumulative patches by
84 older ones. The old livepatches might not provide the necessary callbacks.
86 This might be seen as a limitation in some scenarios. But it makes life
101 A good practice might be to remove shadow variables in the post-unpatch
|
| D | system-state.rst | 13 The problems might come with shadow variables and callbacks. They might
31 The state of the system might get modified either by several livepatch callbacks
99 It might be the original system state or the state modification
113 - Allocate *state->data* when necessary. The allocation might fail
125 - Clean up its own mess in case of error. It might be done by a custom
154 state. It might mean doing nothing.
166 It might be called also during the transition reverse. Therefore it
|
| D | livepatch.rst | 61 the same way to the rest of the system. In this case, the functions might
64 But there are more complex fixes. For example, a patch might change
66 might exchange meaning of some temporary structures and update
236 might want to access functions or data from the original source file
270 together. Note that patched modules might be loaded later than
271 the patch itself and the relevant functions might be patched
307 Second, the error code might be used to refuse loading the module when
336 Note that functions might be patched multiple times. The ftrace handler
344 functions might be patched two times only during the transition period.
350 All enabled patches might get replaced by a cumulative patch that
[all …]
|
| /Linux-v5.15/net/netfilter/ |
| D | nf_conntrack_proto_dccp.c | 101 * We are the man in the middle. All the packets go through us but might
137 * sPO -> sIG Ignore, conntrack might be out of sync
138 * sOP -> sIG Ignore, conntrack might be out of sync
139 * sCR -> sIG Ignore, conntrack might be out of sync
140 * sCG -> sIG Ignore, conntrack might be out of sync
149 * sRQ -> sIG Ignore, might be response to ignored Request
150 * sRS -> sIG Ignore, might be response to ignored Request
151 * sPO -> sIG Ignore, might be response to ignored Request
152 * sOP -> sIG Ignore, might be response to ignored Request
153 * sCR -> sIG Ignore, might be response to ignored Request
[all …]
|
| /Linux-v5.15/Documentation/RCU/ |
| D | rcu_dereference.rst | 112 can now be speculated, such that it might happen before the
188 might provide, especially if you are making use of feedback-based
249 You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
250 but you should not be. After all, the updater might have been invoked
316 first pointer might be. This lack of knowledge prevents the compiler
317 from carrying out optimizations that otherwise might destroy the ordering
321 But without rcu_dereference(), the compiler knows more than you might
383 2. If the access might be within an RCU read-side critical section
391 3. If the access might be within an RCU read-side critical section
410 is appropriate. In addition, rcu_dereference_raw() might be
[all …]
|
| D | rcubarrier.rst | 19 such readers might hold a reference to them. RCU updates can therefore be
23 given that readers might well leave absolutely no trace of their
26 element p from a linked list might do the following, while holding an
38 context might then be as follows::
44 IRQ context. The function p_callback() might be defined as follows::
68 One might be tempted to try several back-to-back synchronize_rcu()
70 heavy RCU-callback load, then some of the callbacks might be deferred
187 Is there any other situation where rcu_barrier() might
192 Your module might have additional complications. For example, if your
302 Is there any other situation where rcu_barrier() might
|
| D | NMI-RCU.rst | 59 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
107 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
109 The caller to set_nmi_callback() might well have
113 just after the new handler was set might see the pointer
|
| /Linux-v5.15/Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 7 Might return "<denied>" in case of special security settings
16 Might return "<denied>" in case of special security settings
25 Might return "<denied>" in case of special security settings
56 Might return "<denied>" in case of special security settings
73 Might return "0" in case of special security settings
105 Might return "<denied>" in case of special security settings
|
| /Linux-v5.15/Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 21 and after a number of such errors are detected the bus might be reset. Note
38 backtracking and restarting the entire programming sequence might be a
39 solution. Alternatively some implementations might directly issue a bus
58 hard-reset might be the best solution.
62 that the Slave might behave in implementation-defined ways. The bus
|
| /Linux-v5.15/Documentation/power/ |
| D | energy-model.rst | 17 Alternatively, userspace might be best positioned. And so on. In order to avoid
23 The power values might be expressed in milli-Watts or in an 'abstract scale'.
24 Multiple subsystems might use the EM and it is up to the system integrator to
28 powercap power values expressed in an 'abstract scale' might cause issues.
30 thus the real milli-Watts might be needed. An example of these requirements can
33 Kernel subsystems might implement automatic detection to check whether EM
100 subsystems which use EM might rely on this flag to check if all EM devices use
101 the same scale. If there are different scales, these subsystems might decide
|
| /Linux-v5.15/drivers/media/test-drivers/vidtv/ |
| D | vidtv_pes.h | 87 * @n_pes_h_s_bytes: Padding bytes. Might be used by an encoder if needed, gets
89 * @access_unit_len: The size of _one_ access unit (with any headers it might need)
104 /* might be used by an encoder if needed, gets discarded by decoder */
117 * @n_stuffing_bytes: Padding bytes. Might be used by an encoder if needed, gets
136 * @access_unit_len: The size of _one_ access unit (with any headers it might need)
148 * @n_pes_h_s_bytes: Padding bytes. Might be used by an encoder if needed, gets
|
| /Linux-v5.15/Documentation/process/ |
| D | volatile-considered-harmful.rst | 36 change unexpectedly while the_lock is held. Any other code which might
40 compiler might think it knows what will be in shared_data, but the
61 Another situation where one might be tempted to use volatile is
76 - The above-mentioned accessor functions might use volatile on
92 - Pointers to data structures in coherent memory which might be modified
|
| /Linux-v5.15/Documentation/userspace-api/media/rc/ |
| D | lirc-set-wideband-receiver.rst | 39 This might be useful of receivers that have otherwise narrow band receiver
40 that prevents them to be used with some remotes. Wide band receiver might
46 Wide band receiver might be implictly enabled if you enable
|
| /Linux-v5.15/Documentation/networking/ |
| D | ipv6.rst | 23 its functionality. This might be used when another module
45 on all interfaces. This might be used when one does not wish
65 This might be used when no IPv6 addresses are desired.
|
| /Linux-v5.15/Documentation/driver-api/media/drivers/ |
| D | bttv-devel.rst | 27 If your card isn't listed there, you might check the source code for
34 example. If your board has one, you might have to load a helper
37 you might want to check the video4linux mailing list archive first...
87 card installed, you might to check out if you can read these registers
91 You might also dig around in the ``*.ini`` files of the Windows applications.
|
| /Linux-v5.15/Documentation/core-api/ |
| D | dma-attributes.rst | 50 buffer from CPU domain to device domain. Some advanced use cases might
61 might be a time consuming operation, especially if the buffers are
85 pages). You might want to specify this if:
88 You might know that the accesses are likely to be sequential or
95 might be the case.
|
| /Linux-v5.15/Documentation/devicetree/bindings/sound/ |
| D | cs42l42.txt | 31 debounce, the tip sense pin might be noisy on a plug event.
43 With no debounce, the tip sense pin might be noisy on an unplug event.
76 hardware setups, a designer might want to tweak this. This is an array of
89 with CTIA headset type. For different hardware setups, a designer might
|
| /Linux-v5.15/Documentation/dev-tools/kunit/ |
| D | faq.rst | 38 it might require more work than using KUnit on UML.
53 usually just two or three. For example, someone might write an integration
60 code under test. For example, someone might write an end-to-end test for the
72 parameter. This might show details or error messages hidden by the kunit_tool
88 It also preserves any config changes you might make, so you can
|
| /Linux-v5.15/fs/ocfs2/cluster/ |
| D | quorum.c | 192 * the connection. the hold will be droped in conn_up or hb_down. it might be
193 * perpetuated by con_err until hb_down. if we already have a conn, we might
217 /* hb going down releases any holds we might have had due to this node from
242 * though we might be doing so after waiting for holds to drain. Here
260 * hb_up or hb_down. it might be perpetuated by con_err until hb_down. if
261 * it's already heartbeating we might be dropping a hold that conn_up got.
|
| /Linux-v5.15/arch/x86/ |
| D | Kconfig.cpu | 413 CPU might render the kernel unbootable.
427 CPU might render the kernel unbootable.
440 CPU might render the kernel unbootable.
454 CPU might render the kernel unbootable.
467 CPU might render the kernel unbootable.
481 CPU might render the kernel unbootable.
495 CPU might render the kernel unbootable.
508 CPU might render the kernel unbootable.
|
| /Linux-v5.15/tools/memory-model/Documentation/ |
| D | ordering.txt | 162 always successful but spin_trylock() might not be.
187 Note that smp_wmb() might fail to provide ordering for unmarked C-language
190 compiler might then reasonably decide to transform "x = 1" and "y = 1"
223 prohibits compiler code-motion optimizations that might move memory
287 against "y". On x86, the version using smp_store_release() might compile
502 might (and sometimes does) split a plain C-language store into multiple
504 CPU while such a store is executing might see a value that is a mashup
515 but to all the compilers that might be used to build it. Such compilers
516 might replace a series of loads with a single load, and might replace
|
| /Linux-v5.15/drivers/media/usb/pvrusb2/ |
| D | pvrusb2.h | 12 might want to increase this - however the driver operation will not
14 won't have an ID assigned and it might not be possible to specify
|
| /Linux-v5.15/Documentation/fb/ |
| D | vesafb.rst | 74 If this does not work, this might be because your BIOS does not support
76 Even if your board does, it might be the BIOS which does not. VESA BIOS
89 another (accelerated) X-Server like XF86_SVGA might or might not work.
107 * VBE 3.0 might work too. I have neither a gfx board with VBE 3.0
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-dma-buffer | 6 buffers. If this alignment requirement is not met samples might
15 that the alignment requirement in samples sets might change
|
12345678910>>...152
