Home
last modified time | relevance | path

Searched refs:MSR (Results 1 – 25 of 81) sorted by relevance

1234

/Linux-v5.15/Documentation/trace/
Devents-msr.rst2 MSR Trace Events
5 The x86 kernel supports tracing most MSR (Model Specific Register) accesses.
13 Trace MSR reads:
17 - msr: MSR number
22 Trace MSR writes:
26 - msr: MSR number
39 to add symbolic MSR names.
/Linux-v5.15/Documentation/virt/kvm/
Dmsr.rst15 Custom MSR list
18 The current supported Custom MSR list is:
35 guaranteed to update this data at the moment of MSR write.
37 to write more than once to this MSR. Fields have the following meanings:
54 particular MSR is global.
56 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
144 Availability of this MSR must be checked via bit 3 in 0x4000001 cpuid
154 This MSR falls outside the reserved KVM range and may be removed in the
157 Availability of this MSR must be checked via bit 0 in 0x4000001 cpuid
166 This MSR falls outside the reserved KVM range and may be removed in the
[all …]
Dppc-pv.rst124 MSR bits
127 The MSR contains bits that require hypervisor intervention and bits that do
136 If any other bit changes in the MSR, please still use mtmsr(d).
Dapi.rst226 not returned in the MSR list, as different vcpus can have a different number
628 Reads the values of MSR-based features that are available for the VM. This
629 is similar to KVM_GET_SUPPORTED_CPUID, but it returns MSR indices and values.
673 It tries to set the MSRs in array entries[] one by one. If setting an MSR
674 fails, e.g., due to setting reserved bits, the MSR isn't supported/emulated
675 by KVM, etc..., it stops processing the MSR list and returns the number of
953 Sets the MSR that the Xen HVM guest uses to initialize its hypercall
955 blobs in userspace. When the guest writes the MSR, kvm copies one
3731 __u32 base; /* MSR index the bitmap starts at */
3749 a read for a particular MSR should be handled regardless of the default
[all …]
/Linux-v5.15/Documentation/hwmon/
Dfam15h_power.rst81 MaxCpuSwPwrAcc MSR C001007b
85 CpuSwPwrAcc MSR C001007a
88 by CU_PTSC MSR C0010280
98 MSR MaxCpuSwPwrAcc.
102 iii. At time x, SW reads CpuSwPwrAcc MSR and samples the PTSC.
106 iv. At time y, SW reads CpuSwPwrAcc MSR and samples the PTSC.
/Linux-v5.15/Documentation/x86/
Dsva.rst67 A new thread-scoped MSR (IA32_PASID) provides the connection between
69 accesses an SVA-capable device, this MSR is initialized with a newly
86 This MSR is managed with the XSAVE feature set as "supervisor state" to
87 ensure the MSR is updated during context switch.
93 ENQCMD and program it into the new MSR to communicate the process identity to
94 platform hardware. ENQCMD uses the PASID stored in this MSR to tag requests
103 The MSR must be configured on each logical CPU before any application
105 process share the same page tables, thus the same MSR value.
107 PASID is cleared when a process is created. The PASID allocation and MSR
110 process. If a thread uses ENQCMD without the MSR first being populated, a #GP
[all …]
Dpat.rst209 configurations. The PAT MSR must be updated by Linux in order to support WC
210 and WT attributes. Otherwise, the PAT MSR has the value programmed in it
211 by the firmware. Note, Xen enables WC attribute in the PAT MSR for guests.
214 MTRR PAT Call Sequence PAT State PAT MSR
237 OS PAT initializes PAT MSR with OS setting
238 BIOS PAT keeps PAT MSR with BIOS setting
Dtsx_async_abort.rst24 a) TSX disable - one of the mitigations is to disable TSX. A new MSR
109 There are two control bits in IA32_TSX_CTRL MSR:
Damd-memory-encryption.rst56 If support for SME is present, MSR 0xc00100010 (MSR_AMD64_SYSCFG) can be used to
63 If SEV is supported, MSR 0xc0010131 (MSR_AMD64_SEV) can be used to determine if
/Linux-v5.15/drivers/net/hamradio/
Dbaycom_ser_hdx.c86 #define MSR(iobase) (iobase+6) macro
209 cur_s = inb(MSR(dev->base_addr)) & 0x10; /* the CTS line */ in ser12_rx()
346 hdlcdrv_setdcd(&bc->hdrv, !((inb(MSR(dev->base_addr)) ^ bc->opt_dcd) & 0x80)); in ser12_rx()
398 inb(MSR(dev->base_addr)); in ser12_interrupt()
432 b2 = inb(MSR(iobase)); in ser12_check_uart()
434 b3 = inb(MSR(iobase)) & 0xf0; in ser12_check_uart()
436 outb(b2, MSR(iobase)); in ser12_check_uart()
Dbaycom_ser_fdx.c100 #define MSR(iobase) (iobase+6) macro
262 msr = inb(MSR(dev->base_addr)); in ser12_interrupt()
296 msr = inb(MSR(dev->base_addr)); in ser12_interrupt()
350 b2 = inb(MSR(iobase)); in ser12_check_uart()
352 b3 = inb(MSR(iobase)) & 0xf0; in ser12_check_uart()
354 outb(b2, MSR(iobase)); in ser12_check_uart()
Dyam.c157 #define MSR(iobase) (iobase+6) macro
300 inb(MSR(iobase)); in fpga_reset()
447 rc = inb(MSR(iobase)); /* check DONE signal */ in fpga_download()
476 inb(MSR(dev->base_addr)); in yam_set_uart()
503 b2 = inb(MSR(iobase)); in yam_check_uart()
505 b3 = inb(MSR(iobase)) & 0xf0; in yam_check_uart()
507 outb(b2, MSR(iobase)); in yam_check_uart()
745 unsigned char msr = inb(MSR(dev->base_addr)); in yam_interrupt()
/Linux-v5.15/Documentation/powerpc/
Dtransactional_memory.rst108 delivered. For future compatibility the MSR.TS field should be checked to
112 For 64-bit processes, uc->uc_mcontext.regs->msr is a full 64-bit MSR and its TS
115 For 32-bit processes, the mcontext's MSR register is only 32 bits; the top 32
116 bits are stored in the MSR of the second ucontext, i.e. in
257 kernel via some exception, MSR will end up as TM=0 and TS=01 (ie. TM
259 the MSR and will perform an rfid to do this. In this case rfid can
261 resulting MSR will retain TM = 0 and TS=01 from before (ie. stay in
269 if (MSR 29:31 ¬ = 0b010 | SRR1 29:31 ¬ = 0b000) then
270 MSR 29:31 <- SRR1 29:31
Dultravisor.rst55 * There is a new bit in the MSR that determines whether the current
56 process is running in secure mode, MSR(S) bit 41. MSR(S)=1, process
57 is in secure mode, MSR(s)=0 process is in normal mode.
59 * The MSR(S) bit can only be set by the Ultravisor.
61 * HRFID cannot be used to set the MSR(S) bit. If the hypervisor needs
68 * The privilege of a process is now determined by three MSR bits,
69 MSR(S, HV, PR). In each of the tables below the modes are listed
73 **Secure Mode MSR Settings**
87 **Normal Mode MSR Settings**
993 the MSR value with which to return to the VM.
[all …]
/Linux-v5.15/arch/sparc/include/asm/
Dfloppy_64.h448 #define MSR (port + 4) macro
457 while (!((status = inb(MSR)) & 0x80) && --timeout) in sun_pci_fd_out_byte()
472 while (!((status = inb(MSR)) & 0x80) && --timeout) in sun_pci_fd_sensei()
493 outb(0x80, MSR); in sun_pci_fd_reset()
531 #undef MSR
/Linux-v5.15/drivers/staging/rtl8712/
Drtl8712_cmdctrl_regdef.h14 #define MSR (RTL8712_CMDCTRL_ + 0x000C) macro
/Linux-v5.15/Documentation/admin-guide/hw-vuln/
Dspecial-register-buffer-data-sampling.rst95 IA32_MCU_OPT_CTRL MSR Definition
98 IA32_MCU_OPT_CTRL MSR, (address 0x123). The presence of this MSR and
100 9]==1. This MSR is introduced through the microcode update.
Dtsx_async_abort.rst15 is 0 in the IA32_ARCH_CAPABILITIES MSR. On processors where the MDS_NO bit
16 (bit 5) is 0 in the IA32_ARCH_CAPABILITIES MSR, the existing MDS mitigations
192 and which get the new IA32_TSX_CTRL MSR through a microcode
193 update. This new MSR allows for the reliable deactivation of
220 provides a TSX control MSR. If so,
232 combinations of CPUID bit MD_CLEAR and IA32_ARCH_CAPABILITIES MSR bits MDS_NO
/Linux-v5.15/drivers/powercap/
DKconfig23 tristate "Intel RAPL Support via MSR Interface"
28 technology via MSR interface, which allows power limits to be enforced
/Linux-v5.15/arch/powerpc/kernel/
Dswsusp_asm64.S114 SAVE_SPECIAL(MSR)
244 RESTORE_SPECIAL(MSR)
/Linux-v5.15/drivers/usb/serial/
Dio_16654.h38 #define MSR 6 // Modem Status Register macro
/Linux-v5.15/arch/x86/boot/
Dearly_serial_console.c20 #define MSR 6 /* Modem Status */ macro
/Linux-v5.15/arch/x86/kernel/
Dverify_cpu.S96 jnc .Lverify_cpu_check # only write MSR if bit was changed
/Linux-v5.15/drivers/staging/rtl8192u/
Dr8192U_hw.h161 MSR = 0x303, // Media Status register enumerator
/Linux-v5.15/Documentation/translations/zh_CN/admin-guide/
Dtainted-kernels.rst120 运行,MSR被暴露到用户空间中。

1234