| /linux/drivers/gpu/drm/i915/gem/ |
| A D | i915_gem_region.c | 16 mutex_lock(&mem->objects.lock); in i915_gem_object_init_memory_region()
17 list_add(&obj->mm.region_link, &mem->objects.list); in i915_gem_object_init_memory_region()
18 mutex_unlock(&mem->objects.lock); in i915_gem_object_init_memory_region()
25 mutex_lock(&mem->objects.lock); in i915_gem_object_release_memory_region()
27 mutex_unlock(&mem->objects.lock); in i915_gem_object_release_memory_region()
113 mutex_lock(&mr->objects.lock); in i915_gem_process_region()
117 obj = list_first_entry_or_null(&mr->objects.list, typeof(*obj), in i915_gem_process_region()
131 mutex_unlock(&mr->objects.lock); in i915_gem_process_region()
144 mutex_lock(&mr->objects.lock); in i915_gem_process_region()
148 list_splice_tail(&still_in_list, &mr->objects.list); in i915_gem_process_region()
[all …]
|
| /linux/drivers/gpu/drm/i915/selftests/ |
| A D | i915_gem_evict.c | 38 struct list_head *objects) in quirk_add() argument
43 list_add(&obj->st_link, objects); in quirk_add()
69 quirk_add(obj, objects); in populate_ggtt()
109 LIST_HEAD(objects); in igt_evict_something()
157 LIST_HEAD(objects); in igt_overcommit()
174 quirk_add(obj, &objects); in igt_overcommit()
196 LIST_HEAD(objects); in igt_evict_for_vma()
251 LIST_HEAD(objects); in igt_evict_for_cache_color()
269 quirk_add(obj, &objects); in igt_evict_for_cache_color()
285 quirk_add(obj, &objects); in igt_evict_for_cache_color()
[all …]
|
| A D | intel_memory_region.c | 31 struct list_head *objects) in close_objects() argument
60 LIST_HEAD(objects); in igt_mock_fill()
99 close_objects(mem, &objects); in igt_mock_fill()
106 struct list_head *objects, in igt_object_create() argument
164 LIST_HEAD(objects); in igt_mock_reserve()
227 close_objects(mem, &objects); in igt_mock_reserve()
239 LIST_HEAD(objects); in igt_mock_contiguous()
316 list = &objects; in igt_mock_contiguous()
362 close_objects(mem, &objects); in igt_mock_contiguous()
374 LIST_HEAD(objects); in igt_mock_splintered_region()
[all …]
|
| A D | i915_gem_gtt.c | 406 LIST_HEAD(objects); in fill_hole()
432 list_add(&obj->st_link, &objects); in fill_hole()
595 close_object_list(&objects, vm); in fill_hole()
602 close_object_list(&objects, vm); in fill_hole()
871 LIST_HEAD(objects); in __shrink_hole()
887 list_add(&obj->st_link, &objects); in __shrink_hole()
934 close_object_list(&objects, vm); in __shrink_hole()
1344 LIST_HEAD(objects); in igt_gtt_reserve()
1372 list_add(&obj->st_link, &objects); in igt_gtt_reserve()
1424 list_add(&obj->st_link, &objects); in igt_gtt_reserve()
[all …]
|
| /linux/Documentation/networking/device_drivers/ethernet/freescale/dpaa2/ |
| A D | overview.rst | 29 which DPAA2 software drivers use to operate on DPAA2 objects.
71 DPIO objects.
84 types of DPAA2 objects. In the example diagram below there
85 are 8 objects of 5 types (DPMCP, DPIO, DPBP, DPNI, and DPMAC)
129 DPRCs can be defined statically and populated with objects
144 The diagram below shows the objects needed for a simple
225 objects.
233 Some objects have explicit relationships that must
262 All interrupts generated by DPAA2 objects are message
268 In the case of DPAA2 devices/objects, all objects in the
[all …]
|
| A 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.
|
| /linux/drivers/gpu/drm/ |
| A D | drm_lease.c | 345 struct drm_mode_object **objects, in validate_lease() argument
381 struct drm_mode_object **objects; in fill_object_idr() local
388 if (!objects) in fill_object_idr()
394 objects[o] = drm_mode_object_find(dev, lessor_priv, in fill_object_idr()
397 if (!objects[o]) { in fill_object_idr()
402 if (!drm_mode_object_lease_required(objects[o]->type)) { in fill_object_idr()
418 struct drm_mode_object *obj = objects[o]; in fill_object_idr()
419 u32 object_id = objects[o]->id; in fill_object_idr()
460 if (objects[o]) in fill_object_idr()
461 drm_mode_object_put(objects[o]); in fill_object_idr()
[all …]
|
| /linux/Documentation/filesystems/caching/ |
| A D | fscache.rst | 452 /proc/fs/fscache/objects
470 CHLDN Number of child objects of this object
510 C Show objects that have a cookie
511 c Show objects that don't have a cookie
512 B Show objects that are busy
513 b Show objects that aren't busy
514 W Show objects that have pending writes
515 w Show objects that don't have pending writes
516 R Show objects that have outstanding reads
518 S Show objects that have work queued
[all …]
|
| A 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
89 pointers to the cookies. The cookies themselves and any objects attached to
112 and that update the state of objects.
[all …]
|
| /linux/Documentation/dev-tools/ |
| A 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
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
123 'clear' command to clear all reported unreferenced objects from the
138 Freeing kmemleak internal objects
183 The false negatives are real memory leaks (orphan objects) but not
[all …]
|
| /linux/scripts/kconfig/ |
| A 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}};
|
| /linux/Documentation/core-api/ |
| A 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.
147 or destroyed objects.
156 prevent the usage of invalid objects, which are still available in
[all …]
|
| /linux/tools/build/Documentation/ |
| A 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
|
| /linux/Documentation/driver-api/acpi/ |
| A 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
|
| /linux/tools/vm/ |
| A D | slabinfo.c | 633 s->name, s->objects, in slabcache()
704 if (s->objects > 0) in slab_empty()
841 if (!s->slabs || !s->objects) in totals()
847 used = s->objects * s->object_size; in totals()
856 / s->objects; in totals()
873 if (s->objects < min_objects) in totals()
874 min_objects = s->objects; in totals()
898 if (s->objects > max_objects) in totals()
899 max_objects = s->objects; in totals()
916 total_objects += s->objects; in totals()
[all …]
|
| /linux/tools/perf/Documentation/ |
| A 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:
|
| /linux/Documentation/networking/devlink/ |
| A D | netdevsim.rst | 60 Rate objects
63 The ``netdevsim`` driver supports rate objects management, which includes:
65 - registerging/unregistering leaf rate objects per VF devlink port;
66 - creation/deletion node rate objects;
78 Same parameters are exposed for leaf objects in corresponding ports directories.
|
| /linux/drivers/bus/fsl-mc/ |
| A D | Kconfig | 15 DPAA2 objects (which are represented as Linux devices) and
16 binding objects to drivers.
23 configuring DPAA2 objects exported by the Management Complex.
|
| /linux/Documentation/admin-guide/sysctl/ |
| A 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
|
| /linux/Documentation/ABI/testing/ |
| A 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
201 slabs (not objects) are freed by rcu.
287 objects are aligned on cachelines.
309 What: /sys/kernel/slab/<cache>/objects
315 The objects file is read-only and displays how many objects are
335 objects may be allocated from a single slab of the order
438 with the fewest available objects are used first.
480 objects a cache has and from which nodes they are from.
[all …]
|
| /linux/lib/ |
| A 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()
|
| /linux/Documentation/vm/ |
| A 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
|
| /linux/Documentation/firmware-guide/acpi/ |
| A 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 …]
|
| /linux/Documentation/gpu/ |
| A D | drm-mm.rst | 96 GEM is data-agnostic. It manages abstract buffer objects without knowing
137 GEM splits creation of GEM objects and allocation of the memory that
140 GEM objects are represented by an instance of struct :c:type:`struct
142 extend GEM objects with private information and thus create a
172 private GEM objects must be managed by drivers.
194 Communication between userspace and the kernel refers to GEM objects
203 associated GEM objects.
213 avoid leaking GEM objects, drivers must make sure they drop the
223 globally. Names can't be used directly to refer to objects in the DRM
249 co-exist to map GEM objects to userspace. The first method uses a
[all …]
|
| /linux/Documentation/filesystems/ |
| A 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
|