From: Chao Wu <chaowu@linux.alibaba.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Richard Cochran <richardcochran@gmail.com>
Cc: x86@kernel.org, kvm@vger.kernel.org,
Chao Wu <chaowu@linux.alibaba.com>,
Jiang Liu <gerry@linux.alibaba.com>
Subject: [PATCH 2/2] pvclock: remove EXPORT_SYMBOL_GPL for pvclock_get_pvti_cpu0_va
Date: Tue, 25 May 2021 16:44:58 +0800 [thread overview]
Message-ID: <5a337f71a316b4b2dc4661a358110dec9b6cff2e.1621505277.git.chaowu@linux.alibaba.com> (raw)
In-Reply-To: <cover.1621505277.git.chaowu@linux.alibaba.com>
In order to avoid abusing the "pvclock_get_pvti_cpu0_va” interface, we
should remove EXPORT_SYMBOL_GPL for that function.
Signed-off-by: Chao Wu <chaowu@linux.alibaba.com>
Signed-off-by: Jiang Liu <gerry@linux.alibaba.com>
---
arch/x86/kernel/pvclock.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/kernel/pvclock.c b/arch/x86/kernel/pvclock.c
index 637982efecd8..e26940c33d99 100644
--- a/arch/x86/kernel/pvclock.c
+++ b/arch/x86/kernel/pvclock.c
@@ -164,4 +164,3 @@ struct pvclock_vsyscall_time_info *pvclock_get_pvti_cpu0_va(void)
{
return pvti_cpu0_va;
}
-EXPORT_SYMBOL_GPL(pvclock_get_pvti_cpu0_va);
--
2.24.3 (Apple Git-128)
next prev parent reply other threads:[~2021-05-25 8:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:44 [PATCH 0/2] Fix ptp_kvm_get_time_fn infinite loop and remove redundant EXPORT_SYMBOL_GPL Chao Wu
2021-05-25 8:44 ` [PATCH 1/2] ptp_kvm: fix an infinite loop in ptp_kvm_get_time_fn when vm has more than 64 vcpus Chao Wu
2021-05-25 8:44 ` Chao Wu [this message]
2021-08-09 13:05 ` [PATCH 0/2] Fix ptp_kvm_get_time_fn infinite loop and remove redundant EXPORT_SYMBOL_GPL Chao Wu
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=5a337f71a316b4b2dc4661a358110dec9b6cff2e.1621505277.git.chaowu@linux.alibaba.com \
--to=chaowu@linux.alibaba.com \
--cc=bp@alien8.de \
--cc=gerry@linux.alibaba.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.