Searched full:important (Results 1 – 25 of 1466) sorted by relevance
12345678910>>...59
| /Linux-v6.1/Documentation/virt/ |
| D | paravirt_ops.rst | 25 known that the overhead of indirect call isn't very important.
30 very important.
|
| /Linux-v6.1/arch/mips/kernel/ |
| D | pm.c | 37 * Restores important CPU context.
65 * ensure that important CPU context is preserved across a CPU power down.
|
| /Linux-v6.1/Documentation/process/ |
| D | stable-api-nonsense.rst | 68 isn't that important, but the different data structure padding is
69 very important.
138 important changes that needed to be made, and they were made, with
146 Security issues are also very important for Linux. When a
|
| D | handling-regressions.rst | 13 The important bits (aka "The TL;DR")
57 The important basics in more detail
93 you want to see tracked; that's important, as regzbot will later look out
107 What's important when fixing regressions
125 All this is expected from you and important when it comes to regression, as
172 important, to ensure all the improvements and fixes are ideally tested
313 important unexpectedly comes up -- for example a bigger problem in the Linux
331 Regzbot is watching the most important Linux mailing lists as well as the git
647 Binary compatibility is more important.
|
| /Linux-v6.1/Documentation/RCU/ |
| D | arrayRCU.rst | 51 Why is it so important that updates be rare when using seqlock?
160 Why is it so important that updates be rare when using seqlock?
162 The reason that it is important that updates be rare when
|
| D | NMI-RCU.rst | 101 Important note: for this to work, the architecture in question must
121 More important, the rcu_dereference_sched() makes it
|
| /Linux-v6.1/Documentation/trace/ |
| D | events-kmem.rst | 59 mm_page_alloc_zone_locked event is triggered. This event is important as high
110 successful or not. For some types of hardware, this is important although
113 is important.
|
| /Linux-v6.1/Documentation/doc-guide/ |
| D | contributing.rst | 6 Documentation is an important part of any software-development project.
27 important items, but is far from exhaustive; if you see a different way to
49 Another important point is that documentation warnings are often created by
137 times, but it's highly important. If we can actually eliminate warnings
248 Moving documents into the appropriate books is an important task and needs
|
| /Linux-v6.1/Documentation/virt/kvm/s390/ |
| D | s390-pv-dump.rst | 41 The vcpu state contains all the important registers, general, floating
45 in the dump data. For the same reason it is very important to not only
|
| /Linux-v6.1/Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,smd-edge.yaml | 15 important.
18 that "edge". The names of the devices are not important. The properties of
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | gl518sm.rst | 29 .. important::
61 zero'; this is important for negative voltage measurements. The VDD input
|
| /Linux-v6.1/kernel/trace/ |
| D | trace_preemptirq.c | 24 * used in the low level entry code where the ordering vs. RCU is important
57 * used in the low level entry code where the ordering vs. RCU is important
|
| /Linux-v6.1/Documentation/power/ |
| D | energy-model.rst | 35 Important thing to keep in mind is that when the power values are expressed in
95 (leakage) is important.
109 The last argument 'microwatts' is important to set with correct value. Kernel
156 physics of a real device, e.g. when static power (leakage) is important.
|
| D | swsusp-dmcrypt.rst | 29 The most important thing is that you set up dm-crypt in such
129 Note that it is important to set the device in /sys/power/resume,
|
| /Linux-v6.1/Documentation/ABI/ |
| D | README | 52 it changes. This is very important for interfaces in
56 important to get feedback for these interfaces to make
|
| /Linux-v6.1/arch/mips/include/asm/ |
| D | pm.h | 68 /* Save important CPU state for early restoration to global data */
86 /* Restore important CPU state early from global data */
|
| /Linux-v6.1/drivers/usb/c67x00/ |
| D | c67x00-hcd.h | 23 * are very important, bandwidth can be sacrificed to guarantee that the
25 * If bulk transfers are important, the MAX_FRAME_BW can be increased,
|
| /Linux-v6.1/drivers/ufs/ |
| D | Makefile | 3 # The link order is important here. ufshcd-core must initialize
|
| /Linux-v6.1/arch/x86/kvm/svm/ |
| D | vmenter.S | 49 * IMPORTANT: To avoid RSB underflow attacks and any other nastiness,
210 /* IMPORTANT: Stuff the RSB immediately after VM-Exit, before RET! */
347 /* IMPORTANT: Stuff the RSB immediately after VM-Exit, before RET! */
|
| /Linux-v6.1/arch/parisc/lib/ |
| D | io.c | 163 * IDE driver to read disk sectors. Performance is important, but
235 * SRC. Now works with any alignment in SRC. Performance is important,
333 * driver to write disk sectors. Performance is important, but the
406 * Performance is important, but the interfaces seems to be slow:
|
| /Linux-v6.1/Documentation/timers/ |
| D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for
78 scheduling-clock interrupts to idle CPUs, which is critically important
114 and such CPUs are said to be "adaptive-ticks CPUs". This is important
117 duration of a scheduling-clock interrupt. It is also important for
|
| /Linux-v6.1/tools/memory-model/Documentation/ |
| D | access-marking.txt | 87 that fail to exclude the updates. In this case, it is important to use
203 Note that it is important to use plain C-language accesses in these cases,
211 It is important to comment marked accesses so that people reading your
213 However, it is even more important to comment plain C-language accesses
520 When designing stress tests it is important to ensure that race conditions
|
| /Linux-v6.1/arch/microblaze/lib/ |
| D | uaccess_old.S | 100 .align 4 /* Alignment is important to keep icache happy */
161 .align 4 /* Alignment is important to keep icache happy */
|
| /Linux-v6.1/Documentation/core-api/ |
| D | printk-index.rst | 7 There are many ways how to monitor the state of the system. One important
9 including more or less important warnings and error messages.
|
| /Linux-v6.1/tools/testing/memblock/ |
| D | TODO | 6 *Important:* These tests require valid memory ranges, use dummy physical
|
12345678910>>...59
