| /linux-6.12.1/Documentation/firmware-guide/acpi/ |
| D | chromeos-acpi-device.rst | 4 Chrome OS ACPI Device
7 Hardware functionality specific to Chrome OS is exposed through a Chrome OS ACPI device.
8 The plug and play ID of a Chrome OS ACPI device is GGL0001 and the hardware ID is
19 - Chrome OS switch positions
22 - Chrome OS hardware ID
25 - Chrome OS firmware version
28 - Chrome OS read-only firmware version
31 - Chrome OS boot information
34 - Chrome OS GPIO assignments
37 - Chrome OS NVRAM locations
[all …]
|
| D | osi.rst | 24 but where Linux was installed to replace the original OS (Windows or OSX).
71 interpreter in the kernel would return to it a string identifying the OS:
77 The idea was on a platform tasked with running multiple OS's,
78 the BIOS could use _OS to enable devices that an OS
80 necessary to make the platform compatible with that pre-existing OS.
83 of every possible version of the OS that would run on it, and needed to know
84 all the quirks of those OS's. Certainly it would make more sense
85 for the BIOS to ask *specific* things of the OS, such
102 and asks the OS: "YES/NO, are you compatible with this interface?"
104 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
[all …]
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-class-mic | 9 Integrated Core (MIC) architecture that runs a Linux OS.
42 MIC device in the context of the card OS. Possible values that
47 "ready" The MIC device is ready to boot the card OS.
52 "booting" The MIC device has initiated booting a card OS.
54 "shutting_down" The card OS is shutting down.
60 operations depending upon the current state of the card OS.
65 "boot" Boot the card OS image specified by the combination
69 "shutdown" Initiates card OS shutdown.
77 An Intel MIC device runs a Linux OS during its operation. This
78 OS can shutdown because of various reasons. When read, this
[all …]
|
| D | sysfs-driver-ppi | 31 executed in the pre-OS environment. It is the only input from
32 the OS to the pre-OS environment. The request should be an
60 operation to be executed in the pre-OS environment by the BIOS
71 operation to be executed in the pre-OS environment by the BIOS
|
| D | sysfs-firmware-acpi | 14 loading the OS boot loader into memory.
17 launching the currently loaded OS boot loader
20 point when the OS loader calls the
24 just prior to the OS loader gaining control
29 OS write to SLP_TYP upon entry to S3. In
42 handoff to the OS waking vector. In nanoseconds.
48 The BGRT is an ACPI 5.0 feature that allows the OS
112 OS context. GPE 0x12, for example, would vector
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | guest-files.txt | 4 Guest OS /proc/kallsyms file copy. perf reads it to get guest
5 kernel symbols. Users copy it out from guest OS.
8 Guest OS /proc/modules file copy. perf reads it to get guest
9 kernel module information. Users copy it out from guest OS.
12 Guest OS kernel vmlinux.
|
| D | guestmount.txt | 2 Guest OS root file system mount directory. Users mount guest OS
5 For example, start 2 guest OS, one's pid is 8888 and the other's is 9999:
|
| /linux-6.12.1/fs/hpfs/ |
| D | Kconfig | 3 tristate "OS/2 HPFS file system support"
8 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
9 is the file system used for organizing files on OS/2 hard disk
11 write files to an OS/2 HPFS partition on your hard drive. OS/2
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | hpfs.rst | 49 When to mark filesystem dirty so that OS/2 checks it.
63 As in OS/2, filenames are case insensitive. However, shell thinks that names
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
78 On HPFS partitions, OS/2 can associate to each file a special information called
81 variable length. OS/2 stores window and icon positions and file types there. So
107 incompatible with OS/2. OS/2 PmShell symlinks are not supported because they are
118 file has a pointer to codepage its name is in. However OS/2 was created in
120 support is quite buggy. I have Czech OS/2 working in codepage 852 on my disk.
121 Once I booted English OS/2 working in cp 850 and I created a file on my 852
123 Czech OS/2, the file was completely inaccessible under any name. It seems that
[all …]
|
| D | adfs.rst | 25 on a RISC OS Filecore filesystem, but will allow the data within files
45 the RISC OS file type will be added. Default 0.
95 RISC OS file type suffix
98 RISC OS file types are stored in bits 19..8 of the file load address.
100 To enable non-RISC OS systems to be used to store files without losing
104 naming convention is now also used by RISC OS emulators such as RPCEmu.
|
| /linux-6.12.1/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 31 and is waiting to be emptied and processed by the OS. A "not-in-use"
35 During normal operation, on device startup, the OS (specifically, the
39 buffers, and marks them "full". The OS follows up, taking the full
43 and "tail" pointers, managed by the OS, and a hardware current
54 descr. The OS will process this descr, and then mark it "not-in-use",
59 The OS will then note that the current tail is "empty", and halt
64 a "not-in-use" descr. The OS will perform various housekeeping duties
66 dma-mapping it so as to make it visible to the hardware. The OS will
71 pointer, at which point the OS will notice that the head descr is
116 As long as the OS can empty out the RX buffers at a rate faster than
[all …]
|
| /linux-6.12.1/Documentation/PCI/ |
| D | acpi-info.rst | 8 OS might use unless there's another way for the OS to find it [1, 2].
17 described via ACPI. The OS can discover them via the standard PCI
25 namespace [2]. The _CRS is like a generalized PCI BAR: the OS can read
27 a driver for the device [3]. That's important because it means an old OS
28 can work correctly even on a system with new devices unknown to the OS.
29 The new devices might not do anything, but the OS can at least make sure no
33 reserving address space. The static tables are for things the OS needs to
35 is defined, an old OS needs to operate correctly even though it ignores the
37 OS; a static table does not.
39 If the OS is expected to manage a non-discoverable device described via
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 2 Reducing OS jitter due to per-cpu kthreads
6 options to control their OS jitter. Note that non-per-CPU kthreads are
7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind
26 - In order to locate kernel-generated OS jitter on CPU N:
43 To reduce its OS jitter, do any of the following:
62 To reduce its OS jitter, do the following:
73 To reduce its OS jitter, do one of the following:
87 To reduce its OS jitter, each softirq vector must be handled
202 housekeeping CPUs, which can tolerate OS jitter.
228 To reduce its OS jitter, do any of the following:
[all …]
|
| /linux-6.12.1/Documentation/userspace-api/ |
| D | dcdbas.rst | 11 power off after OS shutdown) on certain Dell systems.
55 to perform a power cycle or power off of the system after the OS has finished
57 a driver perform a SMI after the OS has finished shutting down.
73 4) Initiate OS shutdown.
74 (Driver will perform host control SMI when it is notified that the OS
|
| /linux-6.12.1/Documentation/virt/hyperv/ |
| D | coco.rst | 53 guest OS with no knowledge of memory encryption or other aspects of CoCo VMs
56 aspects of CoCo VMs are handled by the Hyper-V paravisor while the guest OS
59 paravisor, and there is no standardized mechanism for a guest OS to query the
61 the paravisor provides is hard-coded in the guest OS.
72 and must be trusted by the guest OS. By implication, the hypervisor/VMM must
79 * With AMD SEV-SNP processors, in fully-enlightened mode the guest OS runs in
81 guest OS runs in VMPL 2 and the paravisor runs in VMPL 0. The paravisor
82 running in VMPL 0 has privileges that the guest OS in VMPL 2 does not have.
84 paravisor mode the guest OS operates in "virtual Top Of Memory" (vTOM) mode
88 * With Intel TDX processor, in fully-enlightened mode the guest OS runs in an
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 61 be used to pass data to the Secure OS. Only the properties defined
64 - stdout-path : specifies the device to be used by the Secure OS for
67 present, the Secure OS should not perform any console output. If
68 /secure-chosen does not exist, the Secure OS should use the value of
70 Normal world OS).
|
| /linux-6.12.1/arch/alpha/include/asm/ |
| D | core_t2.h | 578 #define IOPORT(OS, NS) \ argument
582 return t2_read##OS(xaddr); \
584 return t2_in##OS((unsigned long)xaddr - T2_IO); \
589 t2_write##OS(b, xaddr); \
591 t2_out##OS(b, (unsigned long)xaddr - T2_IO); \
|
| /linux-6.12.1/net/smc/ |
| D | Kconfig | 25 bool "SMC intra-OS shortcut with loopback-ism"
31 when communication occurs within the same OS. This helps in
|
| /linux-6.12.1/Documentation/timers/ |
| D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for
83 1,500 OS instances might find that half of its CPU time was consumed by
202 So you enable all the OS-jitter features described in this document,
204 your workload isn't affected that much by OS jitter, or is it because
206 by providing a simple OS-jitter test suite, which is available on branch
213 whether or not you have succeeded in removing OS jitter from your system.
214 If this trace shows that you have removed OS jitter as much as is
216 sensitive to OS jitter.
219 We do not currently have a good way to remove OS jitter from single-CPU
286 of OS jitter, including interrupts and system-utility tasks
[all …]
|
| /linux-6.12.1/Documentation/devicetree/bindings/remoteproc/ |
| D | st-rproc.txt | 6 Co-processors can be controlled from the bootloader or the primary OS. If
7 the bootloader starts a co-processor, the primary OS must detect its state
|
| /linux-6.12.1/Documentation/driver-api/mei/ |
| D | iamt.rst | 18 - OS updates
79 Intel AMT OS Health Watchdog
82 The Intel AMT Watchdog is an OS Health (Hang/Crash) watchdog.
83 Whenever the OS hangs or crashes, Intel AMT will send an event
|
| /linux-6.12.1/Documentation/livepatch/ |
| D | module-elf-format.rst | 34 selected from OS-specific ranges according to the definitions from glibc.
168 SHF_RELA_LIVEPATCH flag ("o" - for OS-specific).
231 94: 0000000000000000 0 NOTYPE GLOBAL DEFAULT OS [0xff20] .klp.sym.vmlinux.printk,0
282 73: 0000000000000000 0 NOTYPE GLOBAL DEFAULT OS [0xff20] .klp.sym.vmlinux.snprintf,0
283 74: 0000000000000000 0 NOTYPE GLOBAL DEFAULT OS [0xff20] .klp.sym.vmlinux.capable,0
284 75: 0000000000000000 0 NOTYPE GLOBAL DEFAULT OS [0xff20] .klp.sym.vmlinux.find_next_bit,0
285 76: 0000000000000000 0 NOTYPE GLOBAL DEFAULT OS [0xff20] .klp.sym.vmlinux.si_swapinfo,0
292 "OS" means OS-specific.
|
| /linux-6.12.1/Documentation/tee/ |
| D | amd-tee.rst | 38 | API | | | | | OS |
53 The TEE commands supported by AMD-TEE Trusted OS are:
64 AMD-TEE Trusted OS is the firmware running on AMD Secure Processor.
|
| /linux-6.12.1/Documentation/translations/zh_CN/process/ |
| D | embargoed-hardware-issues.rst | 15 所有操作系统（“OS”），因此需要在不同的OS供应商、发行版、硬件供应商和其他各方
|
| /linux-6.12.1/Documentation/translations/zh_TW/process/ |
| D | embargoed-hardware-issues.rst | 18 所有操作系統（“OS”），因此需要在不同的OS供應商、發行版、硬件供應商和其他各方
|