Searched +full:kernel +full:- +full:policy (Results 1 – 25 of 1025) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | security.txt | 6 https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html
13 Targeted policy with perf_event_open() access control capabilities:
15 1. Download selinux-policy SRPM package (e.g. selinux-policy-3.14.4-48.fc31.src.rpm on FC31)
18 # rpm -Uhv selinux-policy-3.14.4-48.fc31.src.rpm
22 # rpmbuild -bp selinux-policy.spec
24 3. Place patch below at rpmbuild/BUILD/selinux-policy-b86eaaf4dbcf2d51dd4432df7185c0eaf3cbcc02
27 # patch -p1 < selinux-policy-perf-events-perfmon.patch
28 patching file policy/flask/access_vectors
29 patching file policy/flask/security_classes
30 # cat selinux-policy-perf-events-perfmon.patch
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | security.txt | 6 https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html
13 Targeted policy with perf_event_open() access control capabilities:
15 1. Download selinux-policy SRPM package (e.g. selinux-policy-3.14.4-48.fc31.src.rpm on FC31)
18 # rpm -Uhv selinux-policy-3.14.4-48.fc31.src.rpm
22 # rpmbuild -bp selinux-policy.spec
24 3. Place patch below at rpmbuild/BUILD/selinux-policy-b86eaaf4dbcf2d51dd4432df7185c0eaf3cbcc02
27 # patch -p1 < selinux-policy-perf-events-perfmon.patch
28 patching file policy/flask/access_vectors
29 patching file policy/flask/security_classes
30 # cat selinux-policy-perf-events-perfmon.patch
[all …]
|
| /kernel/linux/linux-6.6/security/apparmor/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
14 http://apparmor.wiki.kernel.org
43 Set the default value of the apparmor.debug kernel parameter.
45 the kernel message buffer.
48 bool "Allow loaded policy to be introspected"
52 This option selects whether introspection of loaded policy
54 adds to kernel memory usage. It is required for introspection
55 of loaded policy, and check point and restore support. It
66 This option selects whether introspection of loaded policy
69 checking loaded policy. This option adds to policy load
[all …]
|
| /kernel/linux/linux-6.6/security/integrity/ima/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
41 running kernel must be saved and restored on boot.
43 Depending on the IMA policy, the measurement list can grow to
60 Disabling this option will disregard LSM based policy rules.
70 limited to 255 characters. The 'ima-ng' measurement list
76 bool "ima-ng (default)"
78 bool "ima-sig"
83 default "ima-ng" if IMA_NG_TEMPLATE
84 default "ima-sig" if IMA_SIG_TEMPLATE
92 hash algorithm can be overwritten using the kernel command
[all …]
|
| /kernel/linux/linux-5.10/security/integrity/ima/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
41 running kernel must be saved and restored on boot.
43 Depending on the IMA policy, the measurement list can grow to
60 Disabling this option will disregard LSM based policy rules.
70 limited to 255 characters. The 'ima-ng' measurement list
76 bool "ima-ng (default)"
78 bool "ima-sig"
83 default "ima-ng" if IMA_NG_TEMPLATE
84 default "ima-sig" if IMA_SIG_TEMPLATE
92 hash algorithm can be overwritten using the kernel command
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 2 NUMA Memory Policy
5 What is NUMA Memory Policy?
8 In the Linux kernel, "memory policy" determines from which node the kernel will
10 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
11 The current memory policy support was added to Linux 2.6 around May 2004. This
12 document attempts to describe the concepts and APIs of the 2.6 memory policy
16 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
19 programming interface that a NUMA-aware application can take advantage of. When
24 Memory Policy Concepts
28 ------------------------
[all …]
|
| D | hugetlbpage.rst | 9 the Linux kernel. This support is built on top of multiple page size support
13 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
19 Users can use the huge page support in Linux kernel by either using the mmap
22 First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
28 persistent hugetlb pages in the kernel's huge page pool. It also displays
73 ``/sys/kernel/mm/hugepages`` (described below).
77 configured in the kernel.
80 pages in the kernel's huge page pool. "Persistent" huge pages will be
89 Pages that are used as huge pages are reserved inside the kernel and cannot
93 Once a number of huge pages have been pre-allocated to the kernel huge page
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 4 NUMA Memory Policy
7 What is NUMA Memory Policy?
10 In the Linux kernel, "memory policy" determines from which node the kernel will
12 supported platforms with Non-Uniform Memory Access architectures since 2.4.?.
13 The current memory policy support was added to Linux 2.6 around May 2004. This
14 document attempts to describe the concepts and APIs of the 2.6 memory policy
18 (``Documentation/admin-guide/cgroup-v1/cpusets.rst``)
21 programming interface that a NUMA-aware application can take advantage of. When
26 Memory Policy Concepts
30 ------------------------
[all …]
|
| D | hugetlbpage.rst | 11 the Linux kernel. This support is built on top of multiple page size support
15 256M and ppc64 supports 4K and 16M. A TLB is a cache of virtual-to-physical
21 Users can use the huge page support in Linux kernel by either using the mmap
24 First the Linux kernel needs to be built with the CONFIG_HUGETLBFS
30 persistent hugetlb pages in the kernel's huge page pool. It also displays
71 ``/sys/kernel/mm/hugepages`` (described below).
75 configured in the kernel.
78 pages in the kernel's huge page pool. "Persistent" huge pages will be
83 Pages that are used as huge pages are reserved inside the kernel and cannot
87 Once a number of huge pages have been pre-allocated to the kernel huge page
[all …]
|
| /kernel/linux/linux-6.6/security/tomoyo/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
11 This selects TOMOYO Linux, pathname-based access control.
23 that are automatically appended into policy at "learning mode".
36 audit logs that the kernel can hold on memory.
37 You can read the log via /sys/kernel/security/tomoyo/audit.
41 bool "Activate without calling userspace policy loader."
45 Say Y here if you want to activate access control as soon as built-in
46 policy was loaded. This option will be useful for systems where
48 needed before loading the policy. For example, you can activate
49 immediately after loading the fixed part of policy which will allow
[all …]
|
| /kernel/linux/linux-5.10/security/tomoyo/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 This selects TOMOYO Linux, pathname-based access control.
25 that are automatically appended into policy at "learning mode".
38 audit logs that the kernel can hold on memory.
39 You can read the log via /sys/kernel/security/tomoyo/audit.
43 bool "Activate without calling userspace policy loader."
47 Say Y here if you want to activate access control as soon as built-in
48 policy was loaded. This option will be useful for systems where
50 needed before loading the policy. For example, you can activate
51 immediately after loading the fixed part of policy which will allow
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/kexec/ |
| D | test_kexec_file_load.sh | 2 # SPDX-License-Identifier: GPL-2.0
4 # Loading a kernel image via the kexec_file_load syscall can verify either
6 # both signatures depending on the IMA policy, or none.
8 # To determine whether the kernel image is signed, this test depends
9 # on pesign and getfattr. This test also requires the kernel to be
11 # enabled or access to the extract-ikconfig script.
16 trap "{ rm -f $IKCONFIG ; }" EXIT
18 # Some of the IMA builtin policies may require the kexec kernel image to
19 # be signed, but these policy rules may be replaced with a custom
20 # policy. Only CONFIG_IMA_APPRAISE_REQUIRE_KEXEC_SIGS persists after
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kexec/ |
| D | test_kexec_file_load.sh | 2 # SPDX-License-Identifier: GPL-2.0
4 # Loading a kernel image via the kexec_file_load syscall can verify either
6 # both signatures depending on the IMA policy, or none.
8 # To determine whether the kernel image is signed, this test depends
9 # on pesign and getfattr. This test also requires the kernel to be
11 # enabled or access to the extract-ikconfig script.
16 trap "{ rm -f $IKCONFIG ; }" EXIT
18 # Some of the IMA builtin policies may require the kexec kernel image to
19 # be signed, but these policy rules may be replaced with a custom
20 # policy. Only CONFIG_IMA_APPRAISE_REQUIRE_KEXEC_SIGS persists after
[all …]
|
| /kernel/linux/linux-5.10/security/apparmor/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
16 http://apparmor.wiki.kernel.org
27 This option selects whether introspection of loaded policy
31 bool "Enable policy hash introspection by default"
35 This option selects whether sha1 hashing of loaded policy
37 loaded policy provide system administrators a quick way
38 to verify that policy in the kernel matches what is expected,
39 however it can slow down policy load on some devices. In
40 these cases policy hashing can be disabled by default and
68 Set the default value of the apparmor.debug kernel parameter.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
7 latest reference policy release from
11 However, if you want to install a dummy policy for
14 userspace to be installed - in particular you will
15 need checkpolicy to compile a kernel, and setfiles and
18 1. Compile the kernel with selinux enabled.
21 SELinux enabled and a real policy. If
29 Step 4 will create a new dummy policy valid for your
30 kernel, with a single selinux user, role, and type.
31 It will compile the policy, will set your ``SELINUXTYPE`` to
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/LSM/ |
| D | SELinux.rst | 6 to use the distro-provided policies, or install the
7 latest reference policy release from
11 However, if you want to install a dummy policy for
14 userspace to be installed - in particular you will
15 need checkpolicy to compile a kernel, and setfiles and
18 1. Compile the kernel with selinux enabled.
21 SELinux enabled and a real policy. If
29 Step 4 will create a new dummy policy valid for your
30 kernel, with a single selinux user, role, and type.
31 It will compile the policy, will set your ``SELINUXTYPE`` to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | stm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
26 To solve this mapping problem, stm class provides a policy management
28 identifiers to ranges of masters and channels. If these rules (policy)
32 This policy is a tree structure containing rules (policy_node) that
34 associated with it, located in "stp-policy" subsystem directory in
35 configfs. The topmost directory's name (the policy) is formatted as
36 the STM device name to which this policy applies and an arbitrary
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
44 $ cat /config/stp-policy/dummy_stm.my-policy/user/channels
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | stm.rst | 1 .. SPDX-License-Identifier: GPL-2.0
26 To solve this mapping problem, stm class provides a policy management
28 identifiers to ranges of masters and channels. If these rules (policy)
32 This policy is a tree structure containing rules (policy_node) that
34 associated with it, located in "stp-policy" subsystem directory in
35 configfs. The topmost directory's name (the policy) is formatted as
36 the STM device name to which this policy applies and an arbitrary
40 $ ls /config/stp-policy/dummy_stm.my-policy/user
42 $ cat /config/stp-policy/dummy_stm.my-policy/user/masters
44 $ cat /config/stp-policy/dummy_stm.my-policy/user/channels
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
51 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
64 information on the available P-states (or P-state ranges in some cases) and
65 access platform-specific hardware interfaces to change CPU P-states as requested
[all …]
|
| D | intel_pstate.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
40 CPUs. Consequently, if ``intel_pstate`` is in use, every ``CPUFreq`` policy
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
62 depends on what kernel command line options are used and on the capabilities of
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
51 The Linux kernel supports CPU performance scaling by means of the ``CPUFreq``
64 information on the available P-states (or P-state ranges in some cases) and
65 access platform-specific hardware interfaces to change CPU P-states as requested
[all …]
|
| D | intel_pstate.rst | 1 .. SPDX-License-Identifier: GPL-2.0
17 :doc:`CPU performance scaling subsystem <cpufreq>` in the Linux kernel
22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.]
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
40 CPUs. Consequently, if ``intel_pstate`` is in use, every ``CPUFreq`` policy
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
[all …]
|
| /kernel/linux/linux-6.6/drivers/cpufreq/ |
| D | amd-pstate-ut.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * AMD Processor P-state Frequency Driver Unit Test
9 * The AMD P-State Unit Test is a test module for testing the amd-pstate
11 * (SBIOS/Firmware or Hardware). 2) Kernel can have a basic function
12 * test to avoid the kernel regression during the update. 3) We can
19 * See Documentation/admin-guide/pm/amd-pstate.rst Unit Tests for
20 * amd-pstate to get more detail.
25 #include <linux/kernel.h>
29 #include <linux/amd-pstate.h>
35 * amd_pstate_ut: used as a shortform for AMD P-State unit test.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/cpu-freq/ |
| D | core.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Dominik Brodowski <linux@brodo.de>
9 - David Kimdon <dwhedon@debian.org>
10 - Rafael J. Wysocki <rafael.j.wysocki@intel.com>
11 - Viresh Kumar <viresh.kumar@linaro.org>
26 drivers or other part of the kernel that need to be informed of
27 policy changes (ex. thermal modules like ACPI) or of all
30 kernel "constant" loops_per_jiffy is updated on frequency changes
37 policy doesn't get freed while being used.
42 CPUFreq notifiers conform to the standard kernel notifier interface.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/cpu-freq/ |
| D | core.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 - Dominik Brodowski <linux@brodo.de>
9 - David Kimdon <dwhedon@debian.org>
10 - Rafael J. Wysocki <rafael.j.wysocki@intel.com>
11 - Viresh Kumar <viresh.kumar@linaro.org>
26 drivers or other part of the kernel that need to be informed of
27 policy changes (ex. thermal modules like ACPI) or of all
30 kernel "constant" loops_per_jiffy is updated on frequency changes
37 policy doesn't get freed while being used.
42 CPUFreq notifiers conform to the standard kernel notifier interface.
[all …]
|
12345678910>>...41