Searched refs:tracked (Results 1 – 25 of 67) sorted by relevance
123
| /linux-6.1.9/drivers/gpu/drm/i915/gvt/ |
| D | page_track.c | 89 if (track->tracked) in intel_vgpu_unregister_page_track()
112 if (track->tracked) in intel_vgpu_enable_page_track()
118 track->tracked = true; in intel_vgpu_enable_page_track()
139 if (!track->tracked) in intel_vgpu_disable_page_track()
145 track->tracked = false; in intel_vgpu_disable_page_track()
|
| D | cfg_space.c | 135 if (map != vgpu->cfg_space.bar[INTEL_GVT_PCI_BAR_APERTURE].tracked) in map_aperture()
136 vgpu->cfg_space.bar[INTEL_GVT_PCI_BAR_APERTURE].tracked = map; in map_aperture()
141 if (trap != vgpu->cfg_space.bar[INTEL_GVT_PCI_BAR_GTTMMIO].tracked) in trap_gttmmio()
142 vgpu->cfg_space.bar[INTEL_GVT_PCI_BAR_GTTMMIO].tracked = trap; in trap_gttmmio()
|
| D | page_track.h | 40 bool tracked; member
|
| D | gvt.h | 101 bool tracked; member
|
| /linux-6.1.9/Documentation/core-api/ |
| D | debug-objects.rst | 73 When the real object is already tracked by debugobjects it is checked,
82 When the real object is not yet tracked by debugobjects, debugobjects
96 When the real object is already tracked by debugobjects it is checked,
105 When the real object is not yet tracked by debugobjects debugobjects
120 When the real object is already tracked by debugobjects it is checked,
128 When the real object is not yet tracked by debugobjects then the
145 When the real object is tracked by debugobjects it is checked, whether
160 When the real object is tracked by debugobjects it is checked, whether
176 When the real object is tracked by debugobjects it is checked, whether
193 When the real object is not tracked by debugobjects, it calls
[all …]
|
| /linux-6.1.9/Documentation/accounting/ |
| D | psi.rst | 55 stall state is tracked separately and exported in the "full" averages.
60 The ratios (in %) are tracked as recent trends over ten, sixty, and
63 (in us) is tracked and exported as well, to allow detection of latency
178 mounted, pressure stall information is also tracked for tasks grouped
|
| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-class-devlink | 73 - 'not tracked'
81 'not tracked' means this device link does not track the status
|
| D | sysfs-ata | 33 port numbers are tracked based upon number of ports available on
|
| /linux-6.1.9/ |
| D | .gitignore | 9 # any tracked files which get ignored after the change.
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | reporting-regressions.rst | 128 regressions becomes mentioned `on the list of tracked and unresolved Linux
215 get it tracked immediately.
369 Why and how are Linux kernel regressions tracked using a bot?
378 Regzbot works by watching for replies to reports of tracked regressions.
380 reports with "Link:" tags; replies to such patch postings are tracked as well.
389 What kind of issues are supposed to be tracked by regzbot?
397 How to change aspects of a tracked regression?
|
| /linux-6.1.9/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 7 architectures. The mailing list is tracked by patchwork here:
|
| /linux-6.1.9/Documentation/admin-guide/device-mapper/ |
| D | era.rst | 27 tracked by the target
|
| /linux-6.1.9/Documentation/locking/ |
| D | rt-mutex.rst | 46 The state of the rt-mutex is tracked via the owner field of the rt-mutex
|
| /linux-6.1.9/Documentation/ABI/stable/ |
| D | firewire-cdev | 59 node ID changes, are tracked by firewire-core. ABI users do not
|
| /linux-6.1.9/Documentation/block/ |
| D | stat.rst | 59 This counts flush requests executed by disk. Not tracked for partitions.
|
| /linux-6.1.9/Documentation/trace/ |
| D | hwlat_detector.rst | 29 (or an NMI, but those can be tracked).
|
| D | events-kmem.rst | 93 The individual nature of the events is so that pages can be tracked
|
| /linux-6.1.9/Documentation/dev-tools/ |
| D | kmemleak.rst | 87 The corresponding freeing function calls are tracked and the pointers
224 Page allocations and ioremap are not tracked.
|
| /linux-6.1.9/Documentation/scheduler/ |
| D | sched-design-CFS.rst | 33 In CFS the virtual runtime is expressed and tracked via the per-task
63 runqueue. The total amount of work done by the system is tracked using
|
| /linux-6.1.9/Documentation/RCU/ |
| D | lockdep.rst | 9 critical section. Each flavor of RCU is tracked separately (but note
|
| /linux-6.1.9/Documentation/bpf/ |
| D | verifier.rst | 88 Pointer register spill/fill is tracked as well, since four (R6-R9)
151 arithmetic), and this is tracked in two parts: the 'fixed offset' and 'variable
192 As well as range-checking, the tracked information is also used for enforcing
|
| /linux-6.1.9/Documentation/process/ |
| D | handling-regressions.rst | 93 you want to see tracked; that's important, as regzbot will later look out
283 The bot watches for replies to reports of tracked regressions. Additionally,
285 with "Link:" tags; replies to such patch postings are tracked as well.
334 What kind of issues are supposed to be tracked by regzbot?
393 * Mark a regression as a duplicate of another one already tracked by regzbot::
|
| /linux-6.1.9/Documentation/mm/ |
| D | balance.rst | 100 for a zone can be tracked and fed into the balancing scheme (jalvo@mbay.net)
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 39 Only accesses to user memory pages are tracked. These are pages mapped to a
|
| /linux-6.1.9/Documentation/PCI/ |
| D | boot-interrupts.rst | 31 interrupt goes unhandled over time, they are tracked by the Linux kernel as
|
123