From: Sean Christopherson <seanjc@google.com>
To: Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
kvm@vger.kernel.org, xin@zytor.com,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 2/6] x86/kvm: Rename the KVM private read_msr() function
Date: Tue, 6 May 2025 06:53:56 -0700 [thread overview]
Message-ID: <aBoUdApwSgnr3r9V@google.com> (raw)
In-Reply-To: <20250506092015.1849-3-jgross@suse.com>
On Tue, May 06, 2025, Juergen Gross wrote:
> Avoid a name clash with a new general MSR access helper after a future
> MSR infrastructure rework by renaming the KVM specific read_msr() to
> kvm_read_msr().
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/x86/include/asm/kvm_host.h | 2 +-
> arch/x86/kvm/vmx/vmx.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/kvm_host.h b/arch/x86/include/asm/kvm_host.h
> index 9c971f846108..308f7020dc9d 100644
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -2275,7 +2275,7 @@ static inline void kvm_load_ldt(u16 sel)
> }
>
> #ifdef CONFIG_X86_64
> -static inline unsigned long read_msr(unsigned long msr)
Ewwww. Eww, eww, eww. I forgot this thing existed.
Please just delete this and use rdmsrq() directly (or is it still rdmsrl()? at
this point?).
next prev parent reply other threads:[~2025-05-06 13:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 9:20 [PATCH 0/6] x86/msr: let paravirt inline rdmsr/wrmsr instructions Juergen Gross
2025-05-06 9:20 ` [PATCH 1/6] coco/tdx: Rename MSR access helpers Juergen Gross
2025-05-06 11:26 ` Kirill A. Shutemov
2025-05-06 9:20 ` [PATCH 2/6] x86/kvm: Rename the KVM private read_msr() function Juergen Gross
2025-05-06 13:53 ` Sean Christopherson [this message]
2025-05-06 13:58 ` Jürgen Groß
2025-05-06 16:16 ` Ingo Molnar
2025-05-06 16:29 ` H. Peter Anvin
2025-05-06 9:20 ` [PATCH 3/6] x86/msr: minimize usage of native_*() msr access functions Juergen Gross
2025-05-06 14:24 ` Sean Christopherson
2025-05-09 21:49 ` Wei Liu
2025-05-06 9:20 ` [PATCH 4/6] x86/msr: Move MSR trace calls one function level up Juergen Gross
2025-05-06 9:20 ` [PATCH 5/6] x86/paravirt: Switch MSR access pv_ops functions to instruction interfaces Juergen Gross
2025-05-09 8:18 ` Xin Li
2025-05-12 11:20 ` Jürgen Groß
2025-05-12 11:24 ` Juergen Gross
2025-05-13 5:55 ` Xin Li
2025-05-13 6:06 ` Jürgen Groß
2025-05-13 6:55 ` Xin Li
2025-05-13 22:24 ` H. Peter Anvin
2025-05-15 7:32 ` Xin Li
2025-05-15 20:24 ` H. Peter Anvin
2025-05-13 7:44 ` Xin Li
2025-06-11 12:58 ` Juergen Gross
2025-06-13 7:31 ` Xin Li
2025-06-13 8:01 ` Jürgen Groß
2025-08-25 1:54 ` Xin Li
2025-08-26 10:39 ` Jürgen Groß
2025-05-06 9:20 ` [PATCH 6/6] x86/msr: reduce number of low level MSR access helpers Juergen Gross
2025-05-10 16:03 ` [PATCH 0/6] x86/msr: let paravirt inline rdmsr/wrmsr instructions Michael Kelley
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=aBoUdApwSgnr3r9V@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xin@zytor.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;
as well as URLs for NNTP newsgroup(s).