From: "WEI-HONG, YE" <1234567weewee457@gmail.com>
To: seanjc@google.com, pbonzini@redhat.com
Cc: vkuznets@redhat.com, tglx@kernel.org, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, thuth@redhat.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, hank20010209@gmail.com, "WEI-HONG,
YE" <1234567weewee457@gmail.com>
Subject: [PATCH v2] x86/mtrr: Drop stale linux/kvm_para.h include
Date: Wed, 8 Jul 2026 13:52:32 +0000 [thread overview]
Message-ID: <20260708135232.160302-1-1234567weewee457@gmail.com> (raw)
arch/x86/kernel/cpu/mtrr/mtrr.c includes linux/kvm_para.h for
historical reasons. The include was needed for kvm_para_available()
check in mtrr_trim_uncached_memory(), but that usage was removed by
commit bf3647c44bc7 ("x86: tone down mtrr_trim_uncached_memory()
warning").
Drop the stale linux/kvm_para.h include. This also removes the need for
explicit linux/types.h workaround that existed only because kvm_para.h
depended on it.
Suggested-by: Sean Christopherson <seanjc@google.com>
Signed-off-by: WEI-HONG, YE <1234567weewee457@gmail.com>
---
v1...v2: https://lore.kernel.org/all/20260505065849.81691-1-1234567weewee457@gmail.com
- Drop the stale linux/kvm_para.h include from mtrr.c instead of adding
linux/types to asm/kvm_para.h, as suggested by Sean.
arch/x86/kernel/cpu/mtrr/mtrr.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/x86/kernel/cpu/mtrr/mtrr.c b/arch/x86/kernel/cpu/mtrr/mtrr.c
index 4b3d492afe17..db5bf4adfd28 100644
--- a/arch/x86/kernel/cpu/mtrr/mtrr.c
+++ b/arch/x86/kernel/cpu/mtrr/mtrr.c
@@ -18,10 +18,7 @@
System Programming Guide; Section 9.11. (1997 edition - PPro).
*/
-#include <linux/types.h> /* FIXME: kvm_para.h needs this */
-
#include <linux/stop_machine.h>
-#include <linux/kvm_para.h>
#include <linux/uaccess.h>
#include <linux/export.h>
#include <linux/mutex.h>
--
2.48.1
reply other threads:[~2026-07-08 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260708135232.160302-1-1234567weewee457@gmail.com \
--to=1234567weewee457@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hank20010209@gmail.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=thuth@redhat.com \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®