Home
last modified time | relevance | path

Searched full:metadata (Results 1 – 25 of 1902) sorted by relevance

12345678910>>...77

/openbmc/pldm/tools/fw-update/
H A DREADME.md21 metadatafile Path of metadata JSON file
27 - Providing the metadata JSON file is a must
31 metadata json
33 ## Metadata JSON file
36 in an input metadata file (see the section 'Mapping fields to DSP0267') that's
39 metadata JSON files can be reused. The key names used in the metadata JSON
40 _match with the proprerty names_ used in DSP0267. There is an example metadata
41 json file included - metadata-example.json, which has example entries for
55 Metadata JSON must have a key called "PackageHeaderInformation", which is of
58 - PackageHeaderIdentifier: Supported, must be specified in metadata file
[all …]
H A Dpldm_fwup_pkg_creator.py97 def write_package_version_string(pldm_fw_up_pkg, metadata): argument
104 metadata: metadata about PLDM FW update package
108 package_version_string = metadata["PackageHeaderInformation"][
123 def write_component_bitmap_bit_length(pldm_fw_up_pkg, metadata): argument
133 metadata: metadata about PLDM FW update package
144 num_components = len(metadata["ComponentImageInformationArea"])
154 def write_pkg_header_info(pldm_fw_up_pkg, metadata): argument
164 metadata: metadata about PLDM FW update package
171 uuid = metadata["PackageHeaderInformation"]["PackageHeaderIdentifier"]
175 package_header_format_revision = metadata["PackageHeaderInformation"][
[all …]
/openbmc/linux/Documentation/networking/
H A Dxdp-rx-metadata.rst2 XDP RX Metadata
6 hardware metadata related to a packet using a set of helper functions,
7 and how it can pass that metadata on to other consumers.
12 XDP has access to a set of kfuncs to manipulate the metadata in an XDP frame.
13 Every device driver that wishes to expose additional packet metadata can
18 metadata is supported, this set will grow:
23 An XDP program can use these kfuncs to read the metadata into stack
24 variables for its own consumption. Or, to pass the metadata on to other
25 consumers, an XDP program can store it into the metadata area carried
27 metadata available in which case the driver returns ``-ENODATA``.
[all …]
/openbmc/linux/Documentation/filesystems/
H A Dxfs-self-describing-metadata.rst5 XFS Self Describing Metadata
17 Almost all metadata on XFS is dynamically allocated. The only fixed location
18 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
19 other metadata structures need to be discovered by walking the filesystem
32 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata
40 Self Describing Metadata
43 One of the problems with the current metadata format is that apart from the
44 magic number in the metadata block, we have no other way of identifying what it
46 you can't look at a single metadata block in isolation and say "yes, it is
50 verification of metadata values, looking for values that are in range (and hence
[all …]
/openbmc/libbej/src/
H A Dbej_encoder_metadata.c194 node->leaf.metaData.sequenceNumber = sequenceNumber; in bejUpdateIntMetaData()
198 node->leaf.metaData.sflSize = bejNnintEncodingSizeOfUInt(sequenceNumber); in bejUpdateIntMetaData()
200 node->leaf.metaData.sflSize += BEJ_TUPLE_F_SIZE; in bejUpdateIntMetaData()
202 node->leaf.metaData.sflSize += BEJ_TUPLE_L_SIZE_FOR_BEJ_INTEGER; in bejUpdateIntMetaData()
204 node->leaf.metaData.vSize = bejIntLengthOfValue(node->value); in bejUpdateIntMetaData()
217 node->leaf.metaData.sequenceNumber = sequenceNumber; in bejUpdateStringMetaData()
221 node->leaf.metaData.sflSize = bejNnintEncodingSizeOfUInt(sequenceNumber); in bejUpdateStringMetaData()
223 node->leaf.metaData.sflSize += BEJ_TUPLE_F_SIZE; in bejUpdateStringMetaData()
227 node->leaf.metaData.sflSize += bejNnintEncodingSizeOfUInt(strLenWithNull); in bejUpdateStringMetaData()
229 node->leaf.metaData.vSize = strLenWithNull; in bejUpdateStringMetaData()
[all …]
/openbmc/linux/drivers/md/
H A Ddm-clone-metadata.h10 #include "persistent-data/dm-space-map-metadata.h"
15 * The metadata device is currently limited in size.
20 * A metadata device larger than 16GB triggers a warning.
26 /* dm-clone metadata */
32 * @cmd: The dm-clone metadata
43 * @cmd: The dm-clone metadata
55 * Read existing or create fresh metadata.
57 * @bdev: The device storing the metadata
61 * @returns: The dm-clone metadata
64 * If it is, it formats @bdev and creates fresh metadata. If it isn't, it
[all …]
/openbmc/linux/drivers/gpu/drm/vmwgfx/
H A Dvmwgfx_surface.c48 * @srf: The surface metadata.
199 return srf->metadata.num_sizes * sizeof(struct vmw_surface_dma); in vmw_surface_dma_size()
213 return sizeof(struct vmw_surface_define) + srf->metadata.num_sizes * in vmw_surface_define_size()
262 cmd_len = sizeof(cmd->body) + srf->metadata.num_sizes * in vmw_surface_define_encode()
273 cmd->body.surfaceFlags = (SVGA3dSurface1Flags)srf->metadata.flags; in vmw_surface_define_encode()
274 cmd->body.format = srf->metadata.format; in vmw_surface_define_encode()
276 cmd->body.face[i].numMipLevels = srf->metadata.mip_levels[i]; in vmw_surface_define_encode()
280 src_size = srf->metadata.sizes; in vmw_surface_define_encode()
282 for (i = 0; i < srf->metadata.num_sizes; ++i, cmd_size++, src_size++) { in vmw_surface_define_encode()
306 vmw_surface_get_desc(srf->metadata.format); in vmw_surface_dma_encode()
[all …]
/openbmc/linux/drivers/staging/media/atomisp/pci/runtime/isys/src/
H A Dvirtual_isys.c37 bool metadata,
55 bool metadata);
119 bool metadata,
124 bool metadata,
141 bool metadata,
176 isys_stream->enable_metadata = isys_stream_descr->metadata.enable; in ia_css_isys_stream_create()
192 /* create metadata channel */ in ia_css_isys_stream_create()
193 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_create()
214 /* Destroy metadata channel only if its allocated*/ in ia_css_isys_stream_destroy()
243 /* configure metadata channel */ in ia_css_isys_stream_calculate_cfg()
[all …]
/openbmc/linux/Documentation/admin-guide/device-mapper/
H A Dthin-provisioning.rst24 Metadata is stored on a separate device from data, giving the
27 - Improve metadata resilience by storing metadata on a mirrored volume
30 - Improve performance by storing the metadata on SSD.
43 Userspace tools for checking and repairing the metadata have been fully
59 The pool device ties together the metadata volume and the data volume.
60 It maps I/O linearly to the data volume and updates the metadata via
71 Setting up a pool device requires a valid metadata device, and a
72 data device. If you do not have an existing metadata device you can
73 make one by zeroing the first 4k to indicate empty metadata.
77 The amount of metadata you need will vary according to how many blocks
[all …]
H A Dera.rst21 era <metadata dev> <origin dev> <block size>
24 metadata dev fast device holding the persistent metadata
45 Create a clone of the metadata, to allow a userland process to read it.
50 Drop the metadata snapshot.
55 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
56 <current era> <held metadata root | '-'>
59 metadata block size Fixed block size for each metadata block in
61 #used metadata blocks Number of metadata blocks used
62 #total metadata blocks Total number of metadata blocks
64 held metadata root The location, in blocks, of the metadata root
[all …]
H A Ddm-zoned.rst27 internally for storing metadata and performing reclaim operations.
40 metadata. It can also use a regular block device together with the zoned
48 1) Metadata zones: these are conventional zones used to store metadata.
49 Metadata zones are not reported as usable capacity to the user.
60 device being used. This allows reducing the amount of metadata needed to
63 The on-disk metadata format is as follows:
66 super block which describes the on disk amount and position of metadata
114 Metadata Protection
117 To protect metadata against corruption in case of sudden power loss or
118 system crash, 2 sets of metadata zones are used. One set, the primary
[all …]
/openbmc/linux/drivers/staging/media/atomisp/pci/
H A Dia_css_metadata.h20 * This file contains structure for processing sensor metadata.
27 /* Metadata configuration. This data structure contains necessary info
28 * to process sensor metadata.
53 /* @brief Allocate a metadata buffer.
54 * @param[in] metadata_info Metadata info struct, contains details on metadata buffers.
55 * @return Pointer of metadata buffer or NULL (if error)
57 * This function allocates a metadata buffer according to the properties
63 /* @brief Free a metadata buffer.
65 * @param[in] metadata Pointer of metadata buffer.
68 * This function frees a metadata buffer.
[all …]
/openbmc/openpower-proc-control/
H A Dcfam_access.cpp61 using metadata = xyz::openbmc_project::Common::File::Seek; in writeReg() typedef
63 elog<file_error::Seek>(metadata::OFFSET(makeOffset(address)), in writeReg()
64 metadata::WHENCE(SEEK_SET), in writeReg()
65 metadata::ERRNO(errno), in writeReg()
66 metadata::PATH(target->getCFAMPath().c_str())); in writeReg()
74 using metadata = xyz::openbmc_project::Common::Device::WriteFailure; in writeReg() typedef
77 metadata::CALLOUT_ERRNO(errno), in writeReg()
78 metadata::CALLOUT_DEVICE_PATH(target->getCFAMPath().c_str())); in writeReg()
95 using metadata = xyz::openbmc_project::Common::File::Seek; in readReg() typedef
97 elog<file_error::Seek>(metadata::OFFSET(makeOffset(address)), in readReg()
[all …]
/openbmc/linux/Documentation/userspace-api/media/v4l/
H A Ddev-meta.rst6 Metadata Interface
9 Metadata refers to any non-image data that supplements video frames with
13 intended for transfer of metadata between the userspace and the hardware and
16 The metadata interface is implemented on video device nodes. The device can be
17 dedicated to metadata or can support both video and metadata as specified in its
23 Device nodes supporting the metadata capture interface set the
26 ioctl. That flag means the device can capture metadata to memory. Similarly,
27 device nodes supporting metadata output interface set the
30 metadata from memory.
38 The metadata device uses the :ref:`format` ioctls to select the capture format.
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D079.out4 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
5 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
6 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
7 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
8 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
9 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
10 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
11 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
12 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=4294967296 preallocation=metadata
H A D125.out10 --- cluster_size=512 growth_size=16 create_mode=off growth_mode=metadata ---
34 --- cluster_size=512 growth_size=16 create_mode=metadata growth_mode=off ---
35 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2048000 preallocation=metadata
42 --- cluster_size=512 growth_size=16 create_mode=metadata growth_mode=metadata ---
43 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2048000 preallocation=metadata
50 --- cluster_size=512 growth_size=16 create_mode=metadata growth_mode=falloc ---
51 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2048000 preallocation=metadata
58 --- cluster_size=512 growth_size=16 create_mode=metadata growth_mode=full ---
59 Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=2048000 preallocation=metadata
74 --- cluster_size=512 growth_size=16 create_mode=falloc growth_mode=metadata ---
[all …]
/openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-m/files/corstone1000/
H A D0007-Plaform-Corstone1000-Switch-to-metadata-v2.patch4 Subject: [PATCH 7/9] Plaform: Corstone1000: Switch to metadata v2
6 This upgrades metadata data structs from v1 to v2 as described in PSA
10 The TrustedFirmware-A v2.11 release supports only the metadata v2. The
33 + * Metadata version 2 data structures defined by PSA_FW update specification
68 /* Metadata CRC value */
75 + /* Size of the entire metadata in bytes */
125 - /* Calculate CRC32 for fwu metadata */
126 + /* Calculate CRC32 for fwu metadata. The first filed in the _metadata has to be the crc_32.
144 - (metadata->img_entry[IMAGE_0].img_props[active_index].version)) {
145 + (metadata->fw_desc.img_entry[IMAGE_0].img_props[active_index].version)) {
[all …]
/openbmc/linux/Documentation/block/
H A Ddata-integrity.rst8 Modern filesystems feature checksumming of data and metadata to
18 support for appending integrity metadata to an I/O. The integrity
19 metadata (or protection information in SCSI terminology) includes a
40 allow the operating system to interact with the integrity metadata
46 information to each sector. The data + integrity metadata is stored
53 encouraged them to allow separation of the data and integrity metadata
67 when writing and vice versa. This allows the integrity metadata to be
73 buffers and the integrity metadata. These two distinct buffers must
76 The separation of the data and integrity metadata buffers as well as
108 the kernel) is concerned, the integrity metadata is opaque information
[all …]
/openbmc/openbmc/poky/bitbake/lib/bb/
H A Dcache.py45 def listvar(cls, var, metadata): argument
46 return cls.getvar(var, metadata).split()
49 def intvar(cls, var, metadata): argument
50 return int(cls.getvar(var, metadata) or 0)
53 def depvar(cls, var, metadata): argument
54 return bb.utils.explode_deps(cls.getvar(var, metadata))
57 def pkgvar(cls, var, packages, metadata): argument
58 return dict((pkg, cls.depvar("%s:%s" % (var, pkg), metadata))
62 def taskvar(cls, var, tasks, metadata): argument
63 return dict((task, cls.getvar("%s:task-%s" % (var, task), metadata))
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/
H A DREADME.md16 An OpenBMC error has associated metadata, the same is true for a callout. Such
17 metadata would be defined in the callout YAML interface. Here is an example (for
30 metadata fields above. These fields will also let the error handling component
44 The way this inheritance will be implemented is that, Foo's metadata will
46 will have to provide values for Foo and IIC metadata. Like mentioned before, due
47 to the presence of the Callout.IIC metadata, the error handling component can
51 `xyz.openbmc_project.Error.Callout.Device`, which has metadata common to
65 metadata fields for both Callout.Device and Callout.IIC, but provide values only
71 This section talks about creation of a callout, once callout related metadata is
77 - An application commits an error that has associated callout metadata. This
[all …]
/openbmc/phosphor-logging/
H A Delog_meta.hpp21 namespace metadata namespace
24 using Metadata = std::string; typedef
32 /** @brief Build error associations specific to metadata. Specialize this
33 * template for handling a specific type of metadata.
34 * @tparam M - type of metadata
35 * @param [in] match - metadata to be handled
36 * @param [in] data - metadata key=value entries
44 // for this metadata.
58 auto metadata = util::additional_data::parse(data); in build() local
59 auto iter = metadata.find(match); in build()
[all …]
H A Dutil.hpp30 /** @brief Pull out metadata name and value from the string
31 * <metadata name>=<metadata value>
32 * @param [in] data - metadata key=value entries
33 * @return map of metadata name:value
37 /** @brief Combine the metadata keys and values from the map
39 * "<metadata name>=<metadata value>"
40 * @param [in] data - metadata key:value map
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DThreshold.events.yaml7 metadata:
17 metadata:
39 metadata:
61 metadata:
83 metadata:
105 metadata:
127 metadata:
149 metadata:
171 metadata:
193 metadata:
[all …]
/openbmc/phosphor-dbus-monitor/src/
H A Delog.hpp44 * elog metadata.
71 * @tparam Args - Metadata fields types.
86 * The elog callback logs the elog and elog metadata.
89 * @tparam Args - Metadata fields types.
90 * @param[in] arguments - Metadata fields to be added to the error log
118 * current values of certain properties in the metadata of the
122 * metadata that includes the property names and values that caused
133 * This class requires that the error log created only have 1 metadata field,
137 * @tparam metadataType - The metadata to use
173 * @brief Builds a metadata string with property information
[all …]
/openbmc/openbmc/poky/documentation/kernel-dev/
H A Dadvanced.rst4 Working with Advanced Metadata (``yocto-kernel-cache``)
12 :term:`Metadata` that you can use to define
14 the Metadata and the tools that manage it is to help you manage the
18 Kernel Metadata exists in many places. One area in the
31 Using Kernel Metadata in a Recipe
35 Metadata, which is located in the ``yocto-kernel-cache`` Git repository.
36 This Metadata defines Board Support Packages (BSPs) that correspond to
44 A Linux kernel recipe that contains kernel Metadata (e.g. inherits
86 within the kernel Metadata with which to build out the sources and
119 within the kernel Metadata itself. The examples here are taken from the
[all …]

12345678910>>...77