| /openbmc/openbmc/poky/documentation/ref-manual/ |
| H A D | classes.rst | 4 Classes title
19 - ``classes-recipe/`` - classes intended to be inherited by recipes
21 - ``classes-global/`` - classes intended to be inherited globally
22 - ``classes/`` - classes whose usage context is not clearly defined
30 This chapter discusses only the most useful and important classes. Other
31 classes do exist within the ``meta/classes*`` directories in the Source
35 .. _ref-classes-allarch:
40 The :ref:`ref-classes-allarch` class is inherited by recipes that do not produce
52 configured for all architectures using :ref:`ref-classes-allarch`. This is the case
61 By default, all recipes inherit the :ref:`ref-classes-base` and
[all …]
|
| H A D | variables.rst | 60 ":ref:`ref-classes-update-alternatives`"
80 ":ref:`ref-classes-update-alternatives`"
96 ":ref:`ref-classes-update-alternatives`"
126 ":ref:`ref-classes-update-alternatives`" section.
129 When inheriting the :ref:`ref-classes-features_check`
142 See the :ref:`ref-classes-grub-efi` class for more
149 When used with the :ref:`ref-classes-archiver` class,
165 ``meta/classes/archiver.bbclass`` file in the :term:`Source Directory`.
196 When the :ref:`ref-classes-debian` class is inherited,
202 :ref:`ref-classes-debian` class to act on all packages that are
[all …]
|
| /openbmc/linux/net/sched/ |
| H A D | sch_ets.c | 14 * classes at will. Instead one specifies number of classes, how many are
20 * The strict classes, if any, are tried for traffic first: first band 0, if it
55 struct ets_class classes[TCQ_ETS_MAX_BANDS]; member
96 return &q->classes[arg - 1]; in ets_class_from_arg()
102 int band = cl - q->classes; in ets_class_id()
132 q_sum += q->classes[i].quantum; in ets_offload_change()
135 quantum = q->classes[i].quantum; in ets_offload_change()
194 unsigned int band = cl - q->classes; in ets_class_is_strict()
210 /* Classes can be added and removed only through Qdisc_ops.change in ets_class_change()
402 return &q->classes[q->prio2band[band & TC_PRIO_MAX]]; in ets_classify()
[all …]
|
| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | ptest.rst | 28 A recipe is "ptest-enabled" if it inherits the :ref:`ref-classes-ptest`
59 - *Be sure the recipe inherits the* :ref:`ref-classes-ptest` *class:*
66 Classes for common frameworks already exist in :term:`OpenEmbedded-Core
69 - :oe_git:`go-ptest </openembedded-core/tree/meta/classes-recipe/go-ptest.bbclass>`
70 - :ref:`ref-classes-ptest-cargo`
71 - :ref:`ref-classes-ptest-gnome`
72 - :oe_git:`ptest-perl </openembedded-core/tree/meta/classes-recipe/ptest-perl.bbclass>`
73 …- :oe_git:`ptest-python-pytest </openembedded-core/tree/meta/classes-recipe/ptest-python-pytest.b…
75 Inheriting these classes with the ``inherit`` keyword in your recipe will
124 - *Install the test suite:* The :ref:`ref-classes-ptest` class
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-4.0.rst | 122 function has been removed from the :ref:`ref-classes-license` class as
141 classes have been moved to ``meta-python``. Recipes that inherit the ``distutils*``
142 classes should be updated to inherit ``setuptools*`` equivalents instead.
145 The new Python packaging classes that should be used are
146 :ref:`ref-classes-python_flit_core`, :ref:`ref-classes-python_setuptools_build_meta`
147 and :ref:`ref-classes-python_poetry_core`.
149 - The :ref:`ref-classes-setuptools3` class :ref:`ref-tasks-install` task now
153 entry points, then :ref:`ref-classes-setuptools3_legacy` should
175 :ref:`ref-classes-base` class. If you have references in your configuration to
217 :ref:`ref-classes-base` class with a more descriptive
[all …]
|
| H A D | release-notes-5.2.rst | 23 - :ref:`ref-classes-cml1`: in :ref:`ref-tasks-diffconfig`, do not override
25 class :ref:`ref-classes-cml1`.
38 - The :ref:`ref-classes-kernel-yocto` classes now supports in-tree
43 ``.config`` for :ref:`ref-classes-kernel-yocto`-based Kernel recipes.
46 :ref:`ref-classes-kernel-uboot` class. This can be done by setting the
51 - ``python3-pefile``: required for the :ref:`ref-classes-uki` class.
68 - New core classes:
70 - New :ref:`ref-classes-uki` class for building Unified Kernel Images (UKI).
73 - New :ref:`ref-classes-cython` class for python recipes that require Cython
94 - The :ref:`ref-classes-go-mod` class now sets an internal variable
[all …]
|
| H A D | migration-4.1.rst | 74 .. _migration-4.1-classes-split:
76 Classes now split by usage context
79 A split directory structure has now been set up for ``.bbclass`` files - classes
82 ``classes-recipe`` subdirectory and classes that are intended to be inherited
84 or :term:`INHERIT_DISTRO`) should be in ``classes-global``. Classes in the
85 existing ``classes`` subdirectory will continue to work in any context as before.
89 configuration you were using some classes in the incorrect context, you will now
95 Since :ref:`ref-classes-testimage` is a class intended solely to
157 - The :ref:`ref-classes-image-buildinfo` class now writes to
162 - In the :ref:`ref-classes-archiver` class, the default
[all …]
|
| H A D | migration-general.rst | 79 The :ref:`ref-classes-buildhistory` class can be used
84 #. Enable :ref:`ref-classes-buildhistory` before the migration
88 #. Capture the :ref:`ref-classes-buildhistory` output (as
93 deleting the :ref:`ref-classes-buildhistory` output
96 #. Set a tag in the :ref:`ref-classes-buildhistory` output (which is a git repository) before
105 :ref:`ref-classes-buildhistory` output using ``git diff`` or ``buildhistory-diff``.
107 For more information on using :ref:`ref-classes-buildhistory`, see
|
| H A D | release-notes-5.1.rst | 78 - :ref:`ref-classes-nativesdk` now have :ref:`ref-tasks-package_qa` run when
84 - The :ref:`ref-classes-toolchain-scripts` class now exports the target
99 - Running tests on target with :ref:`ref-classes-testimage` can now be done
102 - Artifact collection when using the :ref:`ref-classes-testimage` class is
181 - The :ref:`ref-classes-prserv` class now uses a shared sqlite3 database to
217 - Remove support for ``DIRFILES`` of :ref:`ref-classes-package_rpm` as it is
238 - :ref:`ref-classes-cve-check` changes:
240 - The class :ref:`ref-classes-cve-check` now uses a local copy of the NVD
243 - New statuses can be reported by :ref:`ref-classes-cve-check`:
263 class :ref:`ref-classes-create-spdx`). New ``create-spdx-image-3.0``
[all …]
|
| H A D | migration-2.1.rst | 68 was a historical accident that has required many classes (e.g.
69 :ref:`ref-classes-autotools`, ``module``) and recipes to override this default in order
103 For recipes inheriting the :ref:`ref-classes-autotools`
111 from the :ref:`ref-classes-autotools` class and the software the recipe is building
116 the default implementation from the :ref:`ref-classes-autotools` class to work such
142 functions have been moved from the :ref:`ref-classes-image` class to the
143 :ref:`rootfs-postcommands <ref-classes-rootfs*>` class. Functionally,
190 The following classes have changed:
193 :ref:`ref-classes-autotools` class now provides its
195 now inherit from :ref:`ref-classes-autotools` instead.
[all …]
|
| H A D | migration-1.5.rst | 91 now documented in the ":ref:`ref-classes-insane`" section.
98 - If you are using the :ref:`ref-classes-buildhistory` class, the check for the
104 documented QA checks in the ":ref:`ref-classes-insane`" section.
133 - When :ref:`ref-classes-buildhistory` is enabled, its output
225 :ref:`ref-classes-packagegroup` instead.
227 For more information, see the ":ref:`ref-classes-packagegroup`" section.
247 :ref:`ref-classes-testimage` classes. This
334 - ``classes/image``: Ensure
338 - ``classes/rootfs_rpm``: Implement :term:`BAD_RECOMMENDATIONS` for RPM.
348 - :ref:`ref-classes-image`: Move ``runtime_mapping_rename`` to avoid conflict
|
| H A D | migration-1.8.rst | 79 kernel recipes that do not inherit from :ref:`ref-classes-kernel-yocto` or
87 :ref:`module <ref-classes-module>` classes might need to add explicit
125 Changes have been made to the :ref:`ref-classes-base`,
126 :ref:`ref-classes-autotools`, and :ref:`ref-classes-cmake` classes to clean out
|
| H A D | release-notes-4.1.rst | 33 - Support ``crate://`` fetcher with :ref:`ref-classes-externalsrc`
55 - The :ref:`ref-classes-pypi` class now defaults :term:`CVE_PRODUCT` from :term:`PYPI_PACKAGE`
63 - Pressure data gathering in :ref:`ref-classes-buildstats` and rendering in ``pybootchartgui``
65 - New Picobuild system for lightweight Python PEP-517 build support in the :ref:`ref-classes-python…
67 - Many classes are now split into global and recipe contexts for better
69 :ref:`Classes now split by usage context <migration-4.1-classes-split>`.
102 - :ref:`ref-classes-image-buildinfo` class now also writes build information to SDKs
104 - rust-llvm: enabled :ref:`ref-classes-nativesdk` variant
105 - python3-pluggy: enabled for :ref:`ref-classes-native` / :ref:`ref-classes-nativesdk`
118 - :ref:`ref-classes-image_types`: isolate the write of UBI
[all …]
|
| H A D | migration-1.6.rst | 14 The :ref:`ref-classes-archiver` class has been rewritten and its configuration
225 Yocto Project Development Tasks Manual. See also the ":ref:`ref-classes-ptest`"
235 recipes that inherit the :ref:`ref-classes-cmake` class. In
236 future releases the :ref:`ref-classes-autotools` class
240 :ref:`autotools-brokensep <ref-classes-autotools>` class instead of
241 the :ref:`ref-classes-autotools` or ``autotools_stage`` classes.
380 .. _migration-1.6-removed-classes:
382 Removed Classes
385 The following classes have become obsolete and have been removed:
|
| H A D | migration-1.3.rst | 66 custom recipes or classes, you need to ensure you are using consistent
95 of the packaging code for :ref:`ref-classes-nativesdk` recipes. All custom
96 :ref:`ref-classes-nativesdk` recipes, which are relocatable packages that are
112 :ref:`ref-classes-packagegroup` instead of ``task``, as well
114 :ref:`ref-classes-packagegroup`, such as providing ``-dev`` and ``-dbg``
116 :ref:`ref-classes-packagegroup` section for further details.
|
| /openbmc/linux/Documentation/mm/ |
| H A D | zsmalloc.rst | 40 # cat /sys/kernel/debug/zsmalloc/zram0/classes
98 zsmalloc has 255 size classes, each of which can hold a number of zspages.
103 As an optimization, zsmalloc merges size classes that have similar
107 For instance, consider the following size classes:::
116 Size classes #95-99 are merged with size class #100. This means that when we
144 dewer class mergers, resulting in a more compact grouping of classes, which
147 Let's take a closer look at the bottom of `/sys/kernel/debug/zsmalloc/zramX/classes`:::
159 in huge classes do not share pages).
162 for the huge size class and fewer huge classes overall. This allows for more
207 pages per zspage number of size classes (clusters) huge size class watermark
[all …]
|
| /openbmc/openbmc/poky/bitbake/lib/bblayers/ |
| H A D | query.py | 58 classes = collections.defaultdict(list)
60 for c in ["classes-global", "classes-recipe", "classes"]:
65 classes[classfile].append(classdir)
67 # Locating classes and other files is a bit more complicated than recipes -
76 for (classfile, classdirs) in classes.items():
79 logger.plain('=== Overlayed classes ===')
82 mainfile = bb.utils.which(bbpath, os.path.join('classes', classfile))
90 classdir = os.path.join(layerdir, 'classes')
129 for c in ["classes-global", "classes-recipe", "classes"]:
183 cls_re = re.compile('classes.*/')
[all …]
|
| /openbmc/openbmc/poky/meta/lib/oe/ |
| H A D | classutils.py | 14 """Maintain a registry of classes, indexed by name.
17 a dictionary to hold the classes by name.
21 method returns the registered classes in priority order.
25 abstract base classes out of the registry)."""
|
| /openbmc/phosphor-logging/extensions/openpower-pels/ |
| H A D | section.hpp | 53 * @brief Get section in JSON. Derived classes to override when required to.
66 * @brief Get section in JSON. Derived classes to override when required to.
82 * @brief Get section in JSON. Derived classes to override when required to.
147 * Implemented by derived classes.
154 * Filled in by derived classes.
166 * @brief Messages that derived classes can add during construction
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | dcbnl.h | 148 * @pfc_cap: Indicates the number of traffic classes on the local device
150 * @pfc_en: bitmap indicating pfc enabled traffic classes
186 * @tcs_supported: number of traffic classes supported
204 * @pfc_en: bitmap indicating pfc enabled traffic classes
205 * @tcs_supported: number of traffic classes supported
291 * @DCB_CMD_GNUMTCS: get the number of traffic classes currently supported
292 * @DCB_CMD_SNUMTCS: set the number of traffic classes
362 * @DCB_ATTR_NUM_TC: number of traffic classes supported in the device (NLA_U8)
367 * @DCB_ATTR_NUMTCS: number of traffic classes supported (NLA_NESTED)
532 * @DCB_PG_ATTR_TC_ALL: apply to all traffic classes (NLA_NESTED)
[all …]
|
| /openbmc/linux/include/linux/platform_data/ |
| H A D | i2c-mux-gpio.h | 21 * @classes: Optional I2C auto-detection classes
29 const unsigned *classes; member
|
| H A D | i2c-mux-reg.h | 20 * @classes: Optional I2C auto-detection classes
33 const unsigned int *classes; member
|
| /openbmc/qemu/scripts/codeconverter/ |
| H A D | converter.py | 57 classes = [p for arg in args.patterns
60 for c in classes:
68 DBG("classes: %r", classes)
69 files.patch_content(max_passes=args.passes, class_names=classes)
|
| /openbmc/openbmc/poky/documentation/sdk-manual/ |
| H A D | appendix-customizing.rst | 47 - Classes inherited globally with :term:`INHERIT` that are listed in
49 :term:`ESDK_CLASS_INHERIT_DISABLE` to disable these classes is the typical
50 method to disable classes that are problematic or unnecessary in the SDK
52 :ref:`ref-classes-buildhistory` and :ref:`ref-classes-icecc` classes.
67 - If your SDK configuration inherits additional classes using the
69 do not need or want those classes enabled in the SDK, you can
83 - If you have classes or recipes that add additional tasks to the
148 :ref:`populate_sdk_base <ref-classes-populate-sdk-*>`
214 :ref:`populate_sdk_base <ref-classes-populate-sdk-*>`
|
| /openbmc/linux/Documentation/locking/ |
| H A D | lockdep-design.rst | 19 The validator tracks the 'usage state' of lock-classes, and it tracks
20 the dependencies between different lock-classes. Lock usage indicates
157 between any two lock-classes::
324 is O(N^2), so even with just a few hundred lock-classes we'd have to do
339 The validator tracks a maximum of MAX_LOCKDEP_KEYS number of lock classes.
345 desktop systems have less than 1,000 lock classes, so this warning
351 load of the module will create a new set of lock classes for
353 classes (see below discussion of reuse of lock classes for why).
355 the number of lock classes will eventually reach the maximum.
360 spinlock_t will consume 8192 lock classes -unless- each spinlock
[all …]
|