From: chenqingyun001@208suo.com
To: maz@kernel.org, oliver.upton@linux.dev, catalin.marinas@arm.com,
will@kernel.org
Cc: kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org,
james.morse@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com
Subject: [PATCH] KVM: arm64:Use #include <linux/kprobes.h> instead of <asm/kprobes.h>
Date: Fri, 14 Jul 2023 12:57:42 +0800 [thread overview]
Message-ID: <3d56cf129c2cf1cf53f19ebe3c23a803@208suo.com> (raw)
In-Reply-To: <tencent_2099141F01FC6C32AAA20B385053A477C507@qq.com>
Since <asm/kprobes.h> is a kernel-proprietary header file, it
should not be included by user-space programs.
And <linux/kprobes.h> is a public header file,
which provides some functions for registering
and unregistering probes
Signed-off-by: Qingyun Chen <chenqingyun001@208suo.com>
---
arch/arm64/kvm/hyp/vhe/sysreg-sr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/kvm/hyp/vhe/sysreg-sr.c
b/arch/arm64/kvm/hyp/vhe/sysreg-sr.c
index b35a178e7e0d..072471df8b1b 100644
--- a/arch/arm64/kvm/hyp/vhe/sysreg-sr.c
+++ b/arch/arm64/kvm/hyp/vhe/sysreg-sr.c
@@ -9,7 +9,7 @@
#include <linux/compiler.h>
#include <linux/kvm_host.h>
-#include <asm/kprobes.h>
+#include <linux/kprobes.h>
#include <asm/kvm_asm.h>
#include <asm/kvm_emulate.h>
#include <asm/kvm_hyp.h>
next parent reply other threads:[~2023-07-14 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_2099141F01FC6C32AAA20B385053A477C507@qq.com>
2023-07-14 4:57 ` chenqingyun001 [this message]
2023-07-14 7:57 ` [PATCH] KVM: arm64:Use #include <linux/kprobes.h> instead of <asm/kprobes.h> Marc Zyngier
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=3d56cf129c2cf1cf53f19ebe3c23a803@208suo.com \
--to=chenqingyun001@208suo.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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