| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | timekeeping.rst | 31 timekeeping which may be difficult to find elsewhere, specifically,
279 the APIC CPU-local memory-mapped hardware. Beware that CPU errata may affect
280 the use of the APIC and that workarounds may be required. In addition, some of
283 functionality that may be more computationally expensive to implement.
297 systems designated as legacy free may support only the HPET as a hardware timer
317 timing chips built into the cards which may have registers which are accessible
360 platforms, the TSCs of different CPUs may start at different times depending
364 The BIOS may attempt to resynchronize the TSCs during the poweron process and
365 the operating system or other system software may attempt to do this as well.
367 write the full 64-bits of the TSC, it may be impossible to match the TSC in
[all …]
|
| /openbmc/linux/arch/m68k/ifpsp060/ |
| H A D | fpsp.doc | 206 may exit through _060_real_inex <---|
208 may exit through _060_real_ovfl <---|
210 may exit through _060_fpsp_done <---|
218 may exit through _060_real_inex <---|
220 may exit through _060_real_unfl <---|
222 may exit through _060_fpsp_done <---|
253 |----> may exit through _060_real_trace
255 |----> may exit through _060_real_trap
257 |----> may exit through _060_real_bsun
259 |----> may exit through _060_fpsp_done
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | OLDAP-1.3 | 10 The intent of this document is to state the conditions under which a Package may be copied, such th…
24 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
30 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
40 4. You may distribute the programs of this Package in object code or executable form, provided that…
50 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
52 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
56 …uced by linking your software with this Package may be used and redistributed without restriction …
58 9. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | OLDAP-1.2 | 6 …License" as distributed with the Perl Programming Language. As differences may exist, the complete…
10 The intent of this document is to state the conditions under which a Package may be copied, such th…
24 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
30 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
40 4. You may distribute the programs of this Package in object code or executable form, provided that…
50 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
52 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
56 8. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | Artistic-1.0 | 5 The intent of this document is to state the conditions under which a Package may be copied, such th…
14 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
15 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
17 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
19 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
29 4. You may distribute the programs of this Package in object code or executable form, provided that…
39 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
41 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
45 8. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | Noweb | 5 …may redistribute noweb in whole or in part provided you acknowledge its source and include this CO…
7 You may sell noweb if you wish. For example, you may sell a CD-ROM including noweb.
9 You may sell a derived work, provided that all source code for your derived work is available, at n…
|
| H A D | URT-RLE | 1 * This software is copyrighted as noted below. It may be freely copied,
6 * it is provided solely "as is". Bug reports or fixes may be sent
7 * to the author, who may or may not act on them as he desires.
9 * You may not include this software in a program or other software product
|
| H A D | OLDAP-1.4 | 10 The intent of this document is to state the conditions under which a Package may be copied, such th…
24 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
30 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
40 4. You may distribute the programs of this Package in object code or executable form, provided that…
50 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
52 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
56 …uced by linking your software with this Package may be used and redistributed without restriction …
58 9. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | Qhull | 7 …righted as noted above. Qhull is free software and may be obtained via http from www.qhull.org. It…
15 … that include Qhull, you must provide notice that the original source code may be obtained as note…
17 … provided solely "as is". Bug reports or fixes may be sent to qhull_bug@qhull.org; the authors may…
|
| H A D | OGTSL | 7 a Package may be copied, such that the Copyright Holder maintains
58 itself, though there may be fees involved in handling the
59 item. It also means that recipients of the item may
62 1. You may make and give away verbatim copies of the source form of
67 2. You may apply bug fixes, portability fixes and other
72 3. You may otherwise modify your copy of this Package in any way,
84 4. You may distribute the programs of this Package in object code
94 5. You may charge a reasonable copying fee for any distribution of
95 this Package. You may charge any fee you choose for support of this
96 Package. You may not charge a fee for this Package itself. However,
[all …]
|
| H A D | NBPL-1.0 | 9 The intent of this document is to state the conditions under which a Package may be copied, such th…
23 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
25 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
27 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
29 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
39 4. You may distribute the programs of this Package in object code or executable form, provided that…
49 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
51 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
55 8. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | Artistic-1.0-cl8 | 5 The intent of this document is to state the conditions under which a Package may be copied, such th…
19 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
21 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
23 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
25 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
32 4. You may distribute the programs of this Package in object code or executable form, provided that…
39 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
41 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
47 9. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | OLDAP-1.1 | 10 The intent of this document is to state the conditions under which a Package may be copied, such th…
24 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
26 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
28 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
30 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
40 4. You may distribute the programs of this Package in object code or executable form, provided that…
50 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee y…
52 …of this Package, but belong to whomever generated them, and may be sold commercially, and may be a…
56 8. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | Artistic-1.0-Perl | 5 The intent of this document is to state the conditions under which a Package may be copied, such th…
19 …r the item itself, though there may be fees involved in handling the item. It also means that reci…
21 1. You may make and give away verbatim copies of the source form of the Standard Version of this Pa…
23 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domai…
25 3. You may otherwise modify your copy of this Package in any way, provided that you insert a promin…
32 4. You may distribute the programs of this Package in object code or executable form, provided that…
39 …may charge a reasonable copying fee for any distribution of this Package. You may charge any fee …
41 … of this Package, but belong to whoever generated them, and may be sold commercially, and may be a…
47 9. The name of the Copyright Holder may not be used to endorse or promote products derived from thi…
|
| H A D | ClArtistic | 7 Package may be copied, such that the Copyright Holder maintains some
33 use the item, though there may be fees involved in handling the
34 item. It also means that recipients of the item may redistribute
37 1. You may make and give away verbatim copies of the source form of the
41 2. You may apply bug fixes, portability fixes and other modifications
46 3. You may otherwise modify your copy of this Package in any way, provided
72 4. You may distribute the programs of this Package in object code or
91 5. You may charge a distribution fee for any distribution of this Package.
92 If you offer support for this Package, you may charge any fee you choose
93 for that support. You may not charge a license fee for the right to use
[all …]
|
| H A D | TAPR-OHL-1.0 | 14 framework for Open Hardware projects. It may be used for any kind of
16 contribution to the community; anyone may use the OHL for their Open
32 those who benefit from an OHL design may not bring lawsuits claiming that
43 * You may modify the documentation and make products based upon it.
45 * You may use products for any legal purpose without limitation.
47 * You may distribute unmodified documentation, but you must include the
50 * You may distribute products you make to third parties, if you either
55 * You may distribute modified documentation or products based on it, if
63 and may go on with your distribution.
77 * If you wish to be notified of modifications that others may make,
[all …]
|
| /openbmc/linux/security/smack/ |
| H A D | smack_access.c | 89 int may = srp->smk_access; in smk_access_entry() local
93 if ((may & MAY_WRITE) == MAY_WRITE) in smk_access_entry()
94 may |= MAY_LOCK; in smk_access_entry()
95 return may; in smk_access_entry()
118 int may = MAY_NOT; in smk_access() local
168 may = smk_access_entry(subject->smk_known, object->smk_known, in smk_access()
172 if (may <= 0 || (request & may) != request) { in smk_access()
182 if (may & MAY_BRINGUP) in smk_access()
222 int may; in smk_tskacc() local
234 may = smk_access_entry(sbj_known->smk_known, in smk_tskacc()
[all …]
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | user.rst | 42 user namespace may create.
48 user namespace may create.
54 user namespace may create.
60 current user namespace may create.
66 user namespace may create.
72 user namespace may create.
78 user namespace may create.
84 user namespace may create.
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-pci-devices-aer_stats | 6 Note that this may mean that if an endpoint is causing problems, the AER
7 counters may increment at its link partner (e.g. root port) because the
8 errors may be "seen" / reported by the link partner and not the
9 problematic endpoint itself (which may report all counters as 0 as it never
17 PCI device using ERR_COR. Note that since multiple errors may
19 TOTAL_ERR_COR at the end of the file may not match the actual
38 PCI device using ERR_FATAL. Note that since multiple errors may
40 TOTAL_ERR_FATAL at the end of the file may not match the actual
69 may be reported using a single ERR_FATAL message, thus
70 TOTAL_ERR_NONFATAL at the end of the file may not match the
|
| /openbmc/linux/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 15 functions may have live state and therefore may not be safe to patch. One way
18 Existing stacktrace code may not always give an accurate picture of all
35 * The trace includes all functions that the task may be returned to, and the
56 architectures may need to verify that code has been compiled in a manner
57 expected by the unwinder. For example, an unwinder may expect that
63 In some cases, an unwinder may require metadata to correctly unwind.
78 Unwinding may terminate early for a number of reasons, including:
102 manipulating a frame pointer), but there can be code which may not follow these
103 conventions and may require special handling in the unwinder, e.g.
124 There are several ways an architecture may identify kernel code which is deemed
[all …]
|
| /openbmc/linux/Documentation/security/ |
| H A D | credentials.rst | 17 Objects are things in the system that may be acted upon directly by
43 indicates the 'objective context' of that object. This may or may not be
58 Objects other than tasks may under some circumstances also be subjects.
59 For instance an open file may send SIGIO to a task using the UID and EUID
77 Linux has a number of actions available that a subject may perform upon an
98 file may supply more than one ACL.
102 'group' and 'other'), each of which may be granted certain privileges
112 The system as a whole may have one or more sets of rules that get
166 The inheritable capabilities are the ones that may get passed across
169 The bounding set limits the capabilities that may be inherited across
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | msi.txt | 7 MSIs were originally specified by PCI (and are used with PCIe), but may also be
16 Devices may be configured by software to write to arbitrary doorbells which
17 they can address. An MSI controller may feature a number of doorbells.
21 Devices may be configured to write an arbitrary payload chosen by software.
22 MSI controllers may have restrictions on permitted payloads.
35 address by some master. An MSI controller may feature a number of doorbells.
58 generate, the doorbell and payload may be configured, though sideband
59 information may not be configurable.
67 This property is unordered, and MSIs may be allocated from any combination of
|
| /openbmc/linux/Documentation/staging/ |
| H A D | speculation.rst | 12 work which may be discarded at a later stage.
17 absence of data in caches. Such state may form side-channels which can be
32 Which, on arm64, may be compiled to an assembly sequence such as::
44 value will subsequently be discarded, but the speculated load may affect
47 More complex sequences involving multiple dependent memory accesses may
61 Under speculation, the first call to load_array() may return the value
63 microarchitectural state dependent on this value. This may provide an
|
| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | DSD-properties-rules.rst | 12 namespace. In principle, the format of the data may be arbitrary, but it has to
28 It also may be regarded as the definition of a key and the associated data type
45 Property sets may be hierarchical. That is, a property set may contain
46 multiple property subsets that each may contain property subsets of its
66 principle, the property set may still not be regarded as a valid one.
68 For example, that applies to device properties which may cause kernel code
71 particular, that may happen if the kernel code uses device properties to
77 In all cases in which kernel code may do something that will confuse AML as a
90 avoided. For this reason, it may not be possible to make _DSD return a property
92 sake of code re-use, it may make sense to provide as much of the configuration
|
| /openbmc/linux/drivers/atm/ |
| H A D | Kconfig | 61 Note that extended debugging may create certain race conditions
73 chipsets. However, in some cases, large bursts may overrun buffers
80 may increase the cost of setting up a transfer such that the
92 Burst sixteen words at once in the send direction. This may work
106 Burst four words at once in the send direction. You may want to try
108 may or may not improve throughput.
114 Burst two words at once in the send direction. You may want to try
116 are also set may or may not improve throughput.
122 Burst sixteen words at once in the receive direction. This may work
129 Burst eight words at once in the receive direction. This may work
[all …]
|