From: kbuild test robot <lkp@intel.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: "Roman Kagan" <rkagan@virtuozzo.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org,
"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
"Ingo Molnar" <mingo@redhat.com>,
kbuild-all@01.org, "Andy Lutomirski" <luto@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Mohammed Gamal" <mmorsy@redhat.com>
Subject: [RFC PATCH] x86/kvm: kvm_hyperv_tsc_notifier() can be static
Date: Fri, 19 Jan 2018 19:15:40 +0800 [thread overview]
Message-ID: <20180119111540.GA13358@lkp-ne02> (raw)
In-Reply-To: <20180116182700.1042-8-vkuznets@redhat.com>
Fixes: ce386b0e39a0 ("x86/kvm: support Hyper-V reenlightenment")
Signed-off-by: Fengguang Wu <fengguang.wu@intel.com>
---
x86.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index 94f28e6..27e590a 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -5933,7 +5933,7 @@ static void tsc_khz_changed(void *data)
__this_cpu_write(cpu_tsc_khz, khz);
}
-void kvm_hyperv_tsc_notifier(void)
+static void kvm_hyperv_tsc_notifier(void)
{
#ifdef CONFIG_X86_64
struct kvm *kvm;
prev parent reply other threads:[~2018-01-19 11:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:26 [PATCH v3 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 1/7] x86/hyper-v: check for required priviliges in hyperv_init() Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously Vitaly Kuznetsov
2018-01-16 18:26 ` [PATCH v3 3/7] x86/hyper-v: reenlightenment notifications support Vitaly Kuznetsov
2018-01-16 18:33 ` Thomas Gleixner
2018-01-19 10:21 ` kbuild test robot
2018-01-19 10:47 ` Vitaly Kuznetsov
2018-01-20 7:48 ` Thomas Gleixner
2018-01-22 1:22 ` Michael Kelley (EOSG)
2018-01-22 12:06 ` Vitaly Kuznetsov
2018-01-23 13:41 ` Vitaly Kuznetsov
2018-01-23 14:02 ` Michael Kelley (EOSG)
2018-01-23 14:07 ` Vitaly Kuznetsov
2018-01-22 10:41 ` Vitaly Kuznetsov
2018-01-19 11:11 ` kbuild test robot
2018-01-16 18:26 ` [PATCH v3 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining Vitaly Kuznetsov
2018-01-16 18:31 ` Thomas Gleixner
2018-01-16 18:26 ` [PATCH v3 5/7] x86/irq: Count Hyper-V reenlightenment interrupts Vitaly Kuznetsov
2018-01-16 18:32 ` Thomas Gleixner
2018-01-16 18:26 ` [PATCH v3 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V Vitaly Kuznetsov
2018-01-16 18:27 ` [PATCH v3 7/7] x86/kvm: support Hyper-V reenlightenment Vitaly Kuznetsov
2018-01-19 11:15 ` kbuild test robot
2018-01-19 11:15 ` kbuild test robot [this message]
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=20180119111540.GA13358@lkp-ne02 \
--to=lkp@intel.com \
--cc=Michael.H.Kelley@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mmorsy@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).