attributes (full) in projects: linux-5.10

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:attributes (Results 1 – 25 of 1905) sorted by relevance

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

/linux-5.10/include/linux/
D	compiler_attributes.h	6 * The attributes in this file are unconditionally defined and they directly 11 * Any other "attributes" (i.e. those that depend on a configuration option, 12 * on a compiler, on an architecture, on plugins, on other attributes...) 43 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alias-function-a… 48 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-aligned-function… 49 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Type-Attributes.html#index-aligned-type-attribu… 50 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#index-aligned-variable… 61 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-always_005finlin… 79 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-assume_005falign… 89 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-cold-function-at… [all …]
/linux-5.10/net/netlabel/
D	netlabel_mgmt.h	`28 * Required attributes: 33 * If IPv4 is specified the following attributes are required: 38 * If IPv6 is specified the following attributes are required: 43 * If using NETLBL_NLTYPE_CIPSOV4 the following attributes are required: 47 * If using NETLBL_NLTYPE_UNLABELED no other attributes are required, 56 * Required attributes: 66 * Required attributes: 82 * attributes are required: 87 * attributes are required. 93 * Required attributes: [all …]`
D	netlabel_unlabeled.h	28 * Required attributes: 33 * If IPv4 is specified the following attributes are required: 38 * If IPv6 is specified the following attributes are required: 47 * Required attributes: 51 * If IPv4 is specified the following attributes are required: 56 * If IPv6 is specified the following attributes are required: 67 * Required attributes: 72 * If IPv4 is specified the following attributes are required: 77 * If IPv6 is specified the following attributes are required: 90 * If IPv4 is specified the following attributes are required: [all …]
D	netlabel_cipso_v4.h	`27 * Required attributes: 33 * If using CIPSO_V4_MAP_TRANS the following attributes are required: 38 * If using CIPSO_V4_MAP_PASS or CIPSO_V4_MAP_LOCAL no additional attributes 45 * Required attributes: 53 * Required attributes: 60 * Required attributes: 65 * If using CIPSO_V4_MAP_TRANS the following attributes are required: 70 * If using CIPSO_V4_MAP_PASS or CIPSO_V4_MAP_LOCAL no additional attributes 79 * Required attributes: 96 /* NetLabel CIPSOv4 attributes */`
D	netlabel_calipso.h	`28 * Required attributes: 33 * If using CALIPSO_MAP_PASS no additional attributes are required. 39 * Required attributes: 47 * Required attributes: 54 * Required attributes: 58 * If using CALIPSO_MAP_PASS no additional attributes are required. 66 * Required attributes: 83 /* NetLabel CALIPSO attributes */`
/linux-5.10/fs/efivarfs/
D	file.c	20 u32 attributes; in efivarfs_file_write() local 22 unsigned long datasize = count - sizeof(attributes); in efivarfs_file_write() 26 if (count < sizeof(attributes)) in efivarfs_file_write() 29 if (copy_from_user(&attributes, userbuf, sizeof(attributes))) in efivarfs_file_write() 32 if (attributes & ~(EFI_VARIABLE_MASK)) in efivarfs_file_write() 35 data = memdup_user(userbuf + sizeof(attributes), datasize); in efivarfs_file_write() 39 bytes = efivar_entry_set_get_size(var, attributes, &datasize, in efivarfs_file_write() 53 i_size_write(inode, datasize + sizeof(attributes)); in efivarfs_file_write() 71 u32 attributes; in efivarfs_file_read() local 90 data = kmalloc(datasize + sizeof(attributes), GFP_KERNEL); in efivarfs_file_read() [all …]
/linux-5.10/drivers/firmware/efi/
D	efivars.c	39 __u32 Attributes; member 91 ret = efivar_entry_get(entry, &var->Attributes, &size, var->Data); in efivar_attr_read() 96 if (var->Attributes & EFI_VARIABLE_NON_VOLATILE) in efivar_attr_read() 98 if (var->Attributes & EFI_VARIABLE_BOOTSERVICE_ACCESS) in efivar_attr_read() 100 if (var->Attributes & EFI_VARIABLE_RUNTIME_ACCESS) in efivar_attr_read() 102 if (var->Attributes & EFI_VARIABLE_HARDWARE_ERROR_RECORD) in efivar_attr_read() 104 if (var->Attributes & EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS) in efivar_attr_read() 107 if (var->Attributes & in efivar_attr_read() 111 if (var->Attributes & EFI_VARIABLE_APPEND_WRITE) in efivar_attr_read() 127 ret = efivar_entry_get(entry, &var->Attributes, &size, var->Data); in efivar_size_read() [all …]
/linux-5.10/tools/perf/pmu-events/arch/x86/cascadelakex/
D	other.json	11 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 24 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 37 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 50 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 63 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 76 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 89 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 102 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 115 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 128 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… [all …]
D	memory.json	11 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 24 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 37 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 51 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 65 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 79 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 92 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 106 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 120 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 134 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… [all …]
D	cache.json	12 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 26 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 40 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 54 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 78 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 92 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 118 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 132 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 166 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 180 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… [all …]
/linux-5.10/Documentation/driver-api/driver-model/
D	device.rst	38 Attributes chapter 51 Attributes of devices can be exported by a device driver through sysfs. 56 As explained in Documentation/core-api/kobject.rst, device attributes must be 60 Attributes are declared using a macro called DEVICE_ATTR:: 70 names 'dev_attr_type' and 'dev_attr_power'. These two attributes can be 95 device attributes and the device_unregister() function will use this pointer 96 to remove the device attributes. 100 strict expectations on when attributes get created. When a new device is 102 udev) that a new device is available. If attributes are added after the 104 not know about the new attributes. [all …]
/linux-5.10/include/scsi/fc/
D	fc_ms.h	32 FC_FDMI_GHAT = 0x0101, /* Get HBA Attributes / 34 FC_FDMI_GPAT = 0x0110, / Get Port Attributes / 36 FC_FDMI_RHAT = 0x0201, / Register HBA Attributes / 38 FC_FDMI_RPA = 0x0211, / Register Port Attributes / 40 FC_FDMI_DHAT = 0x0301, / Deregister HBA Attributes / 42 FC_FDMI_DPA = 0x0311, / Deregister Port Attributes / 114 Attribute Entry Block for HBA/Port Attributes 124 * Common for HBA/Port Attributes 149 * Register HBA Attributes (RHAT) 166 * Register Port Attributes (RPA) [all …]
/linux-5.10/include/uapi/linux/
D	ncsi.h	17 * @NCSI_CMD_PKG_INFO: list package and channel attributes. Requires 51 * enum ncsi_nl_attrs - General NCSI netlink attributes 53 * @NCSI_ATTR_UNSPEC: unspecified attributes to catch errors 55 * @NCSI_ATTR_PACKAGE_LIST: nested array of NCSI_PKG_ATTR attributes 81 * enum ncsi_nl_pkg_attrs - NCSI netlink package-specific attributes 83 * @NCSI_PKG_ATTR_UNSPEC: unspecified attributes to catch errors 84 * @NCSI_PKG_ATTR: nested array of package attributes 87 * @NCSI_PKG_ATTR_CHANNEL_LIST: nested array of NCSI_CHANNEL_ATTR attributes 102 * enum ncsi_nl_channel_attrs - NCSI netlink channel-specific attributes 104 * @NCSI_CHANNEL_ATTR_UNSPEC: unspecified attributes to catch errors [all …]
D	openvswitch.h	32 * Attributes following the header are specific to a particular OVS Generic 63 * enum ovs_datapath_attr - attributes for %OVS_DP_* commands. 78 * These attributes follow the &struct ovs_header within the Generic Netlink 150 * enum ovs_packet_attr - attributes for %OVS_PACKET_* commands. 157 * extracted from the packet as nested %OVS_KEY_ATTR_* attributes. This allows 161 * for %OVS_PACKET_CMD_EXECUTE. It has nested %OVS_ACTION_ATTR_* attributes. 172 * extracted from the packet as nested %OVS_TUNNEL_KEY_ATTR_* attributes. 179 * These attributes follow the &struct ovs_header within the Generic Netlink 185 OVS_PACKET_ATTR_KEY, /* Nested OVS_KEY_ATTR_* attributes. / 186 OVS_PACKET_ATTR_ACTIONS, / Nested OVS_ACTION_ATTR_* attributes. */ [all …]
/linux-5.10/include/scsi/
D	scsi_transport_fc.h	3 * FiberChannel transport specific attributes exported to sysfs. 7 * Rewrite for host, target, device, and remote port attributes, 163 /* Macro for use in defining Virtual Port attributes / 190 FC Virtual Port Attributes 201 * roles. FC port attributes for the vport will be reported on any 206 * Fixed attributes are not expected to change. The driver is 211 * Dynamic attributes are expected to change. The driver participates 214 * Private attributes are transport-managed values. They are fully 219 /* Fixed Attributes / 221 / Dynamic Attributes */ [all …]
/linux-5.10/Documentation/hwmon/
D	hwmon-kernel-api.rst	63 as well as all sysfs attributes attached to the hwmon device. 73 attributes in the hardware monitoring core, letting the driver focus on reading 74 from and writing to the chip instead of having to bother with sysfs attributes. 149 is optional, but must be provided if any readable attributes exist. 153 optional, but must be provided if any writeable attributes exist. 171 hwmon_chip A virtual sensor type, used to describe attributes 186 describing the attributes supposed by a single sensor. 250 HWMON_C_xxxx Chip attributes, for use with hwmon_chip. 251 HWMON_T_xxxx Temperature attributes, for use with hwmon_temp. 252 HWMON_I_xxxx Voltage attributes, for use with hwmon_in. [all …]
D	mp2975.rst	50 The driver provides the next attributes for the current: 55 attributes. 57 The driver exports the following attributes via the 'sysfs' files, where 73 The driver provides the next attributes for the voltage: 80 The driver exports the following attributes via the 'sysfs' files, where 98 The driver provides the next attributes for the power: 103 The driver exports the following attributes via the 'sysfs' files, where 117 The driver provides the next attributes for the temperature (only from page 0):
/linux-5.10/include/uapi/linux/netfilter/
D	nf_tables.h	131 * enum nft_list_attributes - nf_tables generic list netlink attributes 143 * enum nft_hook_attributes - nf_tables netfilter hook netlink attributes 170 * enum nft_table_attributes - nf_tables table netlink attributes 199 * enum nft_chain_attributes - nf_tables chain netlink attributes 232 * enum nft_rule_attributes - nf_tables rule netlink attributes 272 * enum nft_rule_compat_attributes - nf_tables rule compat attributes 334 * enum nft_set_field_attributes - attributes of concatenated fields 346 * enum nft_set_attributes - nf_tables set netlink attributes 398 * enum nft_set_elem_attributes - nf_tables set element netlink attributes 427 * enum nft_set_elem_list_attributes - nf_tables set element list netlink attributes [all …]
/linux-5.10/Documentation/netlabel/
D	lsm_interface.rst	12 NetLabel is a mechanism which can set and retrieve security attributes from 18 NetLabel Security Attributes 22 it uses the concept of security attributes to refer to the packet's security 23 labels. The NetLabel security attributes are defined by the 25 NetLabel subsystem converts the security attributes to and from the correct 28 security attributes into whatever security identifiers are in use for their 47 LSM has received a packet, used NetLabel to decode its security attributes, 48 and translated the security attributes into a LSM internal identifier the LSM
/linux-5.10/Documentation/filesystems/ext4/
D	attributes.rst	3 Extended Attributes 6 Extended attributes (xattrs) are typically stored in a separate data 8 The first use of extended attributes seems to have been for storing file 10 option it is possible for users to store extended attributes so long as 14 There are two places where extended attributes can be found. The first 19 where extended attributes can be found is in the block pointed to by 29 Extended attributes, when stored after the inode, have a header 72 - Hash value of all attributes. 92 Attributes stored inside an inode do not need be stored in sorted order. 114 Multiple attributes can share the same value. For an inode attribute [all …]
/linux-5.10/tools/perf/pmu-events/arch/x86/skylakex/
D	memory.json	11 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 24 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 47 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 60 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 73 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 95 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 118 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 141 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 154 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… 167 …event codes and predefine mask bit value in a dedicated MSR to specify attributes of the offcore t… [all …]
/linux-5.10/Documentation/power/
D	power_supply_class.rst	10 It defines core set of attributes, which should be applicable to (almost) 11 every power supply out there. Attributes are available via sysfs and uevent 15 the attributes provided are believed to be universally applicable to any 19 Power supply class is extensible, and allows to define drivers own attributes. 32 Attributes/properties 34 Power supply class has predefined set of attributes, this eliminates code 36 predefined attributes and their units. 38 So, userspace gets predictable set of attributes and their units for any 44 for the example how to declare and handle attributes. 57 Attributes/properties detailed [all …]
/linux-5.10/include/net/
D	netlink.h	11 * Netlink Messages and Attributes Interface (As Seen On TV) 29 * \| Family Header \| Pad \| Attributes \| 59 * nlmsg_attrdata(nlh, hdrlen) head of attributes data 60 * nlmsg_attrlen(nlh, hdrlen) length of attributes data 65 * nlmsg_parse() parse attributes of a message 69 * nlmsg_for_each_attr() loop over all attributes 75 * Attributes Interface 116 * Nested Attributes Construction: 151 * nla_validate() validate a stream of attributes 152 * nla_validate_nested() validate a stream of nested attributes [all …]
/linux-5.10/include/uapi/linux/sched/
D	types.h	25 * This variant (sched_attr) allows to define additional attributes to 28 * Scheduling Class Attributes 31 * A subset of sched_attr attributes specifies the 32 * scheduling policy and relative POSIX attributes: 45 * Sporadic Time-Constrained Task Attributes 48 * A subset of sched_attr attributes allows to describe a so-called 77 * Task Utilization Attributes 80 * A subset of sched_attr attributes allows to specify the utilization 81 * expected for a task. These attributes allow to inform the scheduler about
/linux-5.10/Documentation/driver-api/iio/
D	core.rst	52 Attributes are sysfs files used to expose chip info and also allowing 54 index X, attributes can be found under /sys/bus/iio/iio:deviceX/ directory. 55 Common attributes are: 62 * Available standard attributes for IIO devices are described in the 91 Channel sysfs attributes exposed to userspace are specified in the form of 92 bitmasks. Depending on their shared info, attributes can be set in one of the 95 * info_mask_separate, attributes will be specific to 97 * info_mask_shared_by_type, attributes are shared by all channels of the 99 * info_mask_shared_by_dir, attributes are shared by all channels of the same 101 * info_mask_shared_by_all, attributes are shared by all channels [all …]

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