Home
last modified time | relevance | path

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

12345678910>>...72

/OK3568_Linux_fs/kernel/drivers/gpu/arm/bifrost/hwcnt/
H A Dmali_kbase_hwcnt_types.c30 struct kbase_hwcnt_metadata *metadata; in kbase_hwcnt_metadata_create() local
47 /* Calculate the bytes needed to tightly pack the metadata */ in kbase_hwcnt_metadata_create()
49 /* Top level metadata */ in kbase_hwcnt_metadata_create()
53 /* Group metadata */ in kbase_hwcnt_metadata_create()
56 /* Block metadata */ in kbase_hwcnt_metadata_create()
61 /* Single allocation for the entire metadata */ in kbase_hwcnt_metadata_create()
66 /* Use the allocated memory for the metadata and its members */ in kbase_hwcnt_metadata_create()
68 /* Bump allocate the top level metadata */ in kbase_hwcnt_metadata_create()
70 metadata = (struct kbase_hwcnt_metadata *)(buf + offset); in kbase_hwcnt_metadata_create()
73 /* Bump allocate the group metadata */ in kbase_hwcnt_metadata_create()
[all …]
H A Dmali_kbase_hwcnt_types.h74 * Metadata:
165 * struct kbase_hwcnt_block_metadata - Metadata describing the physical layout
175 * this metadata start.
177 * Block Instances described by this metadata.
180 * metadata start.
182 * Block Instances described by this metadata.
185 * by this metadata start.
200 * struct kbase_hwcnt_group_metadata - Metadata describing the physical layout
208 * @blk_metadata: Non-NULL pointer to an array of blk_cnt block metadata,
213 * this metadata start.
[all …]
H A Dmali_kbase_hwcnt_gpu_narrow.h34 * struct kbase_hwcnt_metadata_narrow - Narrow metadata describing the physical
37 * metadata only supports 64 counters per
39 * @metadata: Non-NULL pointer to the metadata before narrow down to
46 const struct kbase_hwcnt_metadata *metadata; member
52 * @md_narrow: Non-NULL pointer to narrow metadata used to identify, and to
84 * narrow metadata.
85 * @md_narrow: Non-NULL pointer to narrow metadata.
87 * Return: Number of hardware counter groups described by narrow metadata.
92 return kbase_hwcnt_metadata_group_count(md_narrow->metadata); in kbase_hwcnt_metadata_narrow_group_count()
97 * from narrow metadata.
[all …]
H A Dmali_kbase_hwcnt_gpu.c111 * kbasep_hwcnt_backend_gpu_metadata_create() - Create hardware counter metadata
116 * @metadata: Non-NULL pointer to where created metadata is stored
124 const struct kbase_hwcnt_metadata **metadata) in kbasep_hwcnt_backend_gpu_metadata_create() argument
133 WARN_ON(!metadata); in kbasep_hwcnt_backend_gpu_metadata_create()
204 return kbase_hwcnt_metadata_create(&desc, metadata); in kbasep_hwcnt_backend_gpu_metadata_create()
228 const struct kbase_hwcnt_metadata *metadata; in kbase_hwcnt_jm_metadata_create() local
236 * from the arbiter, the v5 dump bytes and the metadata v5 are in kbase_hwcnt_jm_metadata_create()
242 errcode = kbasep_hwcnt_backend_gpu_metadata_create(gpu_info, false, counter_set, &metadata); in kbase_hwcnt_jm_metadata_create()
248 * metadata since physical HW uses 32-bit per value but metadata in kbase_hwcnt_jm_metadata_create()
251 WARN_ON(dump_bytes * 2 != metadata->dump_buf_bytes); in kbase_hwcnt_jm_metadata_create()
[all …]
H A Dmali_kbase_hwcnt_gpu_narrow.c45 * count in the metadata. in kbase_hwcnt_gpu_metadata_narrow_create()
95 err = kbase_hwcnt_metadata_create(&desc, &metadata_narrow->metadata); in kbase_hwcnt_gpu_metadata_narrow_create()
97 /* Narrow down the buffer size to half as the narrowed metadata in kbase_hwcnt_gpu_metadata_narrow_create()
98 * only supports 32-bit but the created metadata uses 64-bit for in kbase_hwcnt_gpu_metadata_narrow_create()
101 metadata_narrow->dump_buf_bytes = metadata_narrow->metadata->dump_buf_bytes >> 1; in kbase_hwcnt_gpu_metadata_narrow_create()
115 kbase_hwcnt_metadata_destroy(md_narrow->metadata); in kbase_hwcnt_gpu_metadata_narrow_destroy()
130 clk_cnt_buf_bytes = sizeof(*dump_buf->clk_cnt_buf) * md_narrow->metadata->clk_cnt; in kbase_hwcnt_dump_buffer_narrow_alloc()
173 clk_cnt_buf_bytes = sizeof(*dump_bufs->bufs->clk_cnt_buf) * md_narrow->metadata->clk_cnt; in kbase_hwcnt_dump_buffer_narrow_array_alloc()
248 WARN_ON(dst_narrow->md_narrow->metadata == src->metadata) || in kbase_hwcnt_dump_buffer_copy_strict_narrow()
249 WARN_ON(dst_narrow->md_narrow->metadata->grp_cnt != src->metadata->grp_cnt) || in kbase_hwcnt_dump_buffer_copy_strict_narrow()
[all …]
H A Dmali_kbase_hwcnt_virtualizer.c37 * @metadata: Hardware counter metadata.
50 const struct kbase_hwcnt_metadata *metadata; member
84 return hvirt->metadata; in kbase_hwcnt_virtualizer_metadata()
106 * @metadata: Non-NULL pointer to counter metadata.
112 static int kbasep_hwcnt_virtualizer_client_alloc(const struct kbase_hwcnt_metadata *metadata, in kbasep_hwcnt_virtualizer_client_alloc() argument
118 WARN_ON(!metadata); in kbasep_hwcnt_virtualizer_client_alloc()
125 errcode = kbase_hwcnt_enable_map_alloc(metadata, &hvcli->enable_map); in kbasep_hwcnt_virtualizer_client_alloc()
129 errcode = kbase_hwcnt_dump_buffer_alloc(metadata, &hvcli->accum_buf); in kbasep_hwcnt_virtualizer_client_alloc()
205 errcode = kbase_hwcnt_enable_map_alloc(hvirt->metadata, &hvirt->scratch_map); in kbasep_hwcnt_virtualizer_accumulator_init()
209 errcode = kbase_hwcnt_dump_buffer_alloc(hvirt->metadata, &hvirt->scratch_buf); in kbasep_hwcnt_virtualizer_accumulator_init()
[all …]
/OK3568_Linux_fs/kernel/Documentation/filesystems/
H A Dxfs-self-describing-metadata.rst4 XFS Self Describing Metadata
16 Almost all metadata on XFS is dynamically allocated. The only fixed location
17 metadata is the allocation group headers (SB, AGF, AGFL and AGI), while all
18 other metadata structures need to be discovered by walking the filesystem
31 However, if we scale the filesystem up to 1PB, we now have 10x as much metadata
39 Self Describing Metadata
42 One of the problems with the current metadata format is that apart from the
43 magic number in the metadata block, we have no other way of identifying what it
45 you can't look at a single metadata block in isolation and say "yes, it is
49 verification of metadata values, looking for values that are in range (and hence
[all …]
/OK3568_Linux_fs/kernel/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 …]
/OK3568_Linux_fs/kernel/drivers/gpu/drm/vmwgfx/
H A Dvmwgfx_surface.c45 * @srf: The surface metadata.
202 return srf->metadata.num_sizes * sizeof(struct vmw_surface_dma); in vmw_surface_dma_size()
216 return sizeof(struct vmw_surface_define) + srf->metadata.num_sizes * in vmw_surface_define_size()
265 cmd_len = sizeof(cmd->body) + srf->metadata.num_sizes * in vmw_surface_define_encode()
276 cmd->body.surfaceFlags = (SVGA3dSurface1Flags)srf->metadata.flags; in vmw_surface_define_encode()
277 cmd->body.format = srf->metadata.format; in vmw_surface_define_encode()
279 cmd->body.face[i].numMipLevels = srf->metadata.mip_levels[i]; in vmw_surface_define_encode()
283 src_size = srf->metadata.sizes; in vmw_surface_define_encode()
285 for (i = 0; i < srf->metadata.num_sizes; ++i, cmd_size++, src_size++) { in vmw_surface_define_encode()
309 svga3dsurface_get_desc(srf->metadata.format); in vmw_surface_dma_encode()
[all …]
/OK3568_Linux_fs/kernel/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 performaing 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 useable 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 …]
H A Dcache.rst20 The target reuses the metadata library used in the thin-provisioning
56 3. A small metadata device - records which blocks are in the cache,
60 e.g. as a mirror for extra robustness. This metadata device may only
75 block sizes are bad because they increase the amount of metadata (both
86 the metadata.
131 Updating on-disk metadata
134 On-disk metadata is committed every time a FLUSH or FUA bio is written.
137 cache. If power is lost you may lose some recent writes. The metadata
181 cache <metadata dev> <cache dev> <origin dev> <block size>
186 metadata dev fast device holding the persistent metadata
[all …]
H A Ddm-clone.rst29 The dm-clone target reuses the metadata library used by the thin-provisioning
58 3. A small metadata device - it records which regions are already valid in the
95 only updates its metadata.
124 Updating on-disk metadata
127 On-disk metadata is committed every time a FLUSH or FUA bio is written. If no
130 power is lost you may lose some recent writes. The metadata should always be
141 clone <metadata dev> <destination dev> <source dev> <region size>
145 metadata dev Fast device holding the persistent metadata
184 <metadata block size> <#used metadata blocks>/<#total metadata blocks>
187 <clone metadata mode>
[all …]
/OK3568_Linux_fs/kernel/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()
203 /* create metadata channel */ in ia_css_isys_stream_create()
204 if (isys_stream_descr->metadata.enable) { in ia_css_isys_stream_create()
225 /* Destroy metadata channel only if its allocated*/ in ia_css_isys_stream_destroy()
254 /* configure metadata channel */ in ia_css_isys_stream_calculate_cfg()
[all …]
/OK3568_Linux_fs/buildroot/package/gvfs/
H A D0001-meson.build-fix-linking-with-libmetadata.patch8 libmetadata_dep or gvfsd-metadata will fail to link on:
10 FAILED: metadata/gvfsd-metadata
11metadata/gvfsd-metadata 'metadata/45447b7@@gvfsd-metadata@exe/meta-daemon.c.o' -Wl,--as-needed -Wl…
12 metadata/libmetadata.a(metatree.c.o): In function `safe_open':
17 gvfsd-metadata to avoid any other build failures.
27 metadata/meson.build | 5 +++--
44 diff --git a/metadata/meson.build b/metadata/meson.build
46 --- a/metadata/meson.build
47 +++ b/metadata/meson.build
/OK3568_Linux_fs/kernel/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 …]
/OK3568_Linux_fs/kernel/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 …]
/OK3568_Linux_fs/kernel/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 …]
/OK3568_Linux_fs/yocto/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
87 within the kernel Metadata with which to build out the sources and
120 within the kernel Metadata itself. The examples here are taken from the
[all …]
/OK3568_Linux_fs/yocto/poky/bitbake/lib/bb/
H A Dcache.py44 def listvar(cls, var, metadata): argument
45 return cls.getvar(var, metadata).split()
48 def intvar(cls, var, metadata): argument
49 return int(cls.getvar(var, metadata) or 0)
52 def depvar(cls, var, metadata): argument
53 return bb.utils.explode_deps(cls.getvar(var, metadata))
56 def pkgvar(cls, var, packages, metadata): argument
57 return dict((pkg, cls.depvar("%s:%s" % (var, pkg), metadata))
61 def taskvar(cls, var, tasks, metadata): argument
62 return dict((task, cls.getvar("%s:task-%s" % (var, task), metadata))
[all …]
/OK3568_Linux_fs/kernel/fs/incfs/
H A Dformat.h10 * list of metadata blocks. Each metadata block contains an offset of the next
17 * the metadata list is stored in the superblock at the beginning of the backing
33 * Metadata records
35 * incfs_blockmap - metadata record that specifies size and location
38 * incfs_file_signature - metadata record that specifies where file signature
41 * incfs_file_attr - metadata record that specifies where additional file
44 * Metadata header
46 * incfs_md_header - header of a metadata record. It's always a part
47 * of other structures and served purpose of metadata
58 * | Metadata record body with useful data | |
[all …]
/OK3568_Linux_fs/yocto/poky/meta/recipes-extended/mdadm/files/
H A D0001-tests-fix-raid0-tests-for-0.90-metadata.patch4 Subject: [PATCH] tests: fix raid0 tests for 0.90 metadata
7 "0.90 metadata does not support layouts for RAID0" added by commit,
9 linear level for 0.9 metadata where possible.
23 tests/04update-metadata | 2 +-
45 @@ -4,6 +4,10 @@ for metadata in 0.9 1.0 1.1 1.2
49 + if [[ $metadata == "0.9" && $level == "raid0" ]];
53 mdadm -CR $md0 -l $level -n 4 --metadata=$metadata \
64 -mdadm -CR $md2 -l0 --metadata=0.90 -n3 $dev0 $dev1 $dev2
67 +mdadm -CR $md2 -llinear --metadata=0.90 -n3 $dev0 $dev1 $dev2
87 diff --git a/tests/04update-metadata b/tests/04update-metadata
[all …]
/OK3568_Linux_fs/buildroot/dl/qt5location/git/src/plugins/geoservices/mapboxgl/
H A Dqgeomappingmanagerenginemapboxgl.cpp81 QVariantMap metadata; in QGeoMappingManagerEngineMapboxGL() local
82 metadata["isHTTPS"] = true; in QGeoMappingManagerEngineMapboxGL()
88 tr("China Streets"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
90 tr("China Light"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
92 tr("China Dark"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
95 tr("Streets"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
97 tr("Basic"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
99 tr("Bright"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
101 tr("Outdoors"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
103 tr("Satellite"), false, false, ++mapId, pluginName, cameraCaps, metadata); in QGeoMappingManagerEngineMapboxGL()
[all …]
/OK3568_Linux_fs/yocto/poky/scripts/lib/devtool/
H A Dimport.py26 metadata = name.split('/')[-1]
27 fn, _ = os.path.splitext(metadata)
34 # Get exported metadata
37 metadata = tar.getmember(export.metadata)
39 …raise DevtoolError('The export metadata file created by "devtool export" was not found. "devtool i…
41 tar.extract(metadata)
42 with open(metadata.name) as fdm:
44 os.unlink(metadata.name)
65 # Find those appends that do not have recipes in current metadata
68 # Check on current metadata (covering those layers indicated in bblayers.conf)
[all …]

12345678910>>...72