x86/kvm/x86.c

325 static bool kvm_msr_ignored_check(u32 msr, u64 data, bool write)
327 	const char *op = write ? "wrmsr" : "rdmsr";
1864 		 * 64-bit code should hence be able to write a non-canonical
2090 		/* MSR write failed? See if we should ask user space */
2329 		++version;  /* first time write, random junk */
2678 	 * We also track th most recent recorded KHZ, write and time to
2679 	 * allow the matching interval to be extended at each write.
2694 		 * nanosecond time, offset, and write, so if TSCs are in
2743 			 * Here lies UAPI baggage: when a user-initiated TSC write has
3506 		/* An attempt to write a 1 to a reserved bit raises #GP */
3751 		version += 1;  /* first time write, random junk */
4167 		 * Userspace is allowed to write '0' to MSRs that KVM reports
4542  * Read or write a bunch of msrs. All parameters are kernel addresses.
4561  * Read or write a bunch of msrs. Parameters are user addresses.
7752 			    gpa_t gpa, bool write)
7759 		trace_vcpu_match_mmio(gva, gpa, write, true);
7768 				bool write)
7772 		| (write ? PFERR_WRITE_MASK : 0);
7784 		trace_vcpu_match_mmio(gva, *gpa, write, false);
7793 	return vcpu_is_mmio_gpa(vcpu, gva, *gpa, write);
7817 	bool write;
7877 	.write = true,
7888 	bool write = ops->write;
7902 		ret = vcpu_is_mmio_gpa(vcpu, addr, gpa, write);
7904 		ret = vcpu_mmio_gva_to_gpa(vcpu, addr, &gpa, exception, write);
7978 	vcpu->run->mmio.is_write = vcpu->mmio_is_write = ops->write;
8032 	 * Emulate the atomic as a straight write to avoid #AC if SLD is
8086 	pr_warn_once("emulating exchange as write\n");
8828 		 * write access need to be emulated.
8843 	 * retry instruction -> write #PF -> emulation fail -> retry
8858 	 * If emulation may have been triggered by a write to a shadowed page
8872 	 * a SPTE and write-protect the gfn to resolve the !PRESENT fault, and
9614  * Indirection to move queue_work() out of the tk_core.seq write held
9639 	 * this is invoked with tk_core.seq write held.
10950 	 * 3) This also orders the write to mode from any reads to the page
11264  *       write gpa, len
11269  * write:
11272  *       write gpa, len
12926 	 * CREATE:      No shadow pages exist, thus nothing to write-protect
12959 		 * Initially-all-set does not require write protecting any page,
12979 		 * the subtly complex checks when removing write access.
12984 		 * write-protected before returning to userspace, i.e. before
12991 		 * Specifically, KVM also write-protects guest page tables to
12993 		 * no CPUs can write to those page before mmu_lock is dropped.
13002 		 * a guest page table being write-protected (KVM clears the
13003 		 * MMU-writable flag when write-protecting for shadow paging).
13012 		 * write access" helpers to ignore MMU-writable entirely.