[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230503182852.3431281-1-seanjc@google.com>
Date: Wed, 3 May 2023 11:28:47 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>,
Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
Wenyao Hai <haiwenyao@...ontech.com>,
Ke Guo <guoke@...ontech.com>
Subject: [PATCH 0/5] KVM: x86: Clean up MSR PAT handling
Clean up KVM's handling of MSR PAT. The PAT is currently lumped in with
MTRRs, and while the PAT does affect memtypes, it's not an MTRR and is even
exempted from KVM's kludgy attempts to play nice with UC memory for guests
with passthrough devices that have non-coherent DMA.
Note, this includes two previously posted patches:
https://lore.kernel.org/all/20230329081859.2571698-1-guoke@uniontech.com
https://lore.kernel.org/all/20230331071929.102070-1-haiwenyao@uniontech.com
Ke Guo (1):
KVM: SVM: Use kvm_pat_valid() directly instead of kvm_mtrr_valid()
Sean Christopherson (3):
KVM: x86: Use MTRR macros to define possible MTRR MSR ranges
KVM: x86: WARN if writes to PAT MSR are handled by common KVM code
KVM: x86: Move PAT MSR handling out of mtrr.c
Wenyao Hai (1):
KVM: VMX: Open code writing vCPU's PAT in VMX's MSR handler
arch/x86/kvm/mtrr.c | 20 ++++++--------------
arch/x86/kvm/svm/svm.c | 2 +-
arch/x86/kvm/vmx/vmx.c | 8 +++-----
arch/x86/kvm/x86.c | 18 ++++++++++++++----
4 files changed, 24 insertions(+), 24 deletions(-)
base-commit: 5c291b93e5d665380dbecc6944973583f9565ee5
--
2.40.1.495.gc816e09b53d-goog
Powered by blists - more mailing lists