| /linux/tools/testing/selftests/net/ |
| H A D | xfrm_policy_add_speed.sh | 23 local policies
26 policies=0
38 policies=$((policies+1))
39 [ "$policies" -gt "$max" ] && return
43 policies=$((policies+1))
44 [ "$policies" -gt "$max" ] && return
67 policies=$(wc -l < "$tmp")
68 printf "Inserted %-06s policies in $result ms\n" $policies
71 if [ "$have" -ne "$policies" ]; then
72 echo "WARNING: mismatch, have $have policies, expected $policies"
|
| /linux/net/netlink/ |
| H A D | policy.c | 24 } policies[] __counted_by(n_alloc); member
38 if (state->policies[i].policy == policy && in add_policy()
39 state->policies[i].maxtype == maxtype) in add_policy()
42 if (!state->policies[i].policy) { in add_policy()
43 state->policies[i].policy = policy; in add_policy()
44 state->policies[i].maxtype = maxtype; in add_policy()
50 state = krealloc(state, struct_size(state, policies, n_alloc), in add_policy()
57 memset(&state->policies[old_n_alloc], 0, in add_policy()
58 flex_array_size(state, policies, n_alloc - old_n_alloc)); in add_policy()
60 state->policies[old_n_alloc].policy = policy; in add_policy()
[all …]
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | xe_guc_ads.c | 112 struct guc_policies policies; member
447 ads_blob_write(ads, policies.dpc_promote_time, in guc_policies_init()
449 ads_blob_write(ads, policies.max_num_work_items, in guc_policies_init()
455 ads_blob_write(ads, policies.global_flags, global_flags); in guc_policies_init()
456 ads_blob_write(ads, policies.is_valid, 1); in guc_policies_init()
883 offsetof(struct __guc_ads_blob, policies)); in xe_guc_ads_populate_minimal()
917 offsetof(struct __guc_ads_blob, policies)); in xe_guc_ads_populate()
993 struct guc_policies *policies; in xe_guc_ads_scheduler_policy_toggle_reset() local
995 CLASS(xe_guc_buf, buf)(&guc->buf, sizeof(*policies)); in xe_guc_ads_scheduler_policy_toggle_reset()
1000 policies = xe_guc_buf_cpu_ptr(buf); in xe_guc_ads_scheduler_policy_toggle_reset()
[all …]
|
| /linux/tools/testing/selftests/amd-pstate/ |
| H A D | run.sh | 77 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
78 for policy in $policies; do
90 policies=$(awk '{print $1}' $OUTFILE.backup_governor.log)
91 for policy in $policies; do
105 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
106 for policy in $policies; do
|
| /linux/tools/testing/selftests/cpufreq/ |
| H A D | cpufreq.sh | 31 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
32 for policy in $policies; do
39 policies=$(ls $CPUFREQROOT| grep "policy[0-9].*")
40 for policy in $policies; do
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | numa_memory_policy.rst | 15 Memory policies should not be confused with cpusets
18 memory may be allocated by a set of processes. Memory policies are a
20 both cpusets and policies are applied to a task, the restrictions of the cpuset
61 In a multi-threaded task, task policies apply only to the thread
88 VMA policies have a few complicating details:
100 * VMA policies are shared between all tasks that share a
103 fork(). However, because VMA policies refer to a specific
105 space is discarded and recreated on exec*(), VMA policies
107 applications may use VMA policies.
123 Conceptually, shared policies apply to "memory objects" mapped
[all …]
|
| /linux/security/ipe/ |
| H A D | Kconfig | 30 is deployed via the $securityfs/ipe/policies/$policy_name/active
61 policies. The property evaluates to TRUE when a file from a dm-verity
70 policies. The property evaluates to TRUE when a file from a dm-verity
81 policies. The property evaluates to TRUE when a file is fsverity
92 policies. The property evaluates to TRUE when a file is fsverity
|
| /linux/Documentation/admin-guide/ |
| H A D | nvme-multipath.rst | 7 This document describes NVMe multipath and its path selection policies supported
19 Different policies result in different path selections.
25 All policies follow the ANA (Asymmetric Namespace Access) mechanism, meaning
27 one. Current the NVMe multipath policies include numa(default), round-robin and
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | ipe.rst | 28 unchangeable over time. For example, IPE policies can be crafted to trust
35 integrity and trust. For example, IPE allows the definition of policies
39 checks, allowing IPE to enforce policies that trust files protected by
165 uniquely identify policies to deploy new policies vs update existing
166 policies.
205 preserve older policies being compatible with newer kernels that can introduce
210 enforcing the configurable policies at startup, around reading and
234 Policies can be deployed from userspace through securityfs. These policies
236 authorization of the policies (prohibiting an attacker from gaining
238 policies must be signed by a certificate that chains to the
[all …]
|
| H A D | SELinux.rst | 17 to use the distro-provided policies, or install the
|
| /linux/tools/perf/trace/beauty/ |
| H A D | sched_policy.c | 22 const char *policies[] = { in syscall_arg__scnprintf_sched_policy() local
31 printed = scnprintf(bf, size, "%s%s", show_prefix ? prefix : "", policies[policy]); in syscall_arg__scnprintf_sched_policy()
|
| /linux/Documentation/filesystems/ |
| H A D | fscrypt.rst | 171 Limitations of v1 policies
174 v1 encryption policies have some weaknesses with respect to online
190 All the above problems are fixed with v2 encryption policies. For
192 policies on all new encrypted directories.
239 the key is used for v1 encryption policies or for v2 encryption
240 policies. Users **must not** use the same key for both v1 and v2
241 encryption policies. (No real-world attack is currently known on this
245 For v1 encryption policies, the KDF only supports deriving per-file
251 For v2 encryption policies, the KDF is HKDF-SHA512. The master key is
286 DIRECT_KEY policies
[all …]
|
| /linux/drivers/gpu/drm/i915/gt/uc/ |
| H A D | intel_guc_ads.c | 64 struct guc_policies policies; member
167 ads_blob_write(guc, policies.dpc_promote_time, in guc_policies_init()
169 ads_blob_write(guc, policies.max_num_work_items, in guc_policies_init()
175 ads_blob_write(guc, policies.global_flags, global_flags); in guc_policies_init()
176 ads_blob_write(guc, policies.is_valid, 1); in guc_policies_init()
187 ads_blob_read(guc, policies.dpc_promote_time)); in intel_guc_ads_print_policy_info()
189 ads_blob_read(guc, policies.max_num_work_items)); in intel_guc_ads_print_policy_info()
191 ads_blob_read(guc, policies.global_flags)); in intel_guc_ads_print_policy_info()
925 offsetof(struct __guc_ads_blob, policies)); in __guc_ads_init()
|
| /linux/kernel/ |
| H A D | Kconfig.preempt | 175 allows scheduling policies to be implemented as BPF programs to
179 iteration of new scheduling policies.
181 implement policies that are not applicable to general-purpose
184 scheduling policies in production environments.
188 wish to implement scheduling policies. The struct_ops structure
|
| /linux/drivers/net/wireless/silabs/wfx/ |
| H A D | data_tx.c | 152 struct wfx_tx_policy *policies = wvif->tx_policy_cache.cache; in wfx_tx_policy_upload() local
159 is_used = memzcmp(policies[i].rates, sizeof(policies[i].rates)); in wfx_tx_policy_upload()
160 if (!policies[i].uploaded && is_used) in wfx_tx_policy_upload()
164 policies[i].uploaded = true; in wfx_tx_policy_upload()
165 memcpy(tmp_rates, policies[i].rates, sizeof(tmp_rates)); in wfx_tx_policy_upload()
|
| /linux/Documentation/security/ |
| H A D | ipe.rst | 153 The first issue is one of code maintenance and duplication. To author policies,
164 and the original file itself to try to understand what policies have been deployed
165 on this system and what policies have not. For a single user, this may be alright,
166 as old policies can be discarded almost immediately after the update takes hold.
169 this quickly becomes an issue, as stale policies from years ago may be present,
243 policies to be updated without updating the kernel).
270 minimum required version across all policies that can be active on
277 need to be aware of this, and ensure the new secure policies are
288 that were critical to its function. In this system, three types of policies
357 policies.
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 2 Guidance for writing policies
7 makes it easier to write the policies.
26 Overview of supplied cache replacement policies
|
| H A D | index.rst | 8 cache-policies
|
| /linux/Documentation/ABI/removed/ |
| H A D | raw1394 | 7 to implement sensible device security policies, and its low level
|
| /linux/Documentation/bpf/ |
| H A D | map_sockmap.rst | 89 This helper is used in programs implementing policies at the socket level. If
169 This helper is used in programs implementing policies at the socket level. If
185 This helper is used in programs implementing policies at the skb socket level.
201 For socket policies, apply the verdict of the BPF program to the next (number
221 For socket policies, prevent the execution of the verdict BPF program for
236 For socket policies, pull in non-linear data from user space for ``msg`` and set
|
| /linux/drivers/acpi/dptf/ |
| H A D | Kconfig | 11 a coordinated approach for different policies to effect the hardware
|
| /linux/security/landlock/ |
| H A D | Kconfig | 11 tailored access control policies. A Landlock security policy is a
|
| /linux/Documentation/userspace-api/media/mediactl/ |
| H A D | media-controller-intro.rst | 31 implementing policies that belong to userspace.
|
| /linux/Documentation/ABI/testing/ |
| H A D | configfs-stp-policy | 5 This group contains policies mandating Master/Channel allocation
|
| /linux/Documentation/process/ |
| H A D | index.rst | 80 policies around the handling of a couple of special classes of bugs:
|