| /OK3568_Linux_fs/kernel/Documentation/livepatch/ |
| H A 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
|
| H A 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
|
| H A D | livepatch.rst | 74 the same way to the rest of the system. In this case, the functions might
77 But there are more complex fixes. For example, a patch might change
79 might exchange meaning of some temporary structures and update
249 might want to access functions or data from the original source file
283 together. Note that patched modules might be loaded later than
284 the patch itself and the relevant functions might be patched
320 Second, the error code might be used to refuse loading the module when
349 Note that functions might be patched multiple times. The ftrace handler
357 functions might be patched two times only during the transition period.
363 All enabled patches might get replaced by a cumulative patch that
[all …]
|
| /OK3568_Linux_fs/kernel/net/netfilter/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/RCU/ |
| H A D | rcu_dereference.rst | 106 can now be speculated, such that it might happen before the
182 might provide, especially if you are making use of feedback-based
243 You might be surprised that the outcome (r1 == 143 && r2 == 44) is possible,
244 but you should not be. After all, the updater might have been invoked
310 first pointer might be. This lack of knowledge prevents the compiler
311 from carrying out optimizations that otherwise might destroy the ordering
315 But without rcu_dereference(), the compiler knows more than you might
377 2. If the access might be within an RCU read-side critical section
385 3. If the access might be within an RCU read-side critical section
404 is appropriate. In addition, rcu_dereference_raw() might be
[all …]
|
| H A 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
|
| H A D | NMI-RCU.rst | 60 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
108 …Why might the rcu_dereference_sched() be necessary on Alpha, given that the code referenced by the…
110 The caller to set_nmi_callback() might well have
114 just after the new handler was set might see the pointer
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/stable/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/soundwire/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/drivers/media/test-drivers/vidtv/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/Documentation/process/ |
| H A 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
|
| /OK3568_Linux_fs/yocto/poky/documentation/ref-manual/ |
| H A D | qa-checks.rst | 66 system used by the software being built, there might be a configure
80 might be a configure option to disable rpath usage completely within
115 go into the ``-dev`` package. This situation might occur if you add
150 not appear in anything but the ``-dbg`` package. This situation might
177 bootloaders, might need to bypass this check. If the file you receive
195 bootloaders, might need to bypass this check. If the file you receive
213 bootloaders, might need to bypass this check. If the file you receive
328 The dependency might have been automatically added because the
330 (e.g. a non-symlink ``.so`` file) or it might have been added
351 The dependency might have been automatically added (because the
[all …]
|
| /OK3568_Linux_fs/buildroot/dl/stressapptest/git/ |
| H A D | missing | 145 you modified \`acinclude.m4' or \`${configure_ac}'. You might want
154 you modified \`${configure_ac}'. You might want to install the
163 you modified \`acconfig.h' or \`${configure_ac}'. You might want
183 You might want to install the \`Automake' and \`Perl' packages.
193 You might have modified some files without having the
289 call might also be the consequence of using a buggy \`make' (AIX,
290 DU, IRIX). You might want to install the \`Texinfo' package or
351 You might have modified some files without having the
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/binutils.html/ |
| H A D | Bug-Reporting.html | 88 problem and assume that some details do not matter. Thus, you might
105 You might as well expedite matters by sending them to begin with.
130 and then we might not encounter the bug.
147 will certainly notice it. But if the bug is incorrect output, we might
148 not notice unless it is glaringly wrong. You might as well not give us
154 the C library on your system. (This has happened!) Your copy might
196 a patch is all we need. We might see problems with your patch and decide
197 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/binutils.html/ |
| H A D | Bug-Reporting.html | 88 problem and assume that some details do not matter. Thus, you might
105 You might as well expedite matters by sending them to begin with.
130 and then we might not encounter the bug.
147 will certainly notice it. But if the bug is incorrect output, we might
148 not notice unless it is glaringly wrong. You might as well not give us
154 the C library on your system. (This has happened!) Your copy might
196 a patch is all we need. We might see problems with your patch and decide
197 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/media/drivers/ |
| H A 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.
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A 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.
|
| /OK3568_Linux_fs/u-boot/include/linux/byteorder/ |
| H A D | generic.h | 28 * = Linus might want to rename all these macros and files to fit his taste,
34 * = cpu_to_beXX and beXX_to_cpu might some day need to be well
37 * But this might be the case for, say, a port of Linux to 20/21 bit
50 * might like the above to be functions, not macros (why?).
146 * Do the prototypes. Somebody might want to take the
|
| /OK3568_Linux_fs/kernel/Documentation/dev-tools/kunit/ |
| H A 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
|
| /OK3568_Linux_fs/external/xserver/dix/ |
| H A D | BuiltInAtoms | 124 paragraph.) For a 3/3/2 allocation red_mult might be 32,
125 green_mult might be 4, and blue_mult might be 1. For a
126 6-colors-each allocation, red_mult might be 36, green_mult might
127 be 6, and blue_mult might be 1.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/as.html/ |
| H A D | Bug-Reporting.html | 90 and assume that some details do not matter. Thus, you might assume that the
106 You might as well expedite matters by sending them to begin with.
130 and then we might not encounter the bug.
144 will certainly notice it. But if the bug is incorrect output, we might not
145 notice unless it is glaringly wrong. You might as well not give us a chance to
151 library on your system. (This has happened!) Your copy might crash and ours
193 a patch is all we need. We might see problems with your patch and decide
194 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/ld.html/ |
| H A D | Bug-Reporting.html | 91 problem and assume that some details do not matter. Thus, you might
108 You might as well expedite matters by sending them to begin with.
134 and then we might not encounter the bug.
155 will certainly notice it. But if the bug is incorrect output, we might
156 not notice unless it is glaringly wrong. You might as well not give us
162 C library on your system. (This has happened!) Your copy might crash
204 a patch is all we need. We might see problems with your patch and decide
205 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/as.html/ |
| H A D | Bug-Reporting.html | 90 and assume that some details do not matter. Thus, you might assume that the
106 You might as well expedite matters by sending them to begin with.
130 and then we might not encounter the bug.
144 will certainly notice it. But if the bug is incorrect output, we might not
145 notice unless it is glaringly wrong. You might as well not give us a chance to
151 library on your system. (This has happened!) Your copy might crash and ours
193 a patch is all we need. We might see problems with your patch and decide
194 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/ld.html/ |
| H A D | Bug-Reporting.html | 91 problem and assume that some details do not matter. Thus, you might
108 You might as well expedite matters by sending them to begin with.
134 and then we might not encounter the bug.
155 will certainly notice it. But if the bug is incorrect output, we might
156 not notice unless it is glaringly wrong. You might as well not give us
162 C library on your system. (This has happened!) Your copy might crash
204 a patch is all we need. We might see problems with your patch and decide
205 to fix the problem another way, or we might not understand it at all.
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A 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.
|