| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/selftests/ |
| D | i915_gem_evict.c | 38 struct list_head *objects) in quirk_add() argument
43 list_add(&obj->st_link, objects); in quirk_add()
46 static int populate_ggtt(struct i915_ggtt *ggtt, struct list_head *objects) in populate_ggtt() argument
69 quirk_add(obj, objects); in populate_ggtt()
109 LIST_HEAD(objects); in igt_evict_something()
114 err = populate_ggtt(ggtt, &objects); in igt_evict_something()
147 cleanup_objects(ggtt, &objects); in igt_evict_something()
157 LIST_HEAD(objects); in igt_overcommit()
164 err = populate_ggtt(ggtt, &objects); in igt_overcommit()
174 quirk_add(obj, &objects); in igt_overcommit()
[all …]
|
| D | intel_memory_region.c | 28 struct list_head *objects) in close_objects() argument
33 list_for_each_entry_safe(obj, on, objects, st_link) { in close_objects()
55 LIST_HEAD(objects); in igt_mock_fill()
78 list_add(&obj->st_link, &objects); in igt_mock_fill()
94 close_objects(mem, &objects); in igt_mock_fill()
101 struct list_head *objects, in igt_object_create() argument
116 list_add(&obj->st_link, objects); in igt_object_create()
137 LIST_HEAD(objects); in igt_mock_contiguous()
148 obj = igt_object_create(mem, &objects, mem->mm.chunk_size, in igt_mock_contiguous()
162 obj = igt_object_create(mem, &objects, total, I915_BO_ALLOC_CONTIGUOUS); in igt_mock_contiguous()
[all …]
|
| /kernel/linux/linux-5.10/scripts/ |
| D | link-vmlinux.sh | 75 local objects
78 objects="--whole-archive \
101 ${LD} ${KBUILD_LDFLAGS} -r -o ${1} ${lds} ${objects}
140 local objects
157 objects="--whole-archive \
162 objects="--whole-archive \
174 -T ${lds} ${objects}
176 objects="-Wl,--whole-archive \
188 ${objects} \
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| D | overview.rst | 26 network ports to create functional objects/devices such as network
29 which DPAA2 software drivers use to operate on DPAA2 objects.
71 DPIO objects.
76 The section provides a brief overview of some key DPAA2 objects.
77 A simple scenario is described illustrating the objects involved
84 types of DPAA2 objects. In the example diagram below there
85 are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC)
105 of the DPRC, discover the hardware objects present (including mappable
118 Hardware objects can be created and destroyed dynamically, providing
119 the ability to hot plug/unplug objects in and out of the DPRC.
[all …]
|
| D | ethernet-driver.rst | 30 Complex (MC) portals. MC abstracts most of these resources as DPAA2 objects
33 are treated as internal resources of other objects.
70 of DPCON objects, using DPIO portals for managing and communicating with the
106 all DPAA2 objects (and implicitly all DPAA2 kernel drivers) that work with data
161 DPNI objects (and the other DPAA2 objects needed for a network interface) can be
164 dynamically at runtime, via the DPAA2 objects APIs.
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_lease.c | 380 struct drm_mode_object **objects, in validate_lease() argument
392 if (objects[o]->type == DRM_MODE_OBJECT_CRTC && has_crtc == -1) { in validate_lease()
395 if (objects[o]->type == DRM_MODE_OBJECT_CONNECTOR && has_connector == -1) in validate_lease()
399 if (objects[o]->type == DRM_MODE_OBJECT_PLANE && has_plane == -1) in validate_lease()
416 struct drm_mode_object **objects; in fill_object_idr() local
421 objects = kcalloc(object_count, sizeof(struct drm_mode_object *), in fill_object_idr()
423 if (!objects) in fill_object_idr()
429 objects[o] = drm_mode_object_find(dev, lessor_priv, in fill_object_idr()
432 if (!objects[o]) { in fill_object_idr()
437 if (!drm_mode_object_lease_required(objects[o]->type)) { in fill_object_idr()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | fscache.rst | 104 (5) Cookies are used to represent indices, files and other objects to the
131 FS-Cache maintains a virtual indexing tree in which all indices, files, objects
165 indexed by NFS file handles to get data file objects. Each data file
166 objects can have an array of pages, but may also have further child
167 objects, such as extended attributes and directory entries. Extended
168 attribute objects themselves have page-array contents.
173 Each of these contains vnode data file objects, each of which contains an
223 |Objects |alc=N |Number of objects allocated |
227 | |avl=N |Number of objects that reached the available state |
229 | |ded=N |Number of objects that reached the dead state |
[all …]
|
| D | object.rst | 27 currently interested in. Such objects are represented by the fscache_cookie
30 FS-Cache also maintains a separate in-kernel representation of the objects that
31 a cache backend is currently actively caching. Such objects are represented by
34 as objects.
36 There is a 1:N relationship between cookies and objects. A cookie may be
37 represented by multiple objects - an index may exist in more than one cache -
38 or even by no objects (it may not be cached).
40 Furthermore, both cookies and objects are hierarchical. The two hierarchies
84 and DObject represent data storage objects. Indices may have representation in
85 multiple caches, but currently, non-index objects may not. Objects of any type
[all …]
|
| /kernel/linux/linux-5.10/scripts/kconfig/ |
| D | streamline_config.pl | 145 my %objects;
336 if (defined($objects{$1})) {
337 @arr = @{$objects{$1}};
344 $objects{$1} = \@arr;
399 if (defined($objects{$module})) {
400 my @arr = @{$objects{$module}};
691 if (defined($objects{$module})) {
692 my @arr = @{$objects{$module}};
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/i915/gem/ |
| D | i915_gem_region.c | 115 mutex_lock(&mem->objects.lock); in i915_gem_object_init_memory_region()
118 list_add(&obj->mm.region_link, &mem->objects.purgeable); in i915_gem_object_init_memory_region()
120 list_add(&obj->mm.region_link, &mem->objects.list); in i915_gem_object_init_memory_region()
122 mutex_unlock(&mem->objects.lock); in i915_gem_object_init_memory_region()
129 mutex_lock(&mem->objects.lock); in i915_gem_object_release_memory_region()
131 mutex_unlock(&mem->objects.lock); in i915_gem_object_release_memory_region()
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kmemleak.rst | 7 with the difference that the orphan objects are not freed but only
17 number of new unreferenced objects found. If the ``debugfs`` isn't already
37 Note that the orphan objects are listed in the order they were allocated
39 objects to be reported as orphan.
61 marking all current reported unreferenced objects grey,
62 or free all kmemleak objects if kmemleak has been disabled.
99 1. mark all objects as white (remaining white objects will later be
105 3. scan the gray objects for matching addresses (some white objects
108 4. the remaining white objects are considered orphan and reported via
123 'clear' command to clear all reported unreferenced objects from the
[all …]
|
| /kernel/linux/linux-5.10/tools/build/Documentation/ |
| D | Build.txt | 5 idea and the way how objects are built is the same.
7 Basically the user provides set of 'Build' files that list objects and
11 we setup source objects, but we support more. This allows one 'Build' file to
12 carry a sources list for multiple build objects.
46 The user supplies 'Build' makefiles that contains a objects list, and connects
64 only prepares proper objects to be compiled and grouped together.
86 which creates the following objects:
91 that contain request objects names in Build files.
166 $ make util/map.o # objects
|
| /kernel/linux/linux-5.10/Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 13 is scanned in search of device objects that generally represent various pieces
16 and the hierarchy of those struct acpi_device objects reflects the namespace
17 layout (i.e. parent device objects in the namespace are represented by parent
18 struct acpi_device objects and analogously for their children). Those struct
19 acpi_device objects are referred to as "device nodes" in what follows, but they
20 should not be confused with struct device_node objects used by the Device Trees
21 parsing code (although their role is analogous to the role of those objects).
28 information from the device objects represented by them and populating them with
38 basis of the device node's hardware ID (HID). They are performed by objects
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | Build.txt | 18 main makefile that triggers build of all perf objects including
28 makefiles that defines build objects
36 The Makefile.perf triggers the build framework for build objects:
39 resulting in following objects:
43 Those objects are then used in final linking:
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | debug-objects.rst | 11 kernel objects and validate the operations on those.
15 - Activation of uninitialized objects
17 - Initialization of active objects
19 - Usage of freed/destroyed objects
62 tracking objects and the state of the internal tracking objects pool.
75 active and destroyed objects. When debugobjects detects an error, then
98 active and destroyed objects. When debugobjects detects an error, then
112 object returns. Otherwise we keep track of stale objects.
122 active and destroyed objects. When debugobjects detects an error, then
131 objects. The fixup function checks whether the object is valid and calls
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/sysctl/ |
| D | user.rst | 15 limits on the number of namespaces and other objects that have
19 malfunction and attempt to create a ridiculous number of objects,
24 The creation of per user per user namespace objects are charged to
28 The creation of objects is also charged to all of the users
33 This recursive counting of created objects ensures that creating a
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-kernel-slab | 48 The alloc_fastpath file shows how many objects have been
72 was empty but there were objects available as the result of
93 The alloc_slowpath file shows how many objects have been
105 The cache_dma file is read-only and specifies whether objects
168 has been deactivated and contained free objects that were freed
201 slabs (not objects) are freed by rcu.
230 The free_fastpath file shows how many objects have been freed
241 The free_frozen file shows how many objects have been freed to
275 The free_slowpath file shows how many objects have been freed
287 objects are aligned on cachelines.
[all …]
|
| /kernel/linux/linux-5.10/tools/vm/ |
| D | slabinfo.c | 36 unsigned long partial, objects, slabs, objects_partial, objects_total; member
360 return slab_size(s) - s->objects * s->object_size; in slab_waste()
536 s->name, s->aliases, s->order, s->objects); in report()
553 onoff(s->red_zone), s->objects * s->object_size); in report()
556 s->slabs * (page_size << s->order) - s->objects * s->object_size); in report()
559 (s->slab_size - s->object_size) * s->objects); in report()
633 s->name, s->objects, in slabcache()
641 s->name, s->objects, s->object_size, size_str, dist_str, in slabcache()
644 s->slabs ? (s->objects * s->object_size * 100) / in slabcache()
704 if (s->objects > 0) in slab_empty()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | zsmalloc.rst | 21 For simplicity, zsmalloc can only allocate objects of size up to PAGE_SIZE
64 the number of objects allocated
66 the number of objects allocated to the user
74 * n = number of allocated objects
75 * N = total number of objects zspage can store
|
| /kernel/linux/linux-5.10/lib/ |
| D | test_meminit.c | 324 void *objects[10]; in do_kmem_cache_size_bulk() local
328 num = kmem_cache_alloc_bulk(c, GFP_KERNEL, ARRAY_SIZE(objects), in do_kmem_cache_size_bulk()
329 objects); in do_kmem_cache_size_bulk()
331 bytes = count_nonzero_bytes(objects[i], size); in do_kmem_cache_size_bulk()
334 fill_with_garbage(objects[i], size); in do_kmem_cache_size_bulk()
338 kmem_cache_free_bulk(c, num, objects); in do_kmem_cache_size_bulk()
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | namespace.rst | 17 The Linux ACPI subsystem converts ACPI namespace objects into a Linux
39 blocks that contain definitions of various objects, including ACPI
84 is a hierarchy of objects identified by names and paths.
196 objects for ACPI namespace objects representing devices, power resources
197 processors, thermal zones. Those objects are exported to user space via
235 The following rules apply when creating struct acpi_device objects on
261 struct acpi_device objects represented by the given row (xSDT means DSDT
269 is derived from the _HID/_CID identification objects present under
275 objects having bus_id of the "LNXxxxxx" form (pseudo devices), in
289 ACPI device (i.e. struct acpi_device) objects may be linked to other
[all …]
|
| /kernel/linux/linux-5.10/drivers/bus/fsl-mc/ |
| D | Kconfig | 15 DPAA2 objects (which are represented as Linux devices) and
16 binding objects to drivers.
|
| /kernel/linux/linux-5.10/mm/ |
| D | slub.c | 456 bitmap_zero(object_map, page->objects); in get_map()
530 if (object < base || object >= base + page->objects * s->size || in check_valid_pointer()
643 page, page->objects, page->inuse, page->freelist, page->flags); in print_page_info()
960 if (page->objects > maxobj) { in check_slab()
962 page->objects, maxobj); in check_slab()
965 if (page->inuse > page->objects) { in check_slab()
967 page->inuse, page->objects); in check_slab()
987 while (fp && nr <= page->objects) { in on_freelist()
998 page->inuse = page->objects; in on_freelist()
1013 if (page->objects != max_objects) { in on_freelist()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | drm-mm.rst | 99 GEM is data-agnostic. It manages abstract buffer objects without knowing
140 GEM splits creation of GEM objects and allocation of the memory that
143 GEM objects are represented by an instance of struct :c:type:`struct
145 extend GEM objects with private information and thus create a
172 often the case in embedded devices. Drivers can create GEM objects with
173 no shmfs backing (called private GEM objects) by initializing them with a call
175 private GEM objects must be managed by drivers.
180 All GEM objects are reference-counted by the GEM core. References can be
197 Communication between userspace and the kernel refers to GEM objects
206 associated GEM objects.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | directory-locking.rst | 10 When taking the i_rwsem on multiple non-directory objects, we
70 objects - A < B iff A is an ancestor of B.
84 (3) locks on non-directory objects are acquired only after locks on
85 directory objects, and are acquired in inode pointer order.
99 non-directory objects are not included in the set of contended locks.
110 Otherwise the set of contended objects would be infinite - each of them
117 would again have an infinite set of contended objects). But that
128 source), such loop would have to contain these objects and the rest of it
143 children", so if we are going to introduce hybrid objects we will need
|