/linux-6.12.1/tools/testing/selftests/openat2/ |
D | openat2_test.c | 159 struct open_how how; member 170 .how.flags = O_TMPFILE | O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags() 172 .how.flags = O_TMPFILE | O_CREAT | O_RDWR, .err = -EINVAL }, in test_openat2_flags() 176 .how.flags = O_PATH | O_CLOEXEC }, in test_openat2_flags() 178 .how.flags = O_PATH | O_DIRECTORY }, in test_openat2_flags() 180 .how.flags = O_PATH | O_NOFOLLOW }, in test_openat2_flags() 183 .how.flags = O_PATH | O_RDWR, .err = -EINVAL }, in test_openat2_flags() 185 .how.flags = O_PATH | O_CREAT, .err = -EINVAL }, in test_openat2_flags() 187 .how.flags = O_PATH | O_EXCL, .err = -EINVAL }, in test_openat2_flags() 189 .how.flags = O_PATH | O_NOCTTY, .err = -EINVAL }, in test_openat2_flags() [all …]
|
D | resolve_test.c | 113 struct open_how how; member 139 .path = "/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 142 .path = "cheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 145 .path = "abscheeky/absself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 148 .path = "..", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 151 .path = "../root/", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 154 .path = "cheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 157 .path = "abscheeky/self", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 160 .path = "cheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() 163 .path = "abscheeky/garbageself", .how.resolve = RESOLVE_BENEATH, in test_openat2_opath_tests() [all …]
|
D | helpers.c | 17 bool needs_openat2(const struct open_how *how) in needs_openat2() argument 19 return how->resolve != 0; in needs_openat2() 22 int raw_openat2(int dfd, const char *path, void *how, size_t size) in raw_openat2() argument 24 int ret = syscall(__NR_openat2, dfd, path, how, size); in raw_openat2() 28 int sys_openat2(int dfd, const char *path, struct open_how *how) in sys_openat2() argument 30 return raw_openat2(dfd, path, how, sizeof(*how)); in sys_openat2() 33 int sys_openat(int dfd, const char *path, struct open_how *how) in sys_openat() argument 35 int ret = openat(dfd, path, how->flags, how->mode); in sys_openat() 98 struct open_how how = {}; in init() local 104 fd = sys_openat2(AT_FDCWD, ".", &how); in init()
|
D | helpers.h | 28 * Arguments for how openat2(2) should open the target path. If @resolve is 48 bool needs_openat2(const struct open_how *how); 51 /* how->resolve flags for openat2(2). */ 96 int raw_openat2(int dfd, const char *path, void *how, size_t size); 97 int sys_openat2(int dfd, const char *path, struct open_how *how); 98 int sys_openat(int dfd, const char *path, struct open_how *how);
|
/linux-6.12.1/fs/autofs/ |
D | expire.c | 12 unsigned long timeout, unsigned int how) in autofs_can_expire() argument 20 if (!(how & AUTOFS_EXP_IMMEDIATE)) { in autofs_can_expire() 30 struct dentry *dentry, unsigned int how) in autofs_mount_busy() argument 52 if (how & AUTOFS_EXP_FORCED) { in autofs_mount_busy() 150 unsigned int how) in autofs_direct_busy() argument 155 if (how & AUTOFS_EXP_FORCED) in autofs_direct_busy() 169 if (!autofs_can_expire(top, timeout, how)) in autofs_direct_busy() 182 unsigned int how) in autofs_tree_busy() argument 204 if (autofs_mount_busy(mnt, p, how)) { in autofs_tree_busy() 228 if (how & AUTOFS_EXP_FORCED) in autofs_tree_busy() [all …]
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-kernel-mm-ksm | 19 full_scans: how many times all mergeable areas have been 22 pages_shared: how many shared pages are being used. 24 pages_sharing: how many more sites are sharing them i.e. how 27 pages_to_scan: how many present pages to scan before ksmd goes 30 pages_unshared: how many pages unique but repeatedly checked 33 pages_volatile: how many pages changing too fast to be placed 41 sleep_millisecs: how many milliseconds ksm should sleep between 59 Description: Measure how effective KSM is. 60 general_profit: how effective is KSM. The formula for the
|
D | sysfs-kernel-slab | 19 The aliases file is read-only and specifies how many caches 48 The alloc_fastpath file shows how many objects have been 59 The alloc_from_partial file shows how many times a cpu slab has 71 The alloc_refill file shows how many times the per-cpu freelist 82 The alloc_slab file is shows how many times a new slab had to 93 The alloc_slowpath file shows how many objects have been 115 The cpu_slabs file is read-only and displays how many cpu slabs 124 The file cpuslab_flush shows how many times a cache's cpu slabs 147 The deactivate_empty file shows how many times an empty cpu slab 157 The deactivate_full file shows how many times a full cpu slab [all …]
|
/linux-6.12.1/Documentation/admin-guide/mm/ |
D | ksm.rst | 80 how many pages to scan before ksmd goes to sleep 89 how many milliseconds ksmd should sleep before next scan 102 sharing of setting 1 (default). You may wish to compare how 154 specifies how frequently KSM checks the metadata of the pages 165 skipped. How often these pages are skipped depends on how often 167 optimization is enabled. The ``pages_skipped`` metric shows how 174 The section about ``advisor`` explains in detail how the scan time 196 how effective is KSM. The calculation is explained below. 198 how many pages are being scanned for ksm 200 how many shared pages are being used [all …]
|
/linux-6.12.1/io_uring/ |
D | openclose.c | 24 struct open_how how; member 47 return open->how.flags & (O_TRUNC | O_CREAT | __O_TMPFILE); in io_openat_force_async() 61 /* open.how should be already initialised */ in __io_openat_prep() 62 if (!(open->how.flags & O_PATH) && force_o_largefile()) in __io_openat_prep() 63 open->how.flags |= O_LARGEFILE; in __io_openat_prep() 75 if (open->file_slot && (open->how.flags & O_CLOEXEC)) in __io_openat_prep() 91 open->how = build_open_how(flags, mode); in io_openat_prep() 98 struct open_how __user *how; in io_openat2_prep() local 102 how = u64_to_user_ptr(READ_ONCE(sqe->addr2)); in io_openat2_prep() 107 ret = copy_struct_from_user(&open->how, sizeof(open->how), how, len); in io_openat2_prep() [all …]
|
/linux-6.12.1/drivers/net/ethernet/intel/ |
D | Kconfig | 50 adapters. For more information on how to identify your adapter, go 69 use the regular e1000 driver For more information on how to 98 adapters. For more information on how to identify your adapter, go 134 information on how to identify your adapter, go to the Adapter & 153 adapters. For more information on how to identify your adapter, go 205 Intel(R) ixgbe driver. For more information on how to identify your 235 devices. For more information on how to identify your adapter, go 270 information on how to identify your adapter, go to the Adapter 298 devices. For more information on how to identify your adapter, go 351 Interface. For more information on how to identify your adapter, [all …]
|
/linux-6.12.1/security/smack/ |
D | Kconfig | 14 If you are unsure how to answer this question, answer N. 32 If you are unsure how to answer this question, answer N. 43 If you are unsure how to answer this question, answer N. 55 If you are unsure how to answer this question, answer N.
|
/linux-6.12.1/fs/ |
D | open.c | 1201 struct open_how how = { in build_open_how() local 1207 if (how.flags & O_PATH) in build_open_how() 1208 how.flags &= O_PATH_FLAGS; in build_open_how() 1210 if (!WILL_CREATE(how.flags)) in build_open_how() 1211 how.mode = 0; in build_open_how() 1212 return how; in build_open_how() 1215 inline int build_open_flags(const struct open_how *how, struct open_flags *op) in build_open_flags() argument 1217 u64 flags = how->flags; in build_open_flags() 1239 if (how->resolve & ~VALID_RESOLVE_FLAGS) in build_open_flags() 1243 if ((how->resolve & RESOLVE_BENEATH) && (how->resolve & RESOLVE_IN_ROOT)) in build_open_flags() [all …]
|
/linux-6.12.1/security/ |
D | Kconfig | 20 If you are unsure how to answer this question, answer N. 65 If you are unsure how to answer this question, answer N. 73 If you are unsure how to answer this question, answer N. 82 If you are unsure how to answer this question, answer N. 91 If you are unsure how to answer this question, answer N. 104 If you are unsure how to answer this question, answer N. 113 If you are unsure how to answer this question, answer N. 140 See Documentation/arch/x86/intel_txt.rst for a description of how to enable
|
/linux-6.12.1/Documentation/process/ |
D | howto.rst | 7 instructions on how to become a Linux kernel developer and how to learn 20 So, you want to learn how to become a Linux kernel developer? Or you 24 and hints on how to work with the community. It will also try to 49 Please remember that you are trying to learn how to work with the 64 rules and how to use `SPDX <https://spdx.org/>`_ identifiers in source code are 79 invaluable for learning how to interact with the kernel community. When 81 documentation files are also added which explain how to use the feature. 108 This file describes in explicit detail how to successfully create 119 Other excellent descriptions of how to create patches properly are: 146 This document describes how Linux kernel maintainers operate and the [all …]
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen1/ |
D | floating-point.json | 6 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 13 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 20 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 27 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 34 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 41 …s dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 48 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 55 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 62 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli… 69 …) dispatched to each of the 4 FPU execution pipelines. This event reflects how busy the FPU pipeli…
|
/linux-6.12.1/Documentation/driver-api/virtio/ |
D | virtio.rst | 47 reference definitions of virtqueues and "Virtqueues and virtio ring: How 48 the data travels" blog post (`[2]`_) for an illustrated overview of how 77 How a virtio device is found and configured by the kernel depends on how 140 _`[2]` Virtqueues and virtio ring: How the data travels 141 https://www.redhat.com/en/blog/virtqueues-and-virtio-ring-how-data-travels
|
/linux-6.12.1/Documentation/bpf/ |
D | map_array.rst | 106 This snippet shows how to declare an array in a BPF program. 118 This example BPF program shows how to access an array element. 145 This snippet shows how to create an array, using ``bpf_map_create_opts`` to 167 This snippet shows how to initialize the elements of an array. 187 This snippet shows how to retrieve an element value from an array. 210 This snippet shows how to initialize the elements of a per CPU array. 232 This snippet shows how to access the per CPU elements of an array value.
|
/linux-6.12.1/samples/ |
D | Kconfig | 67 different kobject sample modules showing how to use kobjects, 101 different kfifo sample modules showing how to use the 110 Build an example of how to dynamically add the hello 120 Build an QMI client sample driver, which demonstrates how to 127 Build an rpmsg client sample driver, which demonstrates how 278 This demonstrates how a user may create their own CoreSight
|
/linux-6.12.1/Documentation/gpu/ |
D | automated_testing.rst | 21 can be used as well for testing the DRM subsystem. This document explains how 92 How to enable automated testing on your tree 113 How to update test expectations 122 How to expand coverage 134 How to test your changes to the scripts 143 How to incorporate external fixes in your testing 155 How to deal with automated testing labs that may be down
|
/linux-6.12.1/include/linux/ |
D | map_benchmark.h | 23 __u32 threads; /* how many threads will do map/unmap in parallel */ 24 __u32 seconds; /* how long the test will last */ 29 __u32 granule; /* how many PAGE_SIZE will do map/unmap once a time */
|
/linux-6.12.1/Documentation/filesystems/nfs/ |
D | knfsd-stats.rst | 49 Counts how many NFS packets have arrived. More precisely, this 59 of how much CPU load is being placed on the sunrpc server layer 63 Counts how many times an NFS transport is enqueued to wait for 79 Counts how many times an idle nfsd thread is woken to try to 88 Counts how many times an nfsd thread triggered an idle timeout,
|
/linux-6.12.1/Documentation/driver-api/gpio/ |
D | intro.rst | 9 The documents in this directory give detailed instructions on how to access 10 GPIOs in drivers, and how to write a driver for a device that provides GPIOs 32 firmware knowing how they're used). 37 options about how that value is driven, so that for example only one 110 example, that's how I2C clocks are stretched: a slave that needs a slower clock
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | vidioc-subdev-enum-mbus-code.rst | 119 See :ref:`v4l2-mbus-format` on how to do this. 126 See :ref:`v4l2-mbus-format` on how to do this. 133 See :ref:`v4l2-mbus-format` on how to do this. 140 See :ref:`v4l2-mbus-format` on how to do this. 147 See :ref:`v4l2-mbus-format` on how to do this.
|
/linux-6.12.1/Documentation/mm/damon/ |
D | design.rst | 19 To know how user-space can do the configurations and start/stop DAMON, refer to 71 describe how those work. 77 To know how user-space can do the configuration via :ref:`DAMON sysfs interface 154 To know how user-space can set the attributes via :ref:`DAMON sysfs interface 162 The output of DAMON says what pages are how frequently accessed for a given 237 By analyzing the monitoring results, users can also find how long the current 306 To know how user-space can set ``apply_interval`` via :ref:`DAMON sysfs 358 To know how user-space can set the action via :ref:`DAMON sysfs interface 375 To know how user-space can set the access pattern via :ref:`DAMON sysfs 398 To know how user-space can set the basic quotas via :ref:`DAMON sysfs interface [all …]
|
/linux-6.12.1/tools/perf/util/ |
D | ordered-events.c | 267 static int __ordered_events__flush(struct ordered_events *oe, enum oe_flush how, in __ordered_events__flush() argument 284 switch (how) { in __ordered_events__flush() 321 str[how], oe->nr_events); in __ordered_events__flush() 327 if (how == OE_FLUSH__ROUND) in __ordered_events__flush() 330 oe->last_flush_type = how; in __ordered_events__flush() 334 str[how], oe->nr_events); in __ordered_events__flush() 340 int ordered_events__flush(struct ordered_events *oe, enum oe_flush how) in ordered_events__flush() argument 342 return __ordered_events__flush(oe, how, 0); in ordered_events__flush()
|