tracks (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:tracks (Results 1 – 25 of 329) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...14

/linux/drivers/scsi/isci/
H A D	phy.h	238 * This PHY information field tracks the number of frames received. 243 * This PHY information field tracks the number of frames transmitted. 248 * This PHY information field tracks the number of DWORDs received. 253 * This PHY information field tracks the number of DWORDs transmitted. 258 * This PHY information field tracks the number of times DWORD 264 * This PHY information field tracks the number of received DWORDs with 270 * This PHY information field tracks the number of received frames with a 276 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT) 282 * This PHY information field tracks the number of DONE (ACK/NAK TIMEOUT) 288 * This PHY information field tracks the number of times the inactivity [all …]
/linux/drivers/cdrom/
H A D	cdrom.c	106 -- Check capability mask from low level driver when counting tracks as 977 static void cdrom_count_tracks(struct cdrom_device_info cdi, tracktype tracks) in cdrom_count_tracks() argument 982 tracks->data = 0; in cdrom_count_tracks() 983 tracks->audio = 0; in cdrom_count_tracks() 984 tracks->cdi = 0; in cdrom_count_tracks() 985 tracks->xa = 0; in cdrom_count_tracks() 986 tracks->error = 0; in cdrom_count_tracks() 990 tracks->error = CDS_NO_INFO; in cdrom_count_tracks() 994 /* Grab the TOC header so we can see how many tracks there are */ in cdrom_count_tracks() 998 tracks->error = CDS_NO_DISC; in cdrom_count_tracks() [all …]
/linux/include/drm/
H A D	drm_vblank.h	`97 * Additionally, this tracks the disable immediate value per crtc, just 109 * This structure tracks the vblank state for one CRTC. 189 * @inmodeset: Tracks whether the vblank is disabled due to a modeset. 190 * For legacy driver bit 2 additionally tracks whether an additional 233 * @enabled: Tracks the enabling state of the corresponding &drm_crtc to`
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-interconnect.json	8 "PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncore in each cycle. This is effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks all requests from any source port.", 18 "PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncore in each cycle. This is effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks only those requests that come from the port specified in the IRP_PmonFilter.OrderingQ register. This register allows one to select one specific queue. It is not possible to monitor multiple queues at a time.", 436 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of atomic transactions", 446 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of 'other' kinds of transactions.", 456 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of read prefetches.", 466 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks only read requests (not including read prefetches).", 476 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks only write requests. Each write request should have a prefetch, so there is no need to explicitly track these requests.", 486 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of write prefetches.",
H A D	uncore-io.json	373 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 383 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 393 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 403 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 413 …ates the occupancy of a given R2PCIe Ingress queue in each cycles. This tracks one of the three r… 533 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 543 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 553 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r…
/linux/fs/xfs/
H A D	xfs_log.h	`88 * logvec region by the opheader that tracks the payload. in xlog_finish_iovec() 98 * The opheader tracks aligned payload length, whilst the logvec tracks in xlog_finish_iovec()`
H A D	xfs_drain.h	`14 * Passive drain mechanism. This data structure tracks a count of some items 60 * Therefore, the intent count tracks entire lifetimes of deferred work items.`
/linux/include/linux/
H A D	if_tap.h	`38 /* This array tracks active taps. / 40 / This list tracks all taps (both enabled and disabled) */`
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-io.json	373 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 383 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 393 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 403 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 413 …ates the occupancy of a given R2PCIe Ingress queue in each cycles. This tracks one of the three r… 533 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 543 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 553 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r…
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-io.json	343 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 353 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 363 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 373 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 383 …ates the occupancy of a given R2PCIe Ingress queue in each cycles. This tracks one of the three r… 503 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 513 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 523 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r…
H A D	uncore-interconnect.json	8 "PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncore in each cycle. This is effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks all requests from any source port.", 18 "PublicDescription": "Accumulates the number of reads and writes that are outstanding in the uncore in each cycle. This is effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks only those requests that come from the port specified in the IRP_PmonFilter.OrderingQ register. This register allows one to select one specific queue. It is not possible to monitor multiple queues at a time.", 436 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of atomic transactions", 446 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of 'other' kinds of transactions.", 456 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of read prefetches.", 466 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks only read requests (not including read prefetches).", 476 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks only write requests. Each write request should have a prefetch, so there is no need to explicitly track these requests. For writes that are tickled and have to retry, the counter will be incremented for each retry.", 486 "PublicDescription": "Counts the number of Inbound transactions from the IRP to the Uncore. This can be filtered based on request type in addition to the source queue. Note the special filtering equation. We do OR-reduction on the request type. If the SOURCE bit is set, then we also do AND qualification based on the source portID.; Tracks the number of write prefetches.", 1555 "PublicDescription": "Counts the number of flits transmitted across the QPI Link. It includes filters for Idle, protocol, and Data Flits. Each flit is made up of 80 bits of information (in addition to some ECC data). In full-width (L0) mode, flits are made up of four fits, each of which contains 20 bits of data (along with some additional ECC data). In half-width (L0p) mode, the fits are only 10 bits, and therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for example, 8.0 GT/s), the transfers here refer to fits. Therefore, in L0, the system will transfer 1 flit at the rate of 1/4th the QPI speed. One can calculate the bandwidth of the link by taking: flits80b/time. Note that this is not the same as data bandwidth. For example, when we are transferring a 64B cacheline across QPI, we will break it into 9 flits -- 1 with header information and 8 with 64 bits of actual data and an additional 16 bits of other information. To calculate data bandwidth, one should therefore do: data flits 8B / time (for L0) or 4B instead of 8B for L0p.; Number of non-NULL non-data flits transmitted across QPI. This basically tracks the protocol overhead on the QPI link. One can get a good picture of the QPI-link characteristics by evaluating the protocol flits, data flits, and idle/null flits. This includes the header flits for data packets.", 1726 "PublicDescription": "Occupancy event that tracks th [all...]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-io.json	246 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 256 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 266 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 306 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 316 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 326 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r…
/linux/arch/x86/kernel/cpu/
H A D	perfctr-watchdog.c	`35 * perfctr_nmi_owner tracks the ownership of the perfctr registers: 36 * evtsel_nmi_owner tracks the ownership of the event selection`
/linux/include/xen/interface/hvm/
H A D	params.h	`68 * As above, missed interrupts are delivered, but guest time always tracks 77 * Guest time always tracks wallclock (i.e., real) time.`
/linux/Documentation/admin-guide/hw-vuln/
H A D	vmscape.rst	`38 Kernel tracks when a CPU has run a potentially malicious guest and issues an 85 Conditional IBPB mitigation is enabled. The kernel tracks when a CPU has`
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-io.json	446 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 456 …"Counts the number of cycles when the R2PCIe Ingress is not empty. This tracks one of the three r… 466 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 476 …ption": "Counts the number of allocations into the R2PCIe Ingress. This tracks one of the three r… 486 …ates the occupancy of a given R2PCIe Ingress queue in each cycles. This tracks one of the three r… 526 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 536 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r… 546 … "Counts the number of cycles when the R2PCIe Egress is not empty. This tracks one of the three r…
H A D	uncore-interconnect.json	28 …released. Note that a single tickle can result in multiple decrements.; Tracks only those request… 38 …released. Note that a single tickle can result in multiple decrements.; Tracks all requests from … 48 …en a write request is issued, and decrements when the data is returned.; Tracks all requests from … 58 …en a write request is issued, and decrements when the data is returned.; Tracks only those request… 68 …hen a read request is issued, and decrements when the data is returned.; Tracks all requests from … 78 …hen a read request is issued, and decrements when the data is returned.; Tracks only those request… 88 …s effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks all requests from … 98 …s effectively the sum of the READ_OCCUPANCY and WRITE_OCCUPANCY events.; Tracks only those request… 108 …/prefetch is issued, and decrements the data is returned to the uncore.; Tracks all requests from … 118 …/prefetch is issued, and decrements the data is returned to the uncore.; Tracks only those request… [all …]
/linux/arch/s390/include/uapi/asm/
H A D	vtoc.h	`77 __u16 DS4DSTRK; /* number of tracks in a logical cylinder / 131 __u16 DS4NOATK; / number of remaining alternate tracks / 161 __u8 ft; / number of remaining free tracks */`
/linux/tools/perf/pmu-events/arch/x86/sapphirerapids/
H A D	uncore-power.json	`182 …"PublicDescription": "Number of cores in C0 : This is an occupancy event that tracks the number of… 192 …"PublicDescription": "Number of cores in C3 : This is an occupancy event that tracks the number of… 201 …"PublicDescription": "Number of cores in C6 : This is an occupancy event that tracks the number of…`
/linux/tools/perf/pmu-events/arch/x86/emeraldrapids/
H A D	uncore-power.json	`182 …"PublicDescription": "Number of cores in C0 : This is an occupancy event that tracks the number of… 192 …"PublicDescription": "Number of cores in C3 : This is an occupancy event that tracks the number of… 201 …"PublicDescription": "Number of cores in C6 : This is an occupancy event that tracks the number of…`
/linux/Documentation/cdrom/
H A D	cdrom-standard.rst	498 reading audio tracks as data, I believe this is because of protection 499 of copyrights of artists. Moreover, I think that if audio-tracks are 708 set, that it contains tracks of type `data mode 1`. Only if all tests 931 also very common for CDs to have some tracks with data, and some 932 tracks with audio. Because this is an existing interface, rather 936 follows: If the CD in question has audio tracks on it, and it has 937 absolutely no CD-I, XA, or data tracks on it, it will be reported 938 as CDS_AUDIO. If it has both audio and data tracks, it will 939 return CDS_MIXED. If there are no audio tracks on the disc, and 940 if the CD in question has any CD-I tracks on it, it will be [all …]
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-power.json	`191 …Number of cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of core… 202 …ion": "Number of cores in C-State : C3 : This is an occupancy event that tracks the number of core… 213 …Number of cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of core…`
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-power.json	`184 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c… 195 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c… 206 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c…`
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-power.json	`184 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c… 195 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c… 206 …"PublicDescription": "This is an occupancy event that tracks the number of cores that are in the c…`
/linux/tools/perf/pmu-events/arch/x86/icelakex/
H A D	uncore-power.json	`192 …Number of cores in C-State : C0 and C1 : This is an occupancy event that tracks the number of core… 203 …ion": "Number of cores in C-State : C3 : This is an occupancy event that tracks the number of core… 214 …Number of cores in C-State : C6 and C7 : This is an occupancy event that tracks the number of core…`

12 3 4 5 6 7 8 9 10 >>...14