Searched full:new (Results 1 – 25 of 951) sorted by relevance
12345678910>>...39
| /Documentation/RCU/ |
| D | arrayRCU.txt | 58 new ipc_id_ary, copies the old to the new portion of the new, initializes
59 the remainder of the new, updates the ids->entries pointer to point to
60 the new array, and invokes ipc_rcu_putref() to free up the old array.
67 struct ipc_id_ary* new;
77 new = ipc_rcu_alloc(sizeof(struct kern_ipc_perm *)*newsize +
79 if(new == NULL)
81 new->size = newsize;
82 memcpy(new->p, ids->entries->p,
86 new->p[i] = NULL;
92 * contents of the new array are visible before the new
[all …]
|
| /Documentation/process/ |
| D | adding-syscalls.rst | 4 Adding a New System Call
7 This document describes what's involved in adding a new system call to the
15 The first thing to consider when adding a new system call is whether one of
22 object, it may make more sense to create a new filesystem or device. This
23 also makes it easier to encapsulate the new functionality in a kernel module
26 - If the new functionality involves operations where the kernel notifies
27 userspace that something has happened, then returning a new file
35 - If you're just exposing runtime system information, a new node in sysfs
44 this option is best for when the new function is closely analogous to
45 existing :manpage:`fcntl(2)` functionality, or the new functionality is very simple
[all …]
|
| D | submit-checklist.rst | 40 6) Any new or modified ``CONFIG`` options do not muck up the config menu and
44 7) All new ``Kconfig`` options have help text.
77 17) All new ``/proc`` entries are documented under ``Documentation/``
79 18) All new kernel boot parameters are documented in
82 19) All new module parameters are documented with ``MODULE_PARM_DESC()``
84 20) All new userspace interfaces are documented in ``Documentation/ABI/``.
94 If the new code is substantial, addition of subsystem-specific fault
|
| /Documentation/security/keys/ |
| D | trusted-encrypted.rst | 5 Trusted and Encrypted Keys are two new key types added to the existing kernel
6 key ring service. Both of these new types are variable length symmetric keys,
16 integrity verifications match. A loaded Trusted Key can be updated with new
17 (future) PCR values, so keys are easily migrated to new pcr values, such as
50 keyctl add trusted name "new keylen [options]" ring
65 migratable= 0|1 indicating permission to reseal to new PCR values,
78 TPM_STORED_DATA format. The key length for new keys are always in bytes.
83 encryption/decryption. New keys are created from kernel generated random
97 keyctl add encrypted name "new [format] key-type:master-key-name keylen"
114 "new 32 keyhandle=0x81000001".
[all …]
|
| /Documentation/admin-guide/ |
| D | binderfs.rst | 8 located in a new binderfs instance are independent of binder devices located in
9 other binderfs instances. Mounting a new binderfs instance makes it possible
20 at which point a new instance of binderfs will show up at ``/dev/binderfs``.
24 create a new and separate instance from all other binderfs mounts. This is
41 To allocate a new binder device in a binderfs instance a request needs to be
47 tell the kernel which name the new binder device should get. By default a name
52 binder_device`` with the name to the kernel it will allocate a new binder
53 device and return the major and minor number of the new device in the struct
55 dynamically.). After the `ioctl() <ioctl_>`_ returns there will be a new
|
| D | initrd.rst | 10 can be run from it. Afterwards, a new root file system can be mounted
41 8) init execs the ``/sbin/init`` on the new root filesystem, performing
54 initrd adds the following new options::
217 - mounting the new root file system
222 Mounting the new root file system is easy: it just needs to be mounted on
225 # mkdir /new-root
226 # mount -o ro /dev/hda1 /new-root
231 [#f3]_). ``pivot_root`` moves the current root to a directory under the new
232 root, and puts the new root at its place. The directory for the old root
235 # cd /new-root
[all …]
|
| /Documentation/security/ |
| D | IMA-templates.rst | 19 a new template is defined, the functions that generate and display
20 the measurements list would include the code for handling a new format
25 definition of two new data structures: a template descriptor, to determine
30 a new data type, developers define the field identifier and implement
32 measurement entries. Defining a new template descriptor requires
40 (new function defined within the patches for the new template management
41 mechanism) to generate a new measurement entry by using the template
44 It is during this phase that the advantages of the new architecture are
61 ``('<identifier>': description)``, that can be used to define new template
97 - register a new template descriptor with custom format through the kernel
|
| /Documentation/virt/kvm/ |
| D | review-checklist.txt | 9 3. If the patch introduces or modifies a new userspace API:
13 4. New state must include support for save/restore.
15 5. New features must default to off (userspace should explicitly request them).
18 6. New cpu features should be exposed via KVM_GET_SUPPORTED_CPUID2
33 11. New guest visible features must either be documented in a hardware manual
|
| /Documentation/vm/ |
| D | page_migration.rst | 18 a new memory policy via mbind(). The pages of process can also be relocated
33 nearer to the new processor. The kernel itself does only provide
46 a new cpuset then also all its pages are moved with it so that the
77 how to allocate the correct new page given the old page.
81 the new page for each page that is considered for
98 3. Lock the new page that we want to move to. It is locked so that accesses to
115 8. The new page is prepped with some settings from the old page so that
116 accesses to the new page will discover a page with the correct settings.
118 9. The radix tree is changed to point to the new page.
121 reference is gone. A reference to the new page is established because
[all …]
|
| D | mmu_notifier.rst | 16 B) a page table entry is updated to point to a new page (COW, write fault
27 - set page table entry to point to new page
30 the new pte/pmd value then you can break memory model like C11 or C++11 for
55 CPU-thread-0 {COW_step1: {update page table to point to new page for addrA}}
56 CPU-thread-1 {COW_step1: {update page table to point to new page for addrB}}
64 CPU-thread-2 {write to addrA which is a write to new page}
72 CPU-thread-3 {write to addrB which is a write to new page}
88 DEV-thread-2 {read addrB from new page}
91 notification to invalidate the secondary TLB, the device see the new value for
92 addrB before seing the new value for addrA. This break total memory ordering
[all …]
|
| /Documentation/sh/ |
| D | new-machine.txt | 2 Adding a new board to LinuxSH
8 for new boards to the LinuxSH port under the new 2.5 and 2.6 kernels. This
12 1. New Directory Structure
15 The first thing to note is the new directory structure. Under 2.4, most
18 include/asm-sh/. For the new kernel, things are broken out by board type,
85 2. Adding a New Board
99 After you have setup your new arch/sh/boards/ directory, remember that you
141 Our new imaginary board will also have to tie into the machvec in order for it
163 Adding a new machine is relatively trivial (using vapor as an example):
169 - add a new file include/asm-sh/vapor.h which contains prototypes for
[all …]
|
| /Documentation/ |
| D | rbtree.txt | 59 Creating a new rbtree
110 new node, then inserting the node and rebalancing ("recoloring") the tree.
113 location of the pointer on which to graft the new node. The new node also
120 struct rb_node **new = &(root->rb_node), *parent = NULL;
122 /* Figure out where to put new node */
123 while (*new) {
124 struct mytype *this = container_of(*new, struct mytype, node);
127 parent = *new;
129 new = &((*new)->rb_left);
131 new = &((*new)->rb_right);
[all …]
|
| D | robust-futexes.txt | 39 prematurely - and the new owner can decide whether the data protected by
56 robust futexes attached to this area'. This approach requires 3 new
86 New approach to robust futexes
89 At the heart of this new approach there is a per-thread private list of
91 userspace list is registered with the kernel via a new syscall [this
121 Ulrich Drepper has implemented the necessary glibc support for this new
152 million (!) held locks, using the new method [on a 2GHz CPU]:
169 The patch adds two new syscalls: one to register the userspace list, and
183 for new threads, without the need of another syscall.]
209 I've tested the new syscalls on x86 and x86_64, and have made sure the
[all …]
|
| /Documentation/x86/ |
| D | intel_mpx.rst | 10 Intel(R) Memory Protection Extensions (Intel(R) MPX) is a new capability
41 starts. New instruction prefixes are noops for old CPUs.
44 bit) and notifies the kernel (via the new prctl(PR_MPX_ENABLE_MANAGEMENT))
52 3) The kernel detects that the CPU has MPX, allows the new prctl() to
61 in the bounds directory point to the new table.
79 * calls a new prctl(PR_MPX_ENABLE_MANAGEMENT) to notify the kernel to
87 updates the bounds directory to point to the new table. It keeps
99 When MPX is enabled, there are 2 new situations that can generate
102 * new bounds tables (BT) need to be allocated to save bounds.
105 We hook #BR handler to handle these two new situations.
[all …]
|
| /Documentation/filesystems/ |
| D | sharedsubtree.txt | 89 the new mount at /tmp becomes a shared mount and it is a replica of
161 Now any process that clones off a new namespace will have a
179 A new process can clone off a new namespace. And mark some part
365 1. 'A' is a shared mount and 'B' is a shared mount. A new mount 'C'
367 mounted on mount 'B' at dentry 'b'. Also new mount 'C1', 'C2', 'C3' ...
369 propagates to. A new propagation tree containing 'C1',..,'Cn' is
374 2. 'A' is a private mount and 'B' is a shared mount. A new mount 'C'
376 mounted on mount 'B' at dentry 'b'. Also new mount 'C1', 'C2', 'C3' ...
378 propagates to. A new propagation tree is set containing all new mounts
382 3. 'A' is a slave mount of mount 'Z' and 'B' is a shared mount. A new
[all …]
|
| D | ecryptfs.txt | 32 then copy the files back into the new eCryptfs mount to migrate the
38 Create a new directory into which eCryptfs will write its encrypted
47 Try writing a new file:
51 The operation will complete. Notice that there is a new file in
|
| /Documentation/userspace-api/ |
| D | unshare.rst | 4 This document describes the new system call, unshare(). The document
48 shared resources without creating a new process. unshare() is a natural
56 where creating a new process to control sharing/unsharing of process
58 when creating a new process using fork or clone, unshare() can benefit
100 stable code to implement a new feature that may not get exercised
103 the benefits of this new feature can exceed its cost.
118 new context flags without requiring a rebuild of old applications.
119 If and when new context flags are added, unshare() design should allow
137 when a new process is created using fork(2), while other parts,
143 shared execution context without creating a new process.
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | ABI.txt | 11 don't result in breakage. For instance, if a new property is added,
15 new. These guidelines aren't new, but they desperately need to be
24 in the future, we can create a new compatible string. See I.
|
| /Documentation/translations/zh_CN/arm/ |
| D | kernel_user_helpers.txt | 168 int old, new;
172 new = old + val;
173 } while(__kuser_cmpxchg(old, new, ptr));
175 return new;
266 int64_t old, new;
270 new = old + val;
271 } while(__kuser_cmpxchg64(&old, &new, ptr));
273 return new;
|
| /Documentation/networking/ |
| D | skfp.txt | 126 changed in SMT version v2.82. With this new SMT version, the yellow
147 New features:
149 - new pci dma interface
153 New features:
157 New features:
170 New features:
175 New features:
184 - New SMT module included, changing LED functionality
193 New features:
203 New features:
|
| /Documentation/arm/ |
| D | kernel_user_helpers.rst | 32 use new instructions for other purpose.
34 New helpers may be added over time, so an older kernel may be missing some
155 int old, new;
159 new = old + val;
160 } while(__kuser_cmpxchg(old, new, ptr));
162 return new;
251 int64_t old, new;
255 new = old + val;
256 } while(__kuser_cmpxchg64(&old, &new, ptr));
258 return new;
|
| /Documentation/ide/ |
| D | ide-tape.rst | 9 interface, on the other hand, creates new requests, adds them
60 it is recommended that new tape drives will *in addition*
65 ATAPI overlap is likely to be supported in most new ATAPI
66 devices, including new ATAPI cdroms, and thus provides us
68 sharing a (fast) ATA-2 disk with any (slow) new ATAPI device.
|
| /Documentation/media/uapi/v4l/ |
| D | hist-v4l2.rst | 21 another four years and two stable kernel releases until the new API was
32 1998-09-10: New video standard interface.
100 changes to drivers to fully support new compatibility features, see
101 Driver Writer's Guide and v4l2cap.c. Added new control IDs:
134 new value in the integer pointed to by the argument, a common
155 simplify the API by eliminating several ioctls and to allow new and
156 driver private data streams without adding new ioctls.
168 ``VIDIOC_S_OUTPARM``. A ``type`` field in the new struct
175 6. Control enumeration was simplified, and two new control flags were
255 2001-09-17: New YUV formats and the
[all …]
|
| D | planar-apis.rst | 38 Multi-planar API introduces new multi-planar formats. Those formats use
55 New structures for describing multi-planar formats are added: struct
58 Drivers may define new multi-planar formats, which have distinct
62 A new struct :c:type:`v4l2_plane` structure for
64 the new ``m.planes`` field of struct
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 13 4.1. New functions
81 (thread, whole kernel) need to start using all new versions of
88 conditions when the new implementation could be used so that the system
186 3.1 Adding consistency model support to new architectures
189 For adding consistency model support to new architectures, there are a
230 The module includes a new implementation of functions that we want
232 relation between the original and the new implementation. Then there
233 is code that makes the kernel start using the new code when the livepatch
239 4.1. New functions
242 New versions of functions are typically just copied from the original
[all …]
|
12345678910>>...39