not\-used (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:not +full:- +full:used (Results 1 – 25 of 1100) sorted by relevance

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

/linux/include/linux/firmware/intel/
H A D	stratix10-smc.h	1 /* SPDX-License-Identifier: GPL-2.0 / 3 Copyright (C) 2017-2018, Intel Corporation 9 #include <linux/arm-smccc.h> 13 * This file defines the Secure Monitor Call (SMC) message protocol used for 19 * An ARM SMC instruction takes a function identifier and up to 6 64-bit 20 * register values as arguments, and can return up to 4 64-bit register 31 * STD call starts a operation which can be preempted by a non-secure 35 * a0..a7 is used as register names in the descriptions below, on arm32 81 * Sync call used by service driver at EL1 to request the FPGA in EL3 to 88 * a2-7: not used. [all …]
/linux/drivers/net/ipa/
H A D	ipa_reg.h	1 /* SPDX-License-Identifier: GPL-2.0 / 3 / Copyright (c) 2012-2018, The Linux Foundation. All rights reserved. 4 * Copyright (C) 2018-2024 Linaro Ltd. 18 * IPA registers are located within the "ipa-reg" address space defined by 35 * (for parameterized registers) a non-zero stride value. Not all versions 44 * used to access register fields; both take an ipa_reg structure as 48 * reg_decode(). In addition, for single-bit fields, reg_bit() 49 * can be used to either encode the bit value, or to generate a mask 50 * used to extract the bit value. 53 /* enum ipa_reg_id - IPA register IDs */ [all …]
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-io.json	8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 17 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 27 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 37 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 47 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 57 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 67 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 77 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 87 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 97 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… [all …]
H A D	uncore-memory.json	12 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM WR_CAS (w/ and w/out auto-pre)", 30 … "BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; All DRAM RD_CAS (w/ and w/out auto-pre)", 57 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Read… 66 …"BriefDescription": "DRAM RD_CAS and WR_CAS Commands.; DRAM WR_CAS (w/ and w/out auto-pre) in Writ… 79 "PublicDescription": "Uncore Fixed Counter - uclks", 126 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 136 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 146 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 156 …ected by a filter) on the given channel. Major modea are channel-wide, and not a per-rank (or di… 175 …e in PPD mode. If IBT=off is enabled, then this can be used to count those cycles. If it is not … [all …]
H A D	uncore-interconnect.json	28 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 38 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 48 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 58 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 68 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 78 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 108 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 118 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 160 … This queue is where the IRP receives data from R2PCIe (the ring). It is used for data returns fr… 164 "BriefDescription": "BL Ingress Occupancy - DRS", [all …]
/linux/Documentation/arch/arm64/
H A D	acpi_object_usage.rst	8 If a section number is used, it refers to a section number in the ACPI 9 specification where the object is defined. If "Signature Reserved" is used, 16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT 18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT 20 - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, 24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT, 41 This table describes a non-maskable event, that is used by the platform 62 Microsoft only table, will not be supported. 68 Optional, not currently supported, with no real use-case for an 82 Optional, not currently supported, and not recommended until such [all …]
/linux/tools/perf/pmu-events/arch/x86/ivytown/
H A D	uncore-io.json	8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 17 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 27 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 37 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 47 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 57 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 67 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 77 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 87 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 97 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
H A D	uncore-interconnect.json	18 … had an address match with another request in the write cache.; When it is not possible to merge t… 28 …not yet returned their data to the uncore. These writes are generally queued up in the switch try… 38 …": "Accumulates the number of writes that have acquired ownership but have not yet returned their … 48 …ing in the uncore trying to acquire ownership in each cycle. This can be used with the write tran… 58 …used with the write transaction count to calculate the average write latency in the uncore. The o… 68 …r of reads that are outstanding in the uncore in each cycle. This can be used with the read trans… 78 …used with the read transaction count to calculate the average read latency in the uncore. The occ… 98 …Q register. This register allows one to select one specific queue. It is not possible to monitor… 108 …efetches) that are outstanding in the uncore in each cycle. This can be used with the transactio… 118 …used with the transaction count event to calculate the average latency in the uncore. The occupan… [all …]
/linux/tools/perf/pmu-events/arch/x86/broadwellx/
H A D	uncore-io.json	8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
H A D	uncore-interconnect.json	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.", 111 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 116 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary", 121 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 126 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Read Transactions as Secondary", 131 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 136 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Write Transactions as Secondary", 141 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", 146 "PublicDescription": "Counts Timeouts - Set 0 : Fastpath Rejects", 151 "BriefDescription": "Misc Events - Se [all...]
/linux/tools/perf/pmu-events/arch/x86/broadwellde/
H A D	uncore-io.json	8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
/linux/Documentation/scsi/
H A D	st.rst	1 .. SPDX-License-Identifier: GPL-2.0 17 The driver is generic, i.e., it does not contain any code tailored 23 flexible method and applicable to single-user workstations. However, 32 drive performs auto-detection of the tape format well (like some 33 QIC-drives). The result is that any tape can be read, writing can be 34 continued using existing format, and the default format is used if 37 does not perform auto-detection well enough and there is a single 39 used only in variable block mode (I don't know if this is sensible 40 or not :-). 51 the configuration of mode 0 is used to provide a starting point for [all …]
/linux/tools/perf/pmu-events/arch/x86/haswellx/
H A D	uncore-io.json	8 …. However, because the R2PCIe is close to the Ubox, they generally should not diverge by more tha… 53 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 63 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 73 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 83 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 93 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 103 … or non-coherent bypass messages are used to transmit data without coherency (and are common). NC… 113 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 123 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… 133 …he AD ring is being used at this ring stop. This includes when packets are passing by and when pa… [all …]
H A D	uncore-interconnect.json	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.", 111 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 116 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Atomic Transactions as Secondary", 121 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 126 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Read Transactions as Secondary", 131 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 136 "PublicDescription": "Counts Timeouts - Set 0 : Cache Inserts of Write Transactions as Secondary", 141 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", 146 "PublicDescription": "Counts Timeouts - Set 0 : Fastpath Rejects", 151 "BriefDescription": "Misc Events - Se [all...]
/linux/drivers/net/ethernet/aquantia/atlantic/macsec/
H A D	macsec_struct.h	1 /* SPDX-License-Identifier: GPL-2.0-only / 13 /! This is used to store the 48 bit value used to compare SA, DA or 17 /! This is used to store the 16 bit ethertype value used for 21 /! The match mask is per-nibble. 0 means don't care, i.e. every value 26 /! 0: No compare, i.e. This entry is not used 52 /! The 8 bit value used to compare with extracted value for byte 3. / 54 /! The 8 bit value used to compare with extracted value for byte 2. / 56 /! The 8 bit value used to compare with extracted value for byte 1. / 58 /! The 8 bit value used to compare with extracted value for byte 0. / 60 /! The 8 bit TCI field used to compare with extracted value. */ [all …]
/linux/Documentation/arch/arm/
H A D	setup.rst	6 structure, otherwise known as 'struct param_struct' which is used 9 This structure is used to pass initialisation parameters from the 12 should not be referenced outside of arch/arm/kernel/setup.c:setup_arch(). 26 If the system contains separate VRAM, this value should not 30 This is now obsolete, and should not be used. 47 or VGA console character size. They should not be used for any other 56 is otherwise unused. (should not be used for other console types, and 57 should not be used for other purposes). 61 based machines. May be used differently by different architectures. 64 Default sound setting on Acorn machines. May be used differently by [all …]
/linux/include/uapi/mtd/
H A D	ubi-user.h	1 /* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note / 16 along with this program; if not, write to the Free Software 17 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA 33 * &struct ubi_attach_req object - UBI will attach the MTD device specified in 54 * device should be used. A pointer to the 32-bit volume ID hast to be passed 57 * UBI volume re-size 60 * To re-size a volume, the %UBI_IOCRSVOL ioctl command of the UBI character 61 * device should be used. A &struct ubi_rsvol_req object has to be properly 64 * UBI volumes re-name 67 * To re-name several volumes atomically at one go, the %UBI_IOCRNVOL command [all …]
/linux/rust/
H A D	compiler_builtins.rs	1 // SPDX-License-Identifier: GPL-2.0 5 //! Rust provides [`compiler_builtins`] as a port of LLVM's [`compiler-rt`]. 6 //! Since we do not need the vast majority of them, we avoid the dependency 9 //! At the moment, some builtins are required that should not be. For instance, 10 //! [`core`] has 128-bit integers functionality which we should not be compiling 12 //! the parts we do not need. For the moment, we define them to [`panic!`] at 16 //! In any case, all these symbols are weakened to ensure we do not override 19 //! [`compiler_builtins`]: https://github.com/rust-lang/compiler-builtins 20 //! [`compiler-rt`]: https://compiler-rt.llvm.org/ 40 define_panicking_intrinsics!("`f32` should not be used", { [all …]
/linux/include/uapi/linux/
H A D	nl80211.h	`6 * Copyright 2006-2010 Johannes Berg <johannes@sipsolutions.net> 13 * Copyright 2015-2017 Intel Deutschland GmbH 14 * Copyright (C) 2018-2025 Intel Corporation 32 * be careful not to break things - i.e. don't move anything around or so 74 * - a setup station entry is added, not yet authorized, without any rate 76 * - when the TDLS setup is done, a single NL80211_CMD_SET_STATION is valid 79 * - %NL80211_TDLS_ENABLE_LINK is then used [all...]`
/linux/sound/pci/emu10k1/
H A D	p17v.h	`1 /* SPDX-License-Identifier: GPL-2.0-or-later / 3 Copyright (c) by James Courtier-Dutton <James@superbug.demon.co.uk> 8 /* Audigy2Value Tina (P17V) pointer-offset register set, / 12 / 00 - 07: Not used / 16 / 09 - 12: Not used / 20 / 14 - 17: Not used / 24 / 1b - 1f: Not used / 25 / 20 - 2f: Not used / 26 / 30 - 3b: Not used / 62 / FIXME: Not tested yet. */ [all …]`
/linux/tools/perf/pmu-events/arch/x86/snowridgex/
H A D	uncore-memory.json	8 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu… 19 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.… 61 …"PublicDescription": "Counts the total number of DRAM Read CAS commands, w/ and w/o auto-pre, issu… 66 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM RD_CAS commands w/auto-pre", 72 …-pre : DRAM RD_CAS and WR_CAS Commands : Counts the total number or DRAM Read CAS commands issued … 88 "BriefDescription": "All DRAM read CAS commands issued (does not include underfills)", 94 …s as well as those with implicit Precharge. We do not filter based on major mode, as RD_CAS is n… 115 … "Counts the total number of DRAM Write CAS commands issued, w/ and w/o auto-pre, on this channel.… 120 "BriefDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre", 126 …"PublicDescription": "DRAM RD_CAS and WR_CAS Commands. : DRAM WR_CAS commands w/o auto-pre : DRAM … [all …]
/linux/tools/perf/pmu-events/arch/x86/cascadelakex/
H A D	uncore-interconnect.json	104 "PublicDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of writing a full cacheline to coherent memory, without a RFO. PCIITOM is a speculative Invalidate to Modified command that requests ownership of the cacheline and does not move data from the mesh to IRP cache.", 144 "PublicDescription": "Inbound read requests to coherent memory, received by the IRP and inserted into the Fire and Forget queue (FAF), a queue used for processing inbound reads in the IRP.", 153 "PublicDescription": "Occupancy of the IRP Fire and Forget (FAF) queue, a queue used for processing inbound reads in the IRP.", 157 "BriefDescription": "FAF allocation -- sent to ADQ", 186 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 196 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 206 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 216 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", 226 "BriefDescription": "Misc Events - Se [all...]
/linux/tools/perf/pmu-events/arch/x86/skylakex/
H A D	uncore-interconnect.json	104 "PublicDescription": "PCIITOM request issued by the IRP unit to the mesh with the intention of writing a full cacheline to coherent memory, without a RFO. PCIITOM is a speculative Invalidate to Modified command that requests ownership of the cacheline and does not move data from the mesh to IRP cache.", 144 "PublicDescription": "Inbound read requests to coherent memory, received by the IRP and inserted into the Fire and Forget queue (FAF), a queue used for processing inbound reads in the IRP.", 153 "PublicDescription": "Occupancy of the IRP Fire and Forget (FAF) queue, a queue used for processing inbound reads in the IRP.", 157 "BriefDescription": "FAF allocation -- sent to ADQ", 186 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Atomic Transactions as Secondary", 196 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Read Transactions as Secondary", 206 "BriefDescription": "Misc Events - Set 0; Cache Inserts of Write Transactions as Secondary", 216 "BriefDescription": "Misc Events - Set 0; Fastpath Rejects", 226 "BriefDescription": "Misc Events - Se [all...]
/linux/Documentation/admin-guide/device-mapper/
H A D	dm-integrity.rst	2 dm-integrity 5 The dm-integrity target emulates a block device that has additional 6 per-sector tags that can be used for storing integrity information. 9 writing the sector and the integrity tag must be atomic - i.e. in case of 12 To guarantee write atomicity, the dm-integrity target uses journal, it 16 The dm-integrity target can be used with the dm-crypt target - in this 17 situation the dm-crypt target creates the integrity data and passes them 18 to the dm-integrity target via bio_integrity_payload attached to the bio. 19 In this mode, the dm-crypt and dm-integrity targets provide authenticated 20 disk encryption - if the attacker modifies the encrypted device, an I/O [all …]
/linux/include/linux/
H A D	dlm.h	1 /* SPDX-License-Identifier: GPL-2.0-only / 5 * Copyright (C) Sistina Software, Inc. 1997-2003 All rights reserved. 6 ** Copyright (C) 2004-2011 Red Hat, Inc. All rights reserved. 46 * name: lockspace name, null terminated, up to DLM_LOCKSPACE_LEN (not 49 * cluster: cluster name, null terminated, up to DLM_LOCKSPACE_LEN (not 51 * is not used. When set, dlm_new_lockspace() returns -EBADR if cluster 52 * is not equal to the dlm cluster name. 56 * The dlm should not use a resource directory, but statically assign 58 * used to select the directory node. Must be the same on all nodes. 60 * dlm_new_lockspace() should return -EEXIST if the lockspace exists. [all …]

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