Searched +full:0 +full:x86 (Results 1 – 25 of 215) sorted by relevance
123456789
| /Documentation/arch/x86/ |
| D | entry_64.rst | 8 arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
13 The x86 architecture has quite a few different ways to jump into
15 arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
16 for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
17 arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
21 The IDT vector assignments are listed in arch/x86/include/asm/irq_vectors.h.
27 - entry_INT80_compat: int 0x80 from 32-bit or 64-bit code; compat syscall
44 There are a few complexities here. The different x86-64 entries
109 generate all 'normal' entry points with the regular (faster) paranoid=0
|
| D | topology.rst | 4 x86 Topology
7 This documents and clarifies the main aspects of x86 topology modelling and
12 Documentation/admin-guide/cputopology.rst. This file holds x86-specific
14 definitions. Thus, the way to read up on Linux topology on x86 is to start
15 with the generic one and look at this one in parallel for the x86 specifics.
18 here to *document* the inner workings of x86 topology.
145 threads. Many BIOSes enumerate all threads 0 first and then all threads 1.
146 That has the "advantage" that the logical Linux CPU numbers of threads 0 stay
152 [package 0] -> [core 0] -> [thread 0] -> Linux CPU 0
158 [package 0] -> [core 0] -> [thread 0] -> Linux CPU 0
[all …]
|
| D | elf_auxvec.rst | 4 x86-specific ELF Auxiliary Vectors
7 This document describes the semantics of the x86 auxiliary vectors.
34 ss.ss_flags = 0;
|
| /Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 7 X86:
21 S390 uses diagnose instruction as hypercall (0x500) along with hypercall
36 KVM hypercalls use the HYPCALL instruction with code 0 and the hypercall
52 :Architecture: x86
60 :Architecture: x86
70 :Purpose: Expose hypercall availability to the guest. On x86 platforms, cpuid
89 :Architecture: x86
105 :Architecture: x86
114 a1: clock_type, ATM only KVM_CLOCK_PAIRING_WALLCLOCK (0)
131 * flags: flags, unused (0) at the moment.
[all …]
|
| D | running-nested-guests.rst | 31 - L0 – level-0; the bare metal host, running KVM
38 .. note:: The above diagram is modelled after the x86 architecture;
50 x86.
76 Enabling "nested" (x86)
92 kvm_intel 133627 0
121 Additional nested-related kernel parameters (x86)
144 Starting a nested guest (x86)
188 bare metal host, works as of Linux kernel 5.3 and QEMU 4.2.0 for
189 Intel x86 systems, and even on older versions for s390x.
258 x86-specific info to collect
|
| /Documentation/translations/sp_SP/process/ |
| D | maintainer-kvm-x86.rst | 3 :Original: Documentation/process/maintainer-kvm-x86.rst
6 KVM x86
16 seguir las directrices de KVM x86, sea receptivo a los comentarios, y
27 KVM x86 se encuentra actualmente en un período de transición de ser parte
29 x86 está dividido entre el árbol principal de KVM,
31 x86, ``github.com/kvm-x86/linux.git``.
35 para el siguiente ciclo se dirige a través del árbol de KVM x86. En el
37 través del árbol KVM x86, se aplicará a la rama ``fixes`` antes de llegar
45 El árbol de KVM x86 está organizado en múltiples ramas por temas. El
62 decir, no pasan por el árbol x86 de KVM.
[all …]
|
| D | adding-syscalls.rst | 112 de manera efectiva que ``param_4 == 0``).
116 ``param_4 == 0``).
163 - xyzzyat(AT_FDCWD, path, ..., 0) es equivalente a xyzzy(path, ...)
191 Finalmente, debe ser conciente de que algunas arquitecturas no-x86 tienen
210 usualmente x86 (incluyendo todas las x86_64, x86_32 y x32).
238 Algunas arquitecturas (e.g. x86) tienen sus propias tablas de syscall
282 Implementación de Llamada de Sistema x86
285 Para conectar su nueva llamada de sistema a plataformas x86, necesita
289 arch/x86/entry/syscalls/syscall_64.tbl::
293 y una entrada "i386" en ``arch/x86/entry/syscalls/syscall_32.tbl``::
[all …]
|
| /Documentation/process/ |
| D | maintainer-kvm-x86.rst | 3 KVM x86
12 an honest effort to follow KVM x86's guidelines, are receptive to feedback,
22 KVM x86 is currently in a transition period from being part of the main KVM
23 tree, to being "just another KVM arch". As such, KVM x86 is split across the
24 main KVM tree, ``git.kernel.org/pub/scm/virt/kvm/kvm.git``, and a KVM x86
25 specific tree, ``github.com/kvm-x86/linux.git``.
29 KVM x86 tree. In the unlikely event that a fix for the current cycle is routed
30 through the KVM x86 tree, it will be applied to the ``fixes`` branch before
38 The KVM x86 tree is organized into multiple topic branches. The purpose of
52 directly to the main KVM tree, i.e. do not route through the KVM x86 tree.
[all …]
|
| D | adding-syscalls.rst | 97 expects is zero (effectively checking that ``param_4 == 0``).
100 setting ``param_4 = 0``).
143 - xyzzyat(AT_FDCWD, path, ..., 0) is equivalent to xyzzy(path,...)
169 Finally, be aware that some non-x86 architectures have an easier time if
186 x86 (including all of x86_64, x86_32 and x32).
213 Some architectures (e.g. x86) have their own architecture-specific syscall
251 x86 System Call Implementation
254 To wire up your new system call for x86 platforms, you need to update the
257 arch/x86/entry/syscalls/syscall_64.tbl::
261 and an "i386" entry in ``arch/x86/entry/syscalls/syscall_32.tbl``::
[all …]
|
| D | maintainer-tip.rst | 16 - **x86 architecture**
18 The x86 architecture development takes place in the tip tree except
19 for the x86 KVM and XEN specific parts which are maintained in the
21 there. It's still good practice to Cc the x86 maintainers on
22 x86-specific KVM and XEN patches.
24 Some x86 subsystems have their own maintainers in addition to the
25 overall x86 maintainers. Please Cc the overall x86 maintainers on
26 patches touching files in arch/x86 even when they are not called out
29 Note, that ``x86@kernel.org`` is not a mailing list. It is merely a
30 mail alias which distributes mails to the x86 top-level maintainer
[all …]
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 12 acpi= [HW,ACPI,X86,ARM64,RISCV64,EARLY]
36 1,0: use 1st APIC table
37 default: 0
77 acpi.debug_layer=0x20000000
80 acpi.debug_layer=0xffffffff acpi.debug_level=0x2
82 acpi.debug_layer=0x2 acpi.debug_level=0xffffffff
106 By default, this is disabled due to x86 early mapping
230 acpi_pm_good [X86]
277 add_efi_memmap [EFI,X86,EARLY] Include EFI memory map in
291 behaviour to be specified. Bit 0 enables warnings,
[all …]
|
| D | kernel-parameters.rst | 80 so that "nohz_full=all" is the equivalent of "nohz_full=0-N".
179 X86-32 X86-32, aka i386 architecture is enabled.
180 X86-64 X86-64 architecture is enabled.
181 More X86-64 boot options can be found in
182 Documentation/arch/x86/x86_64/boot-options.rst.
183 X86 Either 32-bit or 64-bit x86 (same as X86-32+X86-64)
197 need or coordination with <Documentation/arch/x86/boot.rst>.
200 See for example <Documentation/arch/x86/x86_64/boot-options.rst>.
|
| /Documentation/features/ |
| D | list-arch.sh | 9 ARCH=${1:-$(uname -m | sed 's/x86_64/x86/' | sed 's/i386/x86/')}
11 $(dirname $0)/../../scripts/get_feat.pl list --arch $ARCH
|
| /Documentation/arch/x86/x86_64/ |
| D | cpu-hotplug-spec.rst | 4 Firmware support for CPU hotplug under Linux/x86-64
7 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
16 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable
18 it should have its LAPIC Enabled bit set to 0. Linux will use the number
|
| /Documentation/ABI/stable/ |
| D | sysfs-hypervisor-xen | 38 <class>: "xen" -- x86: paravirtualized, arm: standard
39 "hvm" -- x86 only: fully virtualized
43 "x86_32": 32 bit x86 guest without PAE
44 "x86_32p": 32 bit x86 guest with PAE
45 "x86_64": 64 bit x86 guest
73 Might return "0" in case of special security settings
126 KernelVersion: 6.3.0
130 boolean files, returning '1' if set, '0' otherwise.
|
| /Documentation/virt/hyperv/ |
| D | clocks.rst | 22 x86/x64
24 On x86/x64, Hyper-V provides guest VMs with a synthetic system clock
65 Linux clockevents are based on Hyper-V synthetic timer 0 (stimer0).
67 timer 0. In older versions of Hyper-V, an interrupt from stimer0
73 x86/x64 doesn't support per-CPU interrupts, Direct Mode statically
74 allocates an x86 interrupt vector (HYPERV_STIMER0_VECTOR) across all CPUs
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-ideapad-laptop | 6 Control the power of camera module. 1 means on, 0 means off.
16 * 0 -> Super Silent Mode
28 * 0 -> Switched Off
33 Contact: platform-driver-x86@vger.kernel.org
47 * 0 -> Switched Off
51 # echo "0" > \
52 /sys/bus/pci/devices/0000:00:1f.0/PNP0C09:00/VPC2004:00/fn_lock
57 Contact: platform-driver-x86@vger.kernel.org
|
| /Documentation/fb/ |
| D | uvesafb.rst | 12 v86d. v86d is used to run the x86 Video BIOS code in a simulated and
14 than x86. Check the v86d documentation for a list of currently supported
64 start of the window. This option is available on x86
70 Available on x86 only.
73 is the default on non-x86.
84 available. Available on x86 only.
89 - 0 - disabled (equivalent to nomtrr)
92 Values other than 0 and 3 will result in a warning and will be
98 Remap 'n' MiB of video RAM. If 0 or not specified, remap memory
162 /sys/bus/platform/drivers/uvesafb/uvesafb.0
[all …]
|
| /Documentation/timers/ |
| D | hpet.rst | 17 role. Many x86 BIOS writers don't route HPET interrupts at all, which
24 platform code which uses timer 0 or 1 as the main timer to intercept HPET
26 arch/x86/kernel/hpet.c.
|
| /Documentation/dev-tools/ |
| D | checkuapi.rst | 43 0) Success
79 All 912 UAPI headers compatible with x86 appear to be backwards compatible
114 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible
127 All 912 UAPI headers compatible with x86 appear to be backwards compatible
161 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible
178 All 912 UAPI headers compatible with x86 appear to be backwards compatible
199 error - 1/912 UAPI headers compatible with x86 appear _not_ to be backwards compatible
219 #define FPSIMD_MAGIC 0x46508001
223 running the script from an x86 machine with an x86 compiler, so, by default,
224 the script only checks x86-compatible UAPI header files::
[all …]
|
| /Documentation/translations/zh_CN/core-api/ |
| D | protection-keys.rst | 55 pkey = pkey_alloc(0, PKEY_DISABLE_WRITE);
56 ptr = mmap(NULL, PAGE_SIZE, PROT_NONE, MAP_ANONYMOUS|MAP_PRIVATE, -1, 0);
63 pkey_set(pkey, 0); // clear PKEY_DISABLE_WRITE
72 .. note:: pkey_set()是RDPKRU和WRPKRU指令的一个封装器。在tools/testing/selftests/x86/protection_keys.c中可以找到一个实现实…
73 tools/testing/selftests/x86/protection_keys.c.
85 pkey = pkey_alloc(0, PKEY_DISABLE_WRITE | PKEY_DISABLE_READ);
|
| /Documentation/virt/kvm/ |
| D | api.rst | 108 x86 includes both i386 and x86_64.
148 You probably want to use 0 as machine type.
150 X86:
153 Supported X86 VM types can be queried via KVM_CAP_VM_TYPES.
178 address used by the VM. The IPA_Bits is encoded in bits[7-0] of the
188 0 Implies default size, 40bits (for backward compatibility)
211 :Architectures: x86
214 :Returns: 0 on success; -1 on error
228 __u32 indices[0];
256 :Returns: 0 if unsupported; 1 (or some other positive integer) if supported
[all …]
|
| /Documentation/staging/ |
| D | static-keys.rst | 86 consist of a single atomic 'no-op' instruction (5 bytes on x86), in the
190 see: arch/x86/Kconfig
193 see: arch/x86/include/asm/jump_label.h
196 see: arch/x86/include/asm/jump_label.h
199 see: arch/x86/include/asm/jump_label.h
202 see: arch/x86/kernel/jump_label.c
205 see: arch/x86/include/asm/jump_label.h
233 ffffffff81044294: e9 00 00 00 00 jmpq ffffffff81044299 <sys_getppid+0x9>
234 ffffffff81044299: 65 48 8b 04 25 c0 b6 mov %gs:0xb6c0,%rax
236 ffffffff810442a2: 48 8b 80 80 02 00 00 mov 0x280(%rax),%rax
[all …]
|
| /Documentation/translations/it_IT/process/ |
| D | adding-syscalls.rst | 109 ``param_4 == 0``).
112 ``param_4 = 0``).
159 - xyzzyat(AT_FDCWD, path, ..., 0) is equivalent to xyzzy(path,...)
187 Infine, state attenti che in alcune architetture non-x86 la vita delle chiamate
206 solitamente x86 (ovvero tutti: x86_64, x86_32 e x32).
236 Alcune architetture (per esempio x86) hanno le loro specifiche tabelle di
281 Implementazione delle chiamate di sistema x86
284 Per collegare la vostra nuova chiamate di sistema alle piattaforme x86,
288 arch/x86/entry/syscalls/syscall_64.tbl::
292 e un elemento per *i386* ``arch/x86/entry/syscalls/syscall_32.tbl``::
[all …]
|
| /Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 28 hardware such as x86, x86-64 and PowerPC.
49 implemented for x86. This routine runs long before console_init() can be
60 it from PowerPC to x86 and x86_64 and added functionality, firescope can now
96 firewire_ohci 0000:15:00.1: added OHCI v1.0 device as card 2, 4 IR + 4 IT
97 ... contexts, quirks 0x11
129 Port 0 (/dev/fw1) opened, 2 nodes detected
141 2 nodes available, local node is: 0
142 0: ffc0, uuid: 00000000 00000000 [LOCAL]
|
123456789