Searched +full:boot +full:- +full:enabled (Results 1 – 25 of 267) sorted by relevance
1234567891011
| /Documentation/admin-guide/ |
| D | kernel-parameters.rst | 3 The kernel's command-line parameters
12 The kernel parses parameters from the kernel command line up to "``--``";
16 Everything after "``--``" is passed as an argument to init.
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
43 ----------
52 <cpu number>-<cpu number>
57 <cpu number>,...,<cpu number>-<cpu number>
63 <cpu number>-<cpu number>:<used size>/<group size>
[all …]
|
| D | dynamic-debug-howto.rst | 9 debug-print code to obtain additional kernel information.
22 - source filename
23 - function name
24 - line number (including ranges of line numbers)
25 - module name
26 - format string
27 - class name (as known/declared by each module)
29 NOTE: To actually get the debug-print output on the console, you may
32 Documentation/admin-guide/kernel-parameters.rst.
39 :#> head -n7 /proc/dynamic_debug/control
[all …]
|
| D | efi-stub.rst | 2 The EFI Boot Stub
8 along with the EFI-specific entry point that the firmware loader
9 jumps to are collectively known as the "EFI boot stub", and live in
10 arch/x86/boot/header.S and drivers/firmware/efi/libstub/x86-stub.c,
12 arch/arm/boot/compressed/efi-header.S and
13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
19 and drivers/firmware/efi/libstub/arm64-stub.c.
21 By using the EFI boot stub it's possible to boot a Linux kernel
22 without the use of a conventional EFI boot loader, such as grub or
23 elilo. Since the EFI boot stub performs the jobs of a boot loader, in
[all …]
|
| D | kernel-parameters.txt | 5 avoid prolonged boot times. The lazy option will add
10 at once during boot.
16 force -- enable ACPI if default was off
17 on -- enable ACPI but allow fallback to DT [arm64,riscv64]
18 off -- disable ACPI if default was on
19 noirq -- do not use ACPI for IRQ routing
20 strict -- Be less tolerant of platforms that are not
22 rsdt -- prefer RSDT over (default) XSDT
23 copy_dsdt -- copy DSDT to memory
24 nospcr -- disable console in ACPI SPCR table as
[all …]
|
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 CPUs that were not available during boot to be added to the system later.
15 CPU Hotplug on physical systems - CPUs not present at boot
16 ----------------------------------------------------------
34 boot to discover the system wide supported features. ACPI's MADT GICC
42 CPU Hotplug on virtual systems - CPUs not enabled at boot
43 ---------------------------------------------------------
46 ever have can be described at boot. There are no power-domain considerations
63 that firmware wishes to disable either from boot (or later) should not be
64 ``enabled`` in the MADT GICC structures, but should have the ``online capable``
[all …]
|
| /Documentation/arch/x86/ |
| D | amd-memory-encryption.rst | 1 .. SPDX-License-Identifier: GPL-2.0
19 memory. Private memory is encrypted with the guest-specific key, while shared
20 memory may be encrypted with hypervisor key. When SME is enabled, the hypervisor
36 When SEV is enabled, instruction pages and guest page tables are always treated
39 is operating in 64-bit or 32-bit PAE mode, in all other modes the SEV hardware
52 memory encryption is enabled (this only affects
57 determine if SME is enabled and/or to enable memory encryption::
61 1 = memory encryption features are enabled
78 - Supported:
81 - Enabled:
[all …]
|
| D | zero-page.rst | 1 .. SPDX-License-Identifier: GPL-2.0
6 The additional fields in struct boot_params as a part of 32-bit boot
7 protocol of kernel. These should be filled by bootloader or 16-bit
8 real-mode setup code of the kernel. References/settings to it mainly
40 1EB/001 ALL kbd_status Numlock is enabled
41 1EC/001 ALL secure_boot Secure boot is enabled in the firmware
|
| D | pti.rst | 1 .. SPDX-License-Identifier: GPL-2.0
27 This approach helps to ensure that side-channel attacks leveraging
28 the paging structures do not function when PTI is enabled. It can be
29 enabled by setting CONFIG_MITIGATION_PAGE_TABLE_ISOLATION=y at compile
30 time. Once enabled at compile-time, it can be disabled at boot with
31 the 'nopti' or 'pti=' kernel parameters (see kernel-parameters.txt).
36 When PTI is enabled, the kernel manages two sets of page tables.
43 that any missed kernel->user CR3 switch will immediately crash
49 each CPU's copy of the area a compile-time-fixed virtual address.
65 Protection against side-channel attacks is important. But,
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 6 information for firmware performance data for system boot,
10 boot:
14 loading the OS boot loader into memory.
17 launching the currently loaded OS boot loader
36 since the last full boot sequence.
38 logged since the last full boot sequence,
49 to obtain a copy of the firmware boot splash and
51 by boot splash applications in order to interact with
52 the firmware boot splash in order to avoid jarring
55 image: The image bitmap. Currently a 32-bit BMP.
[all …]
|
| D | sysfs-platform-wilco-ec | 5 Boot on AC is a policy which makes the device boot from S5
43 - In S0, the port will always provide power.
44 - In S0ix, if usb_charge is enabled, then power will be
47 - In S5, if usb_charge is enabled, then power will be supplied
|
| D | evm | 8 HMAC-sha1 value across the extended attributes, storing the
12 an HMAC-sha1 generated locally with a
17 keyring using keyctl, and EVM is then enabled by
26 2 Permit modification of EVM-protected metadata at
28 creation is enabled (deprecated).
50 modification of EVM-protected metadata and
89 as part of the trusted boot. For more information on
92 Documentation/security/keys/trusted-encrypted.rst. Both
94 core/ima-setup) have support for loading keys at boot
106 additional attributes are configured on system boot. Writing
|
| /Documentation/devicetree/bindings/mfd/ |
| D | tps6507x.txt | 4 - compatible: "ti,tps6507x"
5 - reg: I2C slave address
6 - regulators: This is the list of child nodes that specify the regulator
11 The regulator is matched with the regulator-compatible.
13 The valid regulator-compatible values are:
15 - xxx-supply: Input voltage supply regulator.
16 These entries are required if regulators are enabled for a device.
19 If some of input supply is powered through battery or always-on
23 vindcdc1_2-supply: VDCDC1 and VDCDC2 input.
24 vindcdc3-supply : VDCDC3 input.
[all …]
|
| D | tps65910.txt | 4 - compatible: "ti,tps65910" or "ti,tps65911"
5 - reg: I2C slave address
6 - interrupts: the interrupt outputs of the controller
7 - #gpio-cells: number of cells to describe a GPIO, this should be 2.
10 - gpio-controller: mark the device as a GPIO controller
11 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
14 Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
15 - regulators: This is the list of child nodes that specify the regulator
20 The regulator is matched with the regulator-compatible.
22 The valid regulator-compatible values are:
[all …]
|
| /Documentation/arch/powerpc/ |
| D | firmware-assisted-dump.rst | 2 Firmware-Assisted Dump
7 The goal of firmware-assisted dump is to enable the dump of
8 a crashed system, and to do so from a fully-reset system, and
12 - Firmware-Assisted Dump (FADump) infrastructure is intended to replace
14 - Fadump uses the same firmware interfaces and memory reservation model
16 - Unlike phyp dump, FADump exports the memory dump through /proc/vmcore
19 - Unlike phyp dump, userspace tool does not need to refer any sysfs
21 - Unlike phyp dump, FADump allows user to release all the memory reserved
23 - Once enabled through kernel boot parameter, FADump can be
28 Comparing with kdump or other strategies, firmware-assisted
[all …]
|
| D | elfnote.rst | 9 ---------------------
18 - Ultravisor-capable bit (PowerNV only).
20 .. code-block:: c
25 ultravisor-enabled system.
27 In an ultravisor-enabled system, some machine resources are now controlled
28 by the ultravisor. If the kernel is not ultravisor-capable, but it ends up
31 boot trying to set the partition table entry 0.
33 In an ultravisor-enabled system, a bootloader could warn the user or prevent
35 or the Ultravisor-capable bit is not set.
38 ----------
|
| /Documentation/admin-guide/mm/ |
| D | zswap.rst | 10 dynamically allocated RAM-based memory pool. zswap basically trades CPU cycles
11 for potentially reduced swap I/O. This trade-off can also result in a
24 drastically reducing life-shortening writes.
30 Whether Zswap is enabled at the boot time depends on whether
31 the ``CONFIG_ZSWAP_DEFAULT_ON`` Kconfig option is enabled or not.
33 ``zswap.enabled=`` option, for example ``zswap.enabled=0``.
34 Zswap can also be enabled and disabled at runtime using the sysfs interface.
38 echo 1 > /sys/module/zswap/parameters/enabled
62 but it can be overridden at boot time by setting the ``zpool`` attribute,
69 means the compression ratio will always be 2:1 or worse (because of half-full
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 5 LoadPin is a Linux Security Module that ensures all kernel-loaded files
7 the expectation that such a filesystem is backed by a read-only device
8 such as dm-verity or CDROM. This allows systems that have a verified
12 The LSM is selectable at build-time with ``CONFIG_SECURITY_LOADPIN``, and
13 can be controlled at boot-time with the kernel command line option
14 "``loadpin.enforce``". By default, it is enabled, but can be disabled at
15 boot ("``loadpin.enforce=0``").
18 block device backing the filesystem is not read-only, a sysctl is
19 created to toggle pinning: ``/proc/sys/kernel/loadpin/enabled``. (Having
26 as "``loadpin.exclude=kernel-module,kexec-image``". This allows to use
|
| /Documentation/networking/ |
| D | netconsole.rst | 1 .. SPDX-License-Identifier: GPL-2.0
29 It can be used either built-in or as a module. As a built-in,
32 capture of early kernel panics, it does capture most of the boot
41 netconsole=[+][r][src-port]@[src-ip]/[<dev>],[tgt-port]@<tgt-ip>/[tgt-macaddr]
46 src-port source for UDP packets (defaults to 6665)
47 src-ip source IP to use (interface address)
49 tgt-port port for logging agent (6666)
50 tgt-ip IP address for logging agent
51 tgt-macaddr ethernet MAC address for logging agent (broadcast)
71 Built-in netconsole starts immediately after the TCP stack is
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator-max77620.txt | 3 Device has multiple DCDC(sd[0-3] and LDOs(ldo[0-8]). The input supply
6 sub-node "regulators" which is child node of device node.
14 -------------------
18 in-sd0-supply: Input supply for SD0, INA-SD0 or INB-SD0 pins.
19 in-sd1-supply: Input supply for SD1.
20 in-sd2-supply: Input supply for SD2.
21 in-sd3-supply: Input supply for SD3.
22 in-ldo0-1-supply: Input supply for LDO0 and LDO1.
23 in-ldo2-supply: Input supply for LDO2.
24 in-ldo3-5-supply: Input supply for LDO3 and LDO5
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | amlogic,meson-nand.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/amlogic,meson-nand.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - $ref: nand-controller.yaml
13 - liang.yang@amlogic.com
18 - amlogic,meson-gxl-nfc
19 - amlogic,meson-axg-nfc
24 reg-names:
26 - const: nfc
[all …]
|
| /Documentation/PCI/ |
| D | boot-interrupts.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Boot Interrupts
7 :Author: - Sean V Kelley <sean.v.kelley@linux.intel.com>
13 interrupt messages (Assert_INTx/Deassert_INTx). The integrated IO-APIC in a
15 MSI interrupts. If the IO-APIC is disabled (via the mask bits in the
16 IO-APIC table entries), the messages are routed to the legacy PCH. This
17 in-band interrupt mechanism was traditionally necessary for systems that
18 did not support the IO-APIC and for boot. Intel in the past has used the
19 term "boot interrupts" to describe this mechanism. Further, the PCI Express
20 protocol describes this in-band legacy wire-interrupt INTx mechanism for
[all …]
|
| /Documentation/firmware-guide/acpi/ |
| D | debug.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 Compile-time configuration
13 The ACPI CA debug output is globally enabled by CONFIG_ACPI_DEBUG. If this
16 Boot- and run-time configuration
20 you're interested in. At boot-time, use the acpi.debug_layer and
21 acpi.debug_level kernel command line options. After boot, you can use the
32 You can set the debug_layer mask at boot-time using the acpi.debug_layer
33 command line argument, and you can change it after boot by writing values
66 You can set the debug_level mask at boot-time using the acpi.debug_level
67 command line argument, and you can change it after boot by writing values
[all …]
|
| /Documentation/networking/device_drivers/ethernet/cirrus/ |
| D | cs89x0.rst | 1 .. SPDX-License-Identifier: GPL-2.0
33 2.1 CS8900-based Adapter Configuration
34 2.2 CS8920-based Adapter Configuration
46 5.2.1 Diagnostic Self-Test
56 6.5 Kernel boot parameters
66 The CS8900-based ISA Ethernet Adapters from Cirrus Logic follow
67 IEEE 802.3 standards and support half or full-duplex operation in ISA bus
69 in 16-bit ISA or EISA bus expansion slots and are available in
70 10BaseT-only or 3-media configurations (10BaseT, 10Base2, and AUI for 10Base-5
73 CS8920-based adapters are similar to the CS8900-based adapter with additional
[all …]
|
| /Documentation/trace/ |
| D | boottime-trace.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
13 device initialization with full features of ftrace including per-event
14 filter and actions, histograms, kprobe-events and synthetic-events,
19 Options in the Boot Config
22 Here is the list of available options list for boot time tracing in
23 boot config file [1]_. All options are under "ftrace." or "kernel."
27 .. [1] See :ref:`Documentation/admin-guide/bootconfig.rst <bootconfig>`
28 .. [2] See :ref:`Documentation/admin-guide/kernel-parameters.rst <kernelparameters>`
[all …]
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
28 hardware such as x86, x86-64 and PowerPC.
31 physical addresses above 4 GB, but this feature is currently not enabled by
34 Together with a early initialization of the OHCI-1394 controller for debugging,
36 buffer on to debug early boot problems in areas like ACPI where the system
37 fails to boot and other means for debugging (serial port) are either not
[all …]
|
1234567891011