public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  Paolo Bonzini <pbonzini@redhat.com>,
	Andy Lutomirski <luto@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	 Xiaoyao Li <xiaoyao.li@intel.com>,
	Kai Huang <kai.huang@intel.com>,
	 Jim Mattson <jmattson@google.com>,
	Shan Kang <shan.kang@intel.com>, Xin Li <xin3.li@intel.com>,
	 Zhao Liu <zhao1.liu@intel.com>
Subject: Re: [PATCH v8 00/10] x86/cpu: KVM: Clean up PAT and VMX macros
Date: Thu, 15 Aug 2024 08:23:15 -0700	[thread overview]
Message-ID: <Zr4dY1EbVu6u7Czv@google.com> (raw)
In-Reply-To: <20240605231918.2915961-1-seanjc@google.com>

On Wed, Jun 05, 2024, Sean Christopherson wrote:
> The primary goal of this series is to clean up the VMX MSR macros and their
> usage in KVM.
> 
> The first half of the series touches memtype code that (obviously) impacts
> areas well outside of KVM, in order to address several warts:
> 
>   (a) KVM is defining VMX specific macros for the architectural memtypes
>   (b) the PAT and MTRR code define similar, yet different macros
>   (c) that the PAT code not only has macros for the types (well, enums),
>       it also has macros for encoding the entire PAT MSR that can be used
>       by KVM.
> 
> The memtype changes aren't strictly required for the KVM-focused changes in
> the second half of the series, but splitting this into two series would
> generating a number of conflicts that would be cumbersome to resolve after
> the fact.
> 
> I would like to take this through the KVM tree, as I don't expect the PAT/MTRR
> code to see much change in the near future, and IIRC the original motiviation
> of the VMX MSR cleanups was to prepare for KVM feature enabling (FRED maybe?).

x86 folks, can I get Acks/reviews/NAKs on patches 1-2?  I'd like to land this
series in 6.12 as there is KVM feature enabling work that builds on top.  It's
not a hard dependency, but having these cleanups in place would make my life easier.

Thanks!

  parent reply	other threads:[~2024-08-15 15:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 23:19 [PATCH v8 00/10] x86/cpu: KVM: Clean up PAT and VMX macros Sean Christopherson
2024-06-05 23:19 ` [PATCH v8 01/10] x86/cpu: KVM: Add common defines for architectural memory types (PAT, MTRRs, etc.) Sean Christopherson
2024-06-10 10:31   ` Huang, Kai
2024-08-15 15:34   ` Thomas Gleixner
2024-06-05 23:19 ` [PATCH v8 02/10] x86/cpu: KVM: Move macro to encode PAT value to common header Sean Christopherson
2024-08-15 15:36   ` Thomas Gleixner
2024-06-05 23:19 ` [PATCH v8 03/10] KVM: x86: Stuff vCPU's PAT with default value at RESET, not creation Sean Christopherson
2024-06-05 23:19 ` [PATCH v8 04/10] KVM: VMX: Move MSR_IA32_VMX_BASIC bit defines to asm/vmx.h Sean Christopherson
2024-06-12  1:49   ` Xiaoyao Li
2024-06-05 23:19 ` [PATCH v8 05/10] KVM: VMX: Track CPU's MSR_IA32_VMX_BASIC as a single 64-bit value Sean Christopherson
2024-06-05 23:19 ` [PATCH v8 06/10] KVM: nVMX: Use macros and #defines in vmx_restore_vmx_basic() Sean Christopherson
2024-06-05 23:19 ` [PATCH v8 07/10] KVM: nVMX: Add a helper to encode VMCS info in MSR_IA32_VMX_BASIC Sean Christopherson
2024-06-05 23:19 ` [PATCH v8 08/10] KVM VMX: Move MSR_IA32_VMX_MISC bit defines to asm/vmx.h Sean Christopherson
2024-06-12  1:53   ` Xiaoyao Li
2024-06-05 23:19 ` [PATCH v8 09/10] KVM: VMX: Open code VMX preemption timer rate mask in its accessor Sean Christopherson
2024-06-12  1:54   ` Xiaoyao Li
2024-06-05 23:19 ` [PATCH v8 10/10] KVM: nVMX: Use macros and #defines in vmx_restore_vmx_misc() Sean Christopherson
2024-08-15 15:23 ` Sean Christopherson [this message]
2024-08-23 23:47 ` [PATCH v8 00/10] x86/cpu: KVM: Clean up PAT and VMX macros Sean Christopherson
2024-08-24  9:41   ` Huang, Kai
2024-08-26 16:21     ` Sean Christopherson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Zr4dY1EbVu6u7Czv@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=jmattson@google.com \
    --cc=kai.huang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=shan.kang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    --cc=xin3.li@intel.com \
    --cc=zhao1.liu@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox