| /openbmc/linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 9 dependency" extends from that load extending to the later access.
20 address dependency extends from that rcu_dereference() to that
27 Acquire: With respect to a lock, acquiring that lock, for example,
29 a special operation that includes a load and which orders that
30 load before later memory references running on that same CPU.
36 to that same variable, (in other words, the acquire load "reads
37 from" the release store), then all operations preceding that
38 store "happen before" any operations following that load acquire.
56 a "control dependency" extends from that load to that store.
71 that is required. In other cases, the notion of pairing must be
[all …]
|
| /openbmc/bmcweb/ |
| H A D | REDFISH_CHECKLIST.md | 7 that have not been completed.
10 that have been added or are used in the commit.
13 that this should include behavior changes that may not affect your system.
15 3. Verify that any additional properties exist in the CSDL schema in
20 Verify that the @odata.type on the schema on which you've added functionality
21 has a version that includes the parameters you've added
23 5. Verify that testing was performed per TESTING.md and it is documented in my
27 not the present commit, note that explicitly with "Tested on prior commit".
29 6. Ensure that you have written unit tests for any behavior that does not have
32 7. Read COMMON_ERRORS.md, and verify that to the best of your knowledge no
[all …]
|
| /openbmc/linux/Documentation/admin-guide/sysctl/ |
| H A D | user.rst | 15 limits on the number of namespaces and other objects that have
18 The primary purpose of these limits is to stop programs that
21 intention that the defaults of these limits are set high enough that
26 verified to be below the per user limit in that user namespace.
33 This recursive counting of created objects ensures that creating a
41 The maximum number of cgroup namespaces that any user in the current
47 The maximum number of ipc namespaces that any user in the current
53 The maximum number of mount namespaces that any user in the current
59 The maximum number of network namespaces that any user in the
65 The maximum number of pid namespaces that any user in the current
[all …]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | main.rst | 5 QEMU has code to load/save the state of the guest that it is running.
7 that, saves the state for each device that the guest is running.
12 two times. I.e. it can only restore the state in one guest that has
13 the same devices that the one it was saved (this last requirement can
14 be relaxed a bit, but for now we can consider that configuration has
17 Once that we are able to save/restore a guest, a new functionality is
18 requested: migration. This means that QEMU is able to start in one
27 the guest to be stopped. Typically the time that the guest is
29 (notice that this depends on a lot of things).
36 The migration stream is normally just a byte stream that can be passed
[all …]
|
| H A D | compatibility.rst | 12 There are two things that are different, but they have very similar
34 device feature exposure. But that is not relevant for this section.
36 I am going to list the number of combinations that we can have. Let's
55 the latest machine type for that version (pc-5.2) but one of an older
61 were configured on 5.1, but this should be easy in the sense that
71 different. Notice also that the machine type needs to be pc-5.1,
79 migration to qemu-5.1. Notice that we can't make updates to
90 compatibility problems. But the reason that we create qemu-5.2 is to
93 If we get a device that has a new feature, or change a default value,
97 So we need a way to tell qemu-5.2 that when we are using machine type
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | dma-attributes.rst | 5 This document describes the semantics of the DMA attributes that are
11 DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
12 may be weakly ordered, that is that reads and writes may pass each other.
15 those that do not will simply ignore the attribute and exhibit default
21 DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
25 those that do not will simply ignore the attribute and exhibit default
37 that you won't dereference the pointer returned by dma_alloc_attr(). You
38 can treat it as a cookie that must be passed to dma_mmap_attrs() and
39 dma_free_attrs(). Make sure that both of these also get this attribute
43 DMA_ATTR_NO_KERNEL_MAPPING, those that do not will simply ignore the
[all …]
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 12 that "inode pointer" order in the following.
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
29 Take the locks that need to be taken, in inode pointer order if need
30 to take both (that can happen only when both source and target are
33 only with RENAME_EXCHANGE, and that won't be removing the target).
39 * check that source is not a directory
62 The rules above obviously guarantee that all directories that are going to be
105 blocked on source and it means that it doesn't hold any locks.
108 has a child that is also contended. Indeed, suppose that it is held by
110 is blocked on belongs to child of that object due to (1).
[all …]
|
| H A D | path-lookup.rst | 22 exploration is needed to discover, is that it is complex. There are
23 many rules, special cases, and implementation alternatives that all
26 tool that we will make extensive use of is "divide and conquer". For
41 of elements: "slashes" that are sequences of one or more "``/``"
42 characters, and "components" that are sequences of one or more
43 non-"``/``" characters. These form two kinds of paths. Those that
52 component, but that isn't always accurate: a pathname can lack both
62 it must identify a directory that already exists, otherwise an error
68 pathname that is just slashes have a final component. If it does
75 tempting to consider that to have an empty final component. In many
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | management-style.rst | 14 to do with reality. It started as a lark, but that doesn't mean that it
27 making it painfully obvious to the questioner that we don't have a clue
37 Everybody thinks managers make decisions, and that decision-making is
47 competent to make that decision for them.
51 Namely that you are in the wrong job, and that **they** should be managing
60 It helps to realize that the key difference between a big decision and a
62 can be made small by just always making sure that if you were wrong (and
67 And people will even see that as true leadership (*cough* bullshit
71 things that can't be undone. Don't get ushered into a corner from which
75 It turns out that since nobody would be stupid enough to ever really let
[all …]
|
| H A D | 6.Followthrough.rst | 8 patches. One of the biggest mistakes that even experienced kernel
9 developers can make is to conclude that their work is now done. In truth,
13 It is a rare patch which is so good at its first posting that there is no
16 code. You, as the author of that code, will be expected to work with the
17 kernel community to ensure that your code is up to the kernel's quality
32 value and why you went to the trouble of writing it. But that value
36 to substantial rewrites - come from the understanding that Linux will
49 be working on the kernel years from now, but they understand that their
57 the same. Sometimes this means that the clever hack in your driver
61 What all of this comes down to is that, when reviewers send you comments,
[all …]
|
| /openbmc/linux/Documentation/networking/ |
| H A D | nexthop-group-resilient.rst | 7 Resilient groups are a type of next-hop group that is aimed at minimizing
34 that they resolve to.
37 this hash space reassignment causes an issue that packets from a single
38 flow suddenly end up arriving at a server that does not expect them. This
42 the same server, the issue is that different latencies and reordering along
49 to choose a hash table bucket, then reads the next hop that this bucket
56 the buckets that held it are simply reassigned to other next hops::
70 choose a subset of buckets that are currently not used for forwarding
82 this number a "wants count" of a next hop. In case of an event that might
86 Next hops that have fewer buckets than their wants count, are called
[all …]
|
| /openbmc/linux/Documentation/networking/devlink/ |
| H A D | devlink-trap.rst | 21 kernel so that it will route it as well and generate an ICMP Time Exceeded
39 as it allows users to obtain further visibility into packet drops that would
123 Generic packet traps are used to describe traps that trap well-defined packets
124 or packets that are trapped due to well-defined conditions (e.g., TTL error).
136 - Traps incoming packets that the device decided to drop because of a
140 - Traps incoming packets that the device decided to drop in case of VLAN
145 - Traps incoming packets that the device decided to drop in case they are
146 tagged with a VLAN that is not configured on the ingress bridge port
149 - Traps incoming packets that the device decided to drop in case the STP
153 - Traps packets that the device decided to drop in case they need to be
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A D | freezing-of-tasks.rst | 17 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN
18 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have
28 sets this variable. After this, it executes try_to_freeze_tasks() that sends a
30 All freezable tasks must react to that by calling try_to_freeze(), which
33 it loop until PF_FROZEN is cleared for it. Then, we say that the task is
40 try_to_freeze() function (defined in include/linux/freezer.h), that checks
47 that combine interruptible sleep with checking if the task is to be frozen and
69 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that
101 IV. Why do we do that?
111 filesystem-related information that must be consistent with the state of the
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | NGPL | 9 …right to share NetHack. To make sure that you get the rights we want you to have, we need to make …
11 …that you have the right to give away copies of NetHack, that you receive source code or else can g…
13 …that everyone has such rights, we have to forbid you to deprive anyone else of these rights. For e…
15 …that everyone finds out that there is no warranty for NetHack. If NetHack is modified by someone e…
21 …ce code as you receive it, in any medium, provided that you keep intact the notices on all files t…
22 …ragraph 1 above (including distributing this License Agreement), provided that you also do the fol…
23 a) cause the modified files to carry prominent notices stating that you changed the files and the d…
25 …that you distribute or publish, that in whole or in part contains or is a derivative of NetHack or…
29 …e or executable form under the terms of Paragraphs 1 and 2 above provided that you also do one of …
37 … permitted to modify NetHack, or otherwise use parts of NetHack, provided that you comply with the…
|
| H A D | Community-Spec-1.0 | 18 materials. Contributor also acknowledges that the Working Group may
39 Contributor’s Contributions and 2) to the Draft Specification that
40 is within Scope as of the date of that Contribution, in both cases for
48 that are within Scope for Licensee’s Implementation of the Approved
59 extend only to Licensees that have indicated their agreement to this
77 claim in a court asserting that a Necessary Claim is infringed by an
79 are immediately terminated unless 1) that claim is directly in response
80 to a claim against Licensee regarding an Implementation, or 2) that claim
85 that any of Contributor’s copyrights or issued patent claims cover
86 an Implementation of the Specification or are enforceable or (ii) that
[all …]
|
| /openbmc/linux/Documentation/driver-api/driver-model/ |
| H A D | binding.rst | 6 driver that can control it. Bus drivers have typically handled this
15 The bus type structure contains a list of all devices that are on that bus
18 list of all drivers of that bus type. When driver_register is called
27 to find one that supports it. In order to determine that, the device
28 ID of the device must match one of the device IDs that the driver
39 chance to verify that it really does support the hardware, and that
47 class, and that is set in the driver's devclass field.
63 A symlink is created in the bus's 'devices' directory that points to
66 A symlink is created in the driver's 'devices' directory that points
70 symlink is created in that directory that points to the device's
[all …]
|
| /openbmc/linux/drivers/pinctrl/intel/ |
| H A D | Kconfig | 21 Cherryview/Braswell pinctrl driver provides an interface that
29 provides an interface that allows configuring of PCH pins and
44 This pinctrl driver provides an interface that allows configuring
51 Broxton pinctrl driver provides an interface that allows
58 This pinctrl driver provides an interface that allows configuring
65 This pinctrl driver provides an interface that allows configuring
72 This pinctrl driver provides an interface that allows configuring
79 This pinctrl driver provides an interface that allows configuring
86 This pinctrl driver provides an interface that allows configuring
93 This pinctrl driver provides an interface that allows configuring
[all …]
|
| /openbmc/docs/ |
| H A D | meta-layer-guidelines.md | 5 "Why" section, to ensure that the intent is being met, and that if exceptions to
10 ## Meta layers should not patch projects that exist within the openBMC tree
15 the possibility that patches exist that repo maintainers aren't aware of makes
16 it much more likely that a single machine breaks, or we have behavior
19 Also, in general, the maintainer is there to ensure that the greater community,
33 PACKAGECONFIG entry that can be set to enable it.
39 Yocto itself is an open source project that accepts contributions. The more
40 changes that OpenBMC stacks against Yocto recipes, the more unmaintainable it
59 There are some OpenBMC projects that are utilized outside of OpenBMC. As such,
60 there are configuration items that are not intended to be used in OpenBMC, or
[all …]
|
| /openbmc/linux/Documentation/mm/ |
| H A D | active_mm.rst | 18 Cc'd to linux-kernel, because I don't write explanations all that often,
31 difference is that an anonymous address space doesn't care about the
36 The obvious use for a "anonymous address space" is any thread that
38 this category, but even "real" threads can temporarily say that for
40 and that the scheduler might as well try to avoid wasting time on
42 sync does that.
45 tsk->mm will be NULL, for the logical reason that an anonymous process
49 "stole" for such an anonymous user. For that, we have "tsk->active_mm",
52 The rule is that for a process with a real address space (ie tsk->mm is
61 To support all that, the "struct mm_struct" now has two counters: a
[all …]
|
| H A D | memory-model.rst | 10 however, that this range contains small holes that are not accessible
18 whether it is possible to manually override that default.
28 helpers that allow the conversion from PFN to `struct page` and vice
38 In the FLATMEM memory model, there is a global `mem_map` array that
45 usable until the call to :c:func:`memblock_free_all` that hands all the
48 An architecture may free parts of the `mem_map` array that do not cover the
64 is the only memory model that supports several advanced features such
71 that contains `section_mem_map` that is, logically, a pointer to an
73 that aids the sections management. The section size and maximal number
75 `MAX_PHYSMEM_BITS` constants defined by each architecture that
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | qe_firmware.rst | 31 the particular license, please see the license text that is distributed with
45 integers that compose the actual QE microcode.
47 The term 'firmware' refers to a binary blob that contains the microcode as
48 well as other data that
55 Firmware files are binary files that contain only a firmware.
70 needs split I-RAM. Split I-RAM is only meaningful for SOCs that have
80 5) If necessary, device drivers that need the virtual traps and extended mode
91 This structure contains 6 words that the application should copy to some
119 This is a double word bit array (64 bits) that defines special functionality
127 | 0 | General | Indicates that prior to each host command |
[all …]
|
| /openbmc/linux/Documentation/filesystems/nfs/ |
| H A D | exporting.rst | 12 applications that access a filesystem via a remote filesystem protocol
35 tree. This means that if any filesystem object is in the dcache, then
36 all of the ancestors of that filesystem object are also in the dcache.
44 the dcache that are not needed for normal filesystem access.
46 1. The dcache must sometimes contain objects that are not part of the
47 proper prefix. i.e that are not connected to the root.
50 that dentry into place (based on the parent and name in the
52 it is a dcache invariant that directories only have one dentry.
57 any dentry that might not be part of the proper prefix.
62 kept in the dcache. If a dentry that is not already in the dcache
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/cec/ |
| H A D | cec-ioc-dqevent.rst | 40 the new one. This means that intermediate results can be thrown away but
41 that the latest event is always available. This also means that is it
42 possible to read two successive events that have the same value (e.g.
44 the same state). In that case the intermediate state changes were lost but
45 it is guaranteed that the state did change in between the two events.
65 has the unregistered logical address. In that case all other bits are 0.
69 This field is only valid if ``CEC_CAP_CONNECTOR_INFO`` is set. If that
70 capability is set and ``have_conn_info`` is zero, then that indicates
71 that the HDMI connector device is not instantiated, either because
91 size of the message queue guarantees that all messages received in
[all …]
|
| /openbmc/linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 13 faults. There may be fancier recovery schemes that are appropriate in
18 result for an operation ... it doesn't indicate that anything is wrong
19 at all, just that the outcome wasn't on the "golden path".
23 the right fault code, so that it can (in turn) behave correctly.
33 Note that the descriptions here are not exhaustive. There are other
34 codes that may be returned, and other cases where these codes should
48 atomic context, when some task is already using that I2C bus
57 host. Note that even if PECs are in use, you should not rely
64 or that the reset was attempted but failed.
85 Returned by any component that can't allocate memory when
[all …]
|
| /openbmc/u-boot/board/sunxi/ |
| H A D | README.nand | 10 In order to mitigate that, various strategies have been found to be
14 This is obviously something that we will take into account when
17 which means that we also have to split that binary accross several
20 In order to accomodate that, we create a tool that will generate an
21 SPL image that is ready to be programmed directly embedding the ECCs,
25 that will have been generated by that tool.
27 In order to flash your U-Boot image onto a board, assuming that the
28 board is in FEL mode, you'll need the sunxi-tools that you can find at
|