Searched full:private (Results 1 – 25 of 223) sorted by relevance
123456789
| /Documentation/filesystems/bcachefs/ |
| D | errorcodes.rst | 3 bcachefs private error codes
7 codes (-EINVAL, -EBUSY, etc.). Instead, we define private error codes as needed
14 Private error codes may subtype another error code, this allows for grouping of
23 Do not reuse error codes! Generally speaking, a private error code should only
|
| /Documentation/translations/zh_CN/mm/ |
| D | overcommit-accounting.rst | 59 | PRIVATE WRITABLE - 每个实例的映射大小
63 | PRIVATE READ-only - 0 cost (但作用不大)
64 | PRIVATE WRITABLE - 每个实例的映射大小
|
| /Documentation/admin-guide/ |
| D | module-signing.rst | 14 .. - Administering/protecting the private key.
103 The string provided should identify a file containing both a private key
107 certificate and a private key.
109 If the PEM file containing the private key is encrypted, or if the
130 private key is used to generate a signature and the corresponding public key is
131 used to check it. The private key is only needed during the build, after which
169 It is also possible to manually generate the key private/public files using the
172 generate the public/private key files::
224 2. The private key filename or PKCS#11 URI
237 If the private key requires a passphrase or PIN, it can be provided in the
[all …]
|
| /Documentation/userspace-api/media/drivers/ |
| D | omap3isp-uapi.rst | 47 Private IOCTLs
55 In general, there is a private ioctl for configuring each of the blocks
58 The following private IOCTLs are supported:
73 While it is possible to use the ISP driver without any use of these private
76 appropriate private IOCTLs.
146 the user from the statistics subdev nodes using private IOCTLs.
148 The private IOCTLs offered by the AEWB, AF and histogram subdevs are heavily
156 This private IOCTL enables/disables a statistic module. If this request is
167 configure private IOCTLs require explanation for better understanding as they
|
| D | aspeed-video.rst | 32 Enable/Disable ASPEED's High quality mode. This is a private control
47 Define the quality of ASPEED's High quality mode. This is a private control
|
| /Documentation/userspace-api/ |
| D | futex2.rst | 37 and ``flags`` to specify the type (e.g. private) and size of futex.
74 A futex can be either private or shared. Private is used for processes that
77 private futexes, it's necessary to specify ``FUTEX_PRIVATE_FLAG`` in the futex
81 properly enqueued. This is the default behavior, and it works with both private
|
| /Documentation/networking/ |
| D | 6lowpan.rst | 4 Netdev private dataroom for 6lowpan interfaces
14 Where LL_PRIV_6LOWPAN_DATA is sizeof linklayer 6lowpan private data struct.
28 Example to evaluate the private usually you can do::
|
| D | ipvlan.rst | 37 FLAGS: bridge (default) | private | vepa
49 (c) This command will create an IPvlan device in L2 private mode::
51 bash# ip link add link eth0 name ipvlan type ipvlan mode l2 private
105 5.2 private:
107 If this option is added to the command-line, the port is set in private
|
| /Documentation/mm/ |
| D | hmm.rst | 34 driver and regular application memory (private anonymous, shared memory, or
46 to copy objects between generically allocated memory (malloc, mmap private, mmap
269 Before migrating pages to device private memory, special device private
272 a page that has been migrated to device private memory.
312 device private memory. If the latter flag is set, the ``args->pgmap_owner``
313 field is used to identify device private pages owned by the driver. This
314 avoids trying to migrate device private pages residing in other devices.
315 Currently only anonymous private VMA ranges can be migrated to or from
316 system memory and device private memory.
327 invalidate device private MMU mappings that are actually migrating.
[all …]
|
| D | overcommit-accounting.rst | 58 | PRIVATE WRITABLE - size of mapping per instance
62 | PRIVATE READ-only - 0 cost (but of little use)
63 | PRIVATE WRITABLE - size of mapping per instance
|
| D | hugetlbfs_reserv.rst | 80 Reservation Map Location (Private or Shared)
83 A huge page mapping or segment is either private or shared. If private,
89 - For private mappings, the reservation map hangs off the VMA structure.
121 One of the big differences between PRIVATE and SHARED mappings is the way
127 - For private mappings, the lack of an entry in the reservation map indicates
133 For private mappings, hugetlb_reserve_pages() creates the reservation map and
138 are needed for the current mapping/segment. For private mappings, this is
167 file_region will exist that includes the range 'from' - 'to'. For private
244 was no reservation in a shared mapping or this was a private mapping a new
265 to the page cache and pages in private mappings are added to an anonymous
[all …]
|
| /Documentation/translations/zh_CN/doc-guide/ |
| D | parse-headers.rst | 148 ignore symbol PRIVATE
153 enum foo { BAR1, BAR2, PRIVATE };
155 不会为 \ **PRIVATE**\ 生成交叉引用。
163 enum foo { BAR1, BAR2, PRIVATE };
|
| /Documentation/filesystems/ |
| D | sharedsubtree.rst | 38 c. private mount
129 2c) A private mount does not forward or receive propagation.
134 2d) A unbindable mount is a unbindable private mount
157 mount --make-private mountpoint
255 4) private
314 (4) Private mount
316 A 'private mount' is defined as vfsmount that does not
332 | |make-shared | make-slave | make-private |make-unbindab|
334 |shared |shared |*slave/private| private | unbindable |
337 |slave |shared | **slave | private | unbindable |
[all …]
|
| /Documentation/scheduler/ |
| D | membarrier.rst | 7 MEMBARRIER_CMD_{PRIVATE,GLOBAL}_EXPEDITED - Architecture requirements
18 membarrier_{private,global}_expedited().
39 entry, cf. membarrier_{private,global}_expedited().
|
| /Documentation/arch/x86/ |
| D | tdx.rst | 24 as TDX private KeyIDs, which are only accessible within the SEAM mode.
35 The kernel detects TDX by detecting TDX private KeyIDs during kernel
38 [..] virt/tdx: BIOS enabled: private KeyID range: [16, 64)
156 write to a TDX private memory cacheline will silently "poison" the
165 Theoretically, a kernel bug could do partial write to TDX private memory
172 kernel bug on TDX private memory.
283 There are essentially two classes of TDX memory: private and shared.
284 Private memory receives full TDX protections. Its content is protected
290 private or shared. It selects the behavior with a bit in its page table
314 #VE on Private Pages
[all …]
|
| /Documentation/doc-guide/ |
| D | parse-headers.rst | 155 ignore symbol PRIVATE
160 enum foo { BAR1, BAR2, PRIVATE };
162 It won't generate cross-references for \ **PRIVATE**\ .
170 enum foo { BAR1, BAR2, PRIVATE };
|
| /Documentation/translations/it_IT/doc-guide/ |
| D | parse-headers.rst | 160 ignore symbol PRIVATE
165 enum foo { BAR1, BAR2, PRIVATE };
167 Non genererà alcun riferimento per \ **PRIVATE**\ .
175 enum foo { BAR1, BAR2, PRIVATE };
|
| /Documentation/security/tpm/ |
| D | tpm-security.rst | 71 and private key import and random number generation, is vulnerable to
180 generated private key is described below.
185 owner hierarchy. The owner creates an external public/private key
186 pair (assume elliptic curve in this case) and wraps the private key
194 copy of the private key only for the certified TPM. This key is now
204 using the null primary as the object handle and the loaded private key
207 part of the loaded private key and the qualifying data checked to
|
| /Documentation/fpga/ |
| D | dfl.rst | 25 FPGA Interface Unit (FIU), Accelerated Function Unit (AFU) and Private Features,
31 | FIU | | | Private | | | Private | | | Private |
63 Private Features represent sub features of the FIU and AFU. They could be
64 various function blocks with different IDs, but all private features which
68 Each FIU, AFU and Private Feature could implement its own functional registers.
70 e.g. FME Header Register Set, and the one for Private Feature, is named as
94 * Type - The type of DFH (e.g. FME, AFU, or private feature).
102 * ID - The feature ID if Type is private feature.
153 * Type - The type of DFH (e.g. FME, AFU, or private feature).
161 * ID - The feature ID if Type is private feature.
[all …]
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | fsl,qman-fqd.yaml | 7 title: QMan Private Memory Nodes
25 The following constraints are relevant to the FQD and PFDR private memory:
|
| /Documentation/devicetree/bindings/net/can/ |
| D | bosch,m_can.yaml | 59 telling driver how the shared or private Message RAM are
66 0x0 if you're using a private Message RAM. The remain cells
84 you're using a private Message RAM.
|
| /Documentation/process/ |
| D | maintainer-pgp-guide.rst | 81 of caching the private key passphrase. There are two options you should
142 private subkey, it cannot be restored or recreated from any other
143 private key on your chain.
183 GnuPG uses passphrases to encrypt your private keys before storing them on
185 its entirety, the attackers cannot use your private keys without first
188 It is absolutely essential that your private keys are protected by a
216 The best way to create a printable hardcopy of your private key is by
222 Run the following command to create a hardcopy backup of your private
325 $ cd ~/.gnupg/private-keys-v1.d
334 $ cd ~/.gnupg/private-keys-v1.d
[all …]
|
| D | code-of-conduct.rst | 34 * Public or private harassment
35 * Publishing others’ private information, such as a physical or electronic
|
| D | botching-up-ioctls.rst | 184 default pick a private per-fd namespace which forces any sharing to be done
189 namespace, private by default, for framebuffers would have been more
207 * Think hard whether you really want a driver-private interface. Of course
208 it's much quicker to push a driver-private interface than engaging in
210 private interface to spearhead a new concept is what's required. But in the
|
| /Documentation/arch/s390/ |
| D | driver-model.rst | 88 struct ccw_device_private *private;
111 The 'private' field contains data needed for internal i/o operation only, and
133 is interested in. The driver should only allocate private structures
176 down the device, but not de-allocate its private data.
261 private data.
|
123456789