Searched full:tag (Results 1 – 25 of 174) sorted by relevance
1234567
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 142 3.4 Tag Types
146 information relevant to the data in the IP packet. Each tag begins with
147 a tag type identifier followed by the length of the tag and ends with the
148 actual security information to be passed. All multi-octet fields in a tag
151 all tags, as well as fields within a tag, are not aligned on any particular
152 octet boundary. The tag types defined in this document contain alignment
156 CIPSO tag types 0 through 127 are reserved for defining standard tag
157 formats. Their definitions will be published in RFCs. Tag types whose
159 only be meaningful in certain Domains of Interpretation. For these tag
160 types, implementations will require the DOI identifier as well as the tag
[all …]
|
| /Documentation/dev-tools/ |
| D | kasan.rst | 16 2. Software Tag-Based KASAN
17 3. Hardware Tag-Based KASAN
23 Software Tag-Based KASAN or SW_TAGS KASAN, enabled with CONFIG_KASAN_SW_TAGS,
28 Hardware Tag-Based KASAN or HW_TAGS KASAN, enabled with CONFIG_KASAN_HW_TAGS,
37 The Generic and the Software Tag-Based modes are commonly referred to as the
38 software modes. The Software Tag-Based and the Hardware Tag-Based modes are
39 referred to as the tag-based modes.
48 and loongarch, and the tag-based KASAN modes are supported only on arm64.
55 support for that. The Hardware Tag-Based mode relies on hardware to perform
62 Software Tag-Based KASAN requires GCC 11+
[all …]
|
| /Documentation/arch/arm64/ |
| D | memory-tagging-extension.rst | 19 allocation tag for each 16-byte granule in the physical address space.
21 attribute. A logical tag is derived from bits 59-56 of the virtual
23 the logical tag against the allocation tag and potentially raise an
42 The allocation tag is set to 0 when such pages are first mapped in the
58 Tag Check Faults
66 tag check fault.
75 thread, asynchronously following one or multiple tag check faults,
87 - ``PR_MTE_TCF_NONE`` - *Ignore* tag check faults
89 - ``PR_MTE_TCF_SYNC`` - *Synchronous* tag check fault mode
90 - ``PR_MTE_TCF_ASYNC`` - *Asynchronous* tag check fault mode
[all …]
|
| D | tagged-pointers.rst | 23 an address tag of 0x00, unless the application enables the AArch64
45 forbidden, and using a non-zero address tag for sp is strongly
60 on the tag information for user virtual addresses being maintained
64 are not preserved in response to synchronous tag check faults
70 tag information will be preserved regardless of the SA_EXPOSE_TAGBITS
|
| D | tagged-address-abi.rst | 62 tag-unaware programs.
154 unsigned long tag = 0;
167 /* set a non-zero tag if the ABI is available */
169 tag = rand() & 0xff;
170 ptr = (char *)((unsigned long)ptr | (tag << TAG_SHIFT));
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 27 In order to create the pull request you must first tag the branch that you
28 have just created. It is recommended that you choose a meaningful tag name,
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
38 git tag -s char-misc-4.15-rc1 char-misc-next
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
44 Linus will only accept pull requests based on a signed tag. Other
48 you to describe the tag. In this case, you are describing a pull request,
50 any, testing has been done. All of this information will end up in the tag
73 the signed tag, so depending on your workflow, you can either
74 describe your work in the signed tag (which will also automatically
[all …]
|
| D | configure-git.rst | 9 ``-u <key-id>`` to ``git tag``. However, since you would *usually* use the same
39 patch to a subsystem tree, it is a good idea to provide a Link: tag with a
42 The link tag will look like this::
|
| /Documentation/networking/ |
| D | mctp.rst | 151 in ``MCTP_TAG_VALUE``, and generate a tag value suitable for the destination
152 EID. If ``MCTP_TAG_OWNER`` is not set, the message will be sent with the tag
153 value as specified. If a tag value cannot be allocated, the system call will
167 specified will cause an allocation of a tag, if no valid tag is already
168 allocated for that destination. The (destination-eid,tag) tuple acts as an
202 remote address of the incoming message, including tag value (this will be needed
219 (and dropping) tag values explicitly, rather than the kernel automatically
220 allocating a per-message tag at ``sendmsg()`` time.
225 In these cases, the ioctls allow you to decouple the tag allocation (and
234 __u8 tag;
[all …]
|
| /Documentation/arch/sparc/ |
| D | adi.rst | 8 address space of a task, the processor will compare the tag in pointers
10 previously. Access to memory is granted only if the tag in given pointer
11 matches the tag set by the application. In case of mismatch, processor
20 addresses ADI is being enabled on. MMU checks the version tag only
23 3. Set the version tag for virtual addresses using stxa instruction
25 given tag for one ADI block size number of bytes. This step must
30 top bits in the virtual address that specify the version tag. Once
31 version tag has been set for a memory location, the tag is stored in the
32 physical memory and the same tag must be present in the ADI version tag
58 - Version tag values of 0x0 and 0xf are reserved. These values match any
[all …]
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 2 Tag matching logic
5 The MPI standard defines a set of rules, known as tag-matching, for matching
10 * User tag - wild card may be specified by the receiver
18 the order they are created, e.g., a later generated tag may be consumed, if
35 2. The Rendezvous Protocol - the sender sends the tag-matching header,
41 Tag matching implementation
54 specified receive buffer. This allows overlapping receive-side MPI tag
66 tightly synchronized with respect to the tag-matching operation, this shadow
|
| /Documentation/networking/dsa/ |
| D | b53.rst | 21 switch tag which gets inserted by the switch for every packet forwarded to the
23 tag for packets entering the CPU port. The tag format is described in
43 Older models (5325, 5365) support a different tag format that is not supported
66 # tag traffic on CPU port
93 # tag traffic on ports
113 # tag traffic on CPU port
148 # tag traffic on CPU port
174 # tag traffic on ports
|
| /Documentation/devicetree/bindings/cache/ |
| D | baikal,bt1-l2-ctl.yaml | 16 to change the Tag, Data and Way-select RAM access latencies. Baikal-T1
34 baikal,l2-tag-latency:
36 description: Cycles of latency for Tag RAM accesses
60 baikal,l2-tag-latency = <1>;
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 9 writing the sector and the integrity tag must be atomic - i.e. in case of
10 crash, either both sector and integrity tag or none of them is written.
24 mode it calculates and verifies the integrity tag internally. In this
70 3. the size of the integrity tag (if "-" is used, the size is taken from
79 and integrity tag doesn't match.
83 either both data and tag or none of them are written. The
189 Use a smaller padding of the tag area that is more
217 block_size of 512, and an internal_hash of crc32c with a tag size of 4
242 * integrity tag size
265 * logical sector (specifies where the data and tag should
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-virtiofs | 1 What: /sys/fs/virtiofs/<n>/tag
5 [RO] The mount "tag" that can be used to mount this filesystem.
|
| D | sysfs-class-fc | 11 FC adapter drivers may query the identifier and tag FC
14 tag to identify traffic sources.
|
| /Documentation/arch/riscv/ |
| D | acpi.rst | 8 Conversion, 12/2022 of the RISC-V specifications, as defined by tag
10 ) <https://github.com/riscv/riscv-isa-manual/releases/tag/riscv-isa-release-1239329-2023-05-23>`_
|
| /Documentation/mm/ |
| D | allocation-profiling.rst | 27 "compressed" optional parameter will try to store page tag references in a
64 - declares a code tag
67 - and finally, restores the task_struct alloc tag pointer to its previous value.
90 It's also possible to stash a pointer to an alloc tag in your own data structures.
101 record alloc tag in your data structure.
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | interconnect.txt | 23 path tag
48 An optional path tag value could specified as additional argument
51 tag.
|
| /Documentation/filesystems/ext4/ |
| D | journal.rst | 320 v2, but the journal block tag size is fixed regardless of the size of
373 journal feature and block tag flags are set.
375 If JBD2_FEATURE_INCOMPAT_CSUM_V3 is set, the journal block tag is
411 tag, after t_checksum. This field is not present if the "same UUID" flag
416 - A UUID to go with this tag. This field appears to be copied from the
422 The journal tag flags are any combination of the following:
439 - This is the last tag in this descriptor block.
441 If JBD2_FEATURE_INCOMPAT_CSUM_V3 is NOT set, the journal block tag
482 tag, after t_flags or t_blocknr_high. This field is not present if the
487 - A UUID to go with this tag. This field appears to be copied from the
[all …]
|
| /Documentation/devicetree/bindings/arm/mstar/ |
| D | mstar.yaml | 30 - wirelesstag,ido-som2d01 # Wireless Tag IDO-SOM2D01
31 - wirelesstag,ido-sbc2d06-v1b-22w # Wireless Tag IDO-SBC2D06-1VB-22W
|
| /Documentation/process/ |
| D | 5.Posting.rst | 158 - One or more tag lines, with, at a minimum, one Signed-off-by: line from
204 One tag is used to refer to earlier commits which introduced problems fixed by
209 Another tag is used for linking web pages with additional backgrounds or
215 Many maintainers when applying a patch also add this tag to link to the
221 "Closes:" tag instead::
226 commit with such a tag is applied. Some bots monitoring mailing lists can
230 Another kind of tag is used to document who was involved in the development of
233 tag: Full Name <email address> optional-other-stuff
245 attributed by the From: tag) when multiple people work on a single patch.
262 patch; this tag is used to give credit to the (often underappreciated)
[all …]
|
| D | submitting-patches.rst | 135 In case your patch fixes a bug, use the 'Closes:' tag with a URL referencing
141 commit with such a tag is applied. Some bots monitoring mailing lists can
146 ``git bisect``, please use the 'Fixes:' tag with the first 12 characters of
147 the SHA-1 ID, and the one line summary. Do not split the tag across multiple
459 The Signed-off-by: tag indicates that the signer was involved in the
483 provided such comments, you may optionally add a ``Cc:`` tag to the patch.
484 This is the only tag which might be added without an explicit action by the
486 patch. This tag documents that potentially interested parties
491 attributed by the From: tag) when several people work on a single patch. Since
499 Note, the From: tag is optional when the From: author is also the person (and
[all …]
|
| D | license-rules.rst | 205 All text after this tag is treated as the original license text
214 tag/value pairs into a comment according to the placement
229 tag/value pair into a comment according to the placement
276 tag/value pair into a comment according to the placement
325 tag/value pair into a comment according to the placement guidelines in
386 All text after this tag is treated as the original exception text
398 identifiers in the SPDX-Licenses tag:
413 identifiers in the SPDX-Licenses tag:
428 Loadable kernel modules also require a MODULE_LICENSE() tag. This tag is
434 The sole purpose of this tag is to provide sufficient information
|
| /Documentation/devicetree/ |
| D | dynamic-resolution-notes.rst | 14 proper dtc option and having a /plugin/ tag. This generates the
24 in the live tree. This is the label used to tag the node.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_cls.rst | 6 tag network packets with a class identifier (classid).
10 Also, Netfilter (iptables) can use this tag to perform
|
1234567