| /linux/Documentation/core-api/ |
| H A 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/Documentation/arch/s390/ |
| H A D | mm.rst | 19 - The virtual memory regions are tracked or untracked by KASAN
58 | | KASAN tracked
96 | | KASAN tracked
|
| /linux/drivers/gpu/drm/i915/gvt/ |
| H A D | page_track.h | 40 bool tracked; member
|
| /linux/Documentation/accounting/ |
| H A 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
182 mounted, pressure stall information is also tracked for tasks grouped
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-devlink | 73 - 'not tracked'
81 'not tracked' means this device link does not track the status
|
| H A D | sysfs-class-intel_pmt-features | 63 - Maximum number of RMIDs tracked simultaneously.
|
| H A D | sysfs-ata | 33 port numbers are tracked based upon number of ports available on
|
| /linux/Documentation/driver-api/ |
| H A D | hw-recoverable-errors.rst | 33 - The tracked error data consists of per-error-type counts and timestamps of
|
| /linux/Documentation/admin-guide/ |
| H A 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/ |
| H A D | .gitignore | 9 # any tracked files which get ignored after the change.
|
| /linux/fs/btrfs/ |
| H A D | delayed-ref.h | 195 bool tracked; member
|
| /linux/Documentation/nvdimm/ |
| H A D | maintainer-entry-profile.rst | 7 architectures. The mailing list is tracked by patchwork here:
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | era.rst | 27 tracked by the target
|
| /linux/Documentation/locking/ |
| H A D | rt-mutex.rst | 46 The state of the rt-mutex is tracked via the owner field of the rt-mutex
|
| /linux/Documentation/ABI/stable/ |
| H A D | firewire-cdev | 59 node ID changes, are tracked by firewire-core. ABI users do not
|
| /linux/Documentation/block/ |
| H A D | stat.rst | 59 This counts flush requests executed by disk. Not tracked for partitions.
|
| /linux/Documentation/trace/ |
| H A D | hwlat_detector.rst | 29 (or an NMI, but those can be tracked).
|
| H A D | events-kmem.rst | 93 The individual nature of the events is so that pages can be tracked
|
| /linux/Documentation/userspace-api/netlink/ |
| H A D | intro-specs.rst | 65 tracked by git!) For instance the ``fou_nl.c`` kernel source contains::
|
| /linux/tools/arch/x86/kcpuid/ |
| H A D | cpuid.csv | 1001 0x80000020, 3, ecx, 0, bmec_local_reads , Local NUMA reads can be tracked
1002 0x80000020, 3, ecx, 1, bmec_remote_reads , Remote NUMA reads can be tracked
1003 0x80000020, 3, ecx, 2, bmec_local_nontemp_wr , Local NUMA non-temporal writes can be tracked
1004 0x80000020, 3, ecx, 3, bmec_remote_nontemp_wr , Remote NUMA non-temporal writes can be tracked
1005 0x80000020, 3, ecx, 4, bmec_local_slow_mem_rd , Local NUMA slow-memory reads can be tracked
1006 0x80000020, 3, ecx, 5, bmec_remote_slow_mem_rd, Remote NUMA slow-memory reads can be tracked
1007 0x80000020, 3, ecx, 6, bmec_all_dirty_victims , Dirty QoS victims to all types of memory can be tracked
|
| /linux/net/bluetooth/ |
| H A D | hci_conn.c | 3076 if (!track && !comp->tracked) { in hci_conn_tx_queue()
3086 comp->tracked++; in hci_conn_tx_queue()
3100 comp->tracked = 0; in hci_conn_tx_queue()
3114 if (comp->extra && (comp->tracked || skb_queue_empty(&comp->queue))) { in hci_conn_tx_dequeue()
3124 comp->tracked--; in hci_conn_tx_dequeue()
|
| /linux/Documentation/PCI/ |
| H A D | boot-interrupts.rst | 31 interrupt goes unhandled over time, they are tracked by the Linux kernel as
|
| /linux/Documentation/sound/cards/ |
| H A D | maya44.rst | 52 …ems to work only via JACK, not using ALSA directly or via OSS. This still needs to be tracked down.
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | idle_page_tracking.rst | 37 Only accesses to user memory pages are tracked. These are pages mapped to a
|
| /linux/Documentation/process/ |
| H A D | handling-regressions.rst | 96 you want to see tracked; that's important, as regzbot will later look out
334 The bot watches for replies to reports of tracked regressions. Additionally,
336 with "Closes:" tags; replies to such patch postings are tracked as well.
384 What kind of issues are supposed to be tracked by regzbot?
443 * Mark a regression as a duplicate of another one already tracked by regzbot::
|