From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: linmiaohe <linmiaohe@huawei.com>,
pbonzini@redhat.com, rkrcmar@redhat.com,
sean.j.christopherson@intel.com, vkuznets@redhat.com,
wanpengli@tencent.com, jmattson@google.com, joro@8bytes.org,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] KVM: apic: remove unused function apic_lvt_vector()
Date: Thu, 13 Feb 2020 11:14:28 -0800 [thread overview]
Message-ID: <2fb684de-30c1-ed67-600f-08168e64d6c7@oracle.com> (raw)
In-Reply-To: <1581561464-3893-1-git-send-email-linmiaohe@huawei.com>
On 2/12/20 6:37 PM, linmiaohe wrote:
> From: Miaohe Lin <linmiaohe@huawei.com>
>
> The function apic_lvt_vector() is unused now, remove it.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> arch/x86/kvm/lapic.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index eafc631d305c..0b563c280784 100644
> --- a/arch/x86/kvm/lapic.c
> +++ b/arch/x86/kvm/lapic.c
> @@ -294,11 +294,6 @@ static inline int apic_lvt_enabled(struct kvm_lapic *apic, int lvt_type)
> return !(kvm_lapic_get_reg(apic, lvt_type) & APIC_LVT_MASKED);
> }
>
> -static inline int apic_lvt_vector(struct kvm_lapic *apic, int lvt_type)
> -{
> - return kvm_lapic_get_reg(apic, lvt_type) & APIC_VECTOR_MASK;
> -}
> -
> static inline int apic_lvtt_oneshot(struct kvm_lapic *apic)
> {
> return apic->lapic_timer.timer_mode == APIC_LVT_TIMER_ONESHOT;
There is one place, lapic_timer_int_injected(), where this function be
used :
struct kvm_lapic *apic = vcpu->arch.apic;
- u32 reg = kvm_lapic_get_reg(apic, APIC_LVTT);
if (kvm_apic_hw_enabled(apic)) {
- int vec = reg & APIC_VECTOR_MASK;
+ int vec = apic_lvt_vector(APIC_LVTT);
void *bitmap = apic->regs + APIC_ISR;
But since that's the only place I can find, we probably don't need a
separate function.
Reviewed-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
next prev parent reply other threads:[~2020-02-13 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 2:37 linmiaohe
2020-02-13 19:14 ` Krish Sadhukhan [this message]
2020-02-17 17:02 ` Vitaly Kuznetsov
2020-02-17 17:13 ` Paolo Bonzini
2020-02-18 1:56 linmiaohe
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=2fb684de-30c1-ed67-600f-08168e64d6c7@oracle.com \
--to=krish.sadhukhan@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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®