| /linux/include/linux/ |
| H A 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...) 24 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alias-function-a… 29 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-aligned-function… 30 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Type-Attributes.html#index-aligned-type-attribu… 31 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Variable-Attributes.html#index-aligned-variable… 38 * available and includes other attributes. For GCC < 9.1, __alloc_size__ gets undefined 41 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alloc_005fsize-f… 52 …* gcc: https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-always_005finlin… [all …]
|
| /linux/Documentation/netlink/specs/ |
| H A D | nfsd.yaml | 12 attributes: 67 attributes: 91 attributes: 103 attributes: 107 nested-attributes: version 111 attributes: 120 attributes: 124 nested-attributes: sock 128 attributes: 144 attributes: [all …]
|
| H A D | nlctrl.yaml | 50 attributes: 70 nested-attributes: op-attrs 75 nested-attributes: mcast-group-attrs 80 nested-attributes: policy-attrs 85 nested-attributes: op-policy-attrs 93 attributes: 104 attributes: 117 attributes: 159 attributes: 178 attributes: [all …]
|
| H A D | net_shaper.yaml | 75 attributes: 79 nested-attributes: handle 121 nested-attributes: handle 129 nested-attributes: leaf-info 134 attributes: 150 attributes: 159 attributes: 217 attributes: &ns-binding 221 attributes: &ns-attrs 236 attributes: [all …]
|
| H A D | dev-energymodel.yaml | 49 attributes: 74 attributes: 83 nested-attributes: perf-state 89 attributes: 130 attributes: 133 attributes: &perf-domain-attrs 140 attributes: *perf-domain-attrs 147 attributes: 150 attributes: 168 attributes:
|
| H A D | handshake.yaml | 34 attributes: 43 attributes: 69 nested-attributes: x509 79 attributes: 104 attributes: 107 attributes: 122 attributes:
|
| /linux/net/netlabel/ |
| H A 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 …]
|
| H A 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 …]
|
| H A 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 */
|
| H A 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/fs/efivarfs/ |
| H A 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() 50 bytes = efivar_entry_set_get_size(var, attributes, &datasize, in efivarfs_file_write() 65 i_size_write(inode, datasize + sizeof(attributes)); in efivarfs_file_write() 84 u32 attributes; in efivarfs_file_read() local 103 data = kmalloc(datasize + sizeof(attributes), GFP_KERNEL); in efivarfs_file_read() [all …]
|
| /linux/include/uapi/linux/ |
| H A D | smc.h | 15 /* Netlink SMC_PNETID attributes */ 67 /* SMC_GENL_FAMILY top level attributes */ 82 /* SMC_GEN_SYS_INFO attributes */ 95 /* SMC_NLA_LGR_D_V2_COMMON and SMC_NLA_LGR_R_V2_COMMON nested attributes */ 106 /* SMC_NLA_LGR_R_V2 nested attributes */ 116 /* SMC_GEN_LGR_SMCR attributes */ 136 /* SMC_GEN_LINK_SMCR attributes */ 153 /* SMC_GEN_LGR_SMCD attributes */ 173 /* SMC_NLA_DEV_PORT nested attributes */ 186 /* SMC_GEN_DEV_SMCD and SMC_GEN_DEV_SMCR attributes */ [all …]
|
| H A 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 …]
|
| /linux/Documentation/driver-api/driver-model/ |
| H A 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:: 76 names 'dev_attr_type' and 'dev_attr_power'. These two attributes can be 106 device attributes and the device_unregister() function will use this pointer 107 to remove the device attributes. 111 strict expectations on when attributes get created. When a new device is 113 udev) that a new device is available. If attributes are added after the 115 not know about the new attributes. [all …]
|
| /linux/include/scsi/fc/ |
| H A D | fc_ms.h | 38 FC_FDMI_GHAT = 0x0101, /* Get HBA Attributes */ 40 FC_FDMI_GPAT = 0x0110, /* Get Port Attributes */ 42 FC_FDMI_RHAT = 0x0201, /* Register HBA Attributes */ 44 FC_FDMI_RPA = 0x0211, /* Register Port Attributes */ 46 FC_FDMI_DHAT = 0x0301, /* Deregister HBA Attributes */ 48 FC_FDMI_DPA = 0x0311, /* Deregister Port Attributes */ 155 * Attribute Entry Block for HBA/Port Attributes 165 * Common for HBA/Port Attributes 190 * Register HBA Attributes (RHAT) 207 * Register Port Attributes (RPA) [all …]
|
| /linux/Documentation/filesystems/ext4/ |
| H A 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/Documentation/hwmon/ |
| H A D | mp9941.rst | 29 The driver exports the following attributes via the 'sysfs' files 40 The driver provides the following attributes for output voltage: 54 The driver provides the following attributes for input current: 64 The driver provides the following attributes for output current: 70 The driver provides the following attributes for input power: 76 The driver provides the following attributes for output power: 82 The driver provides the following attributes for temperature:
|
| H A D | mp2993.rst | 29 The driver exports the following attributes via the 'sysfs' files 52 The driver provides the following attributes for output voltage: 78 The driver provides the following attributes for input current: 88 The driver provides the following attributes for output current: 114 The driver provides the following attributes for input power: 120 The driver provides the following attributes for output power: 130 The driver provides the following attributes for temperature:
|
| H A D | mp2888.rst | 39 The driver provides the next attributes for the current: 44 The driver exports the following attributes via the 'sysfs' files, where: 58 The driver provides the next attributes for the voltage: 64 The driver exports the following attributes via the 'sysfs' files, where 84 The driver provides the next attributes for the power: 89 The driver exports the following attributes via the 'sysfs' files, where 107 The driver provides the next attributes for the temperature:
|
| H A D | mp2891.rst | 34 The driver exports the following attributes via the 'sysfs' files 53 The driver provides the following attributes for output voltage: 87 The driver provides the following attributes for input current: 105 The driver provides the following attributes for output current: 131 The driver provides the following attributes for input power: 149 The driver provides the following attributes for output power: 159 The driver provides the following attributes for temperature:
|
| H A 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/Documentation/netlabel/ |
| H A 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/include/uapi/linux/sched/ |
| H A D | types.h | 21 * This variant (sched_attr) allows to define additional attributes to 24 * Scheduling Class Attributes 27 * A subset of sched_attr attributes specifies the 28 * scheduling policy and relative POSIX attributes: 41 * Sporadic Time-Constrained Task Attributes 44 * A subset of sched_attr attributes allows to describe a so-called 73 * Task Utilization Attributes 76 * A subset of sched_attr attributes allows to specify the utilization 77 * expected for a task. These attributes allow to inform the scheduler about
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numaperf.rst | 70 the system provides these attributes, the kernel exports them under the 71 node sysfs hierarchy by appending the attributes directory under the 76 These attributes apply only when accessed from nodes that have the 89 The bandwidth attributes are provided in MiB/second. 91 The latency attributes are provided in nanoseconds. 127 An application does not need to know about caching attributes in order 129 attributes in order to maximize the performance out of such a setup. 132 the kernel will append these attributes to the NUMA node memory target. 142 The attributes for each level of cache is provided under its cache 149 Each cache level's directory provides its attributes. For example, the [all …]
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | running_tips.rst | 278 Test Attributes and Filtering 281 Test suites and cases can be marked with test attributes, such as speed of 282 test. These attributes will later be printed in test output and can be used to 285 Marking Test Attributes 291 Test cases can be marked using the ``KUNIT_CASE_ATTR(test_name, attributes)`` 323 Not all attributes need to be set in a ``kunit_attributes`` object. Unset 324 attributes will remain uninitialized and act as though the attribute is set 326 These unset attributes will not be reported and may act as a default value 329 Reporting Attributes 332 When a user runs tests, attributes will be present in the raw kernel output (in [all …]
|