From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thadeu Lima de Souza Cascardo <cascardo@canonical.com>,
Wanpeng Li <kernellwp@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] KVM: Pre-allocate 1 cpumask variable per cpu for both pv tlb and pv ipis
Date: Tue, 04 Feb 2020 15:42:04 +0100 [thread overview]
Message-ID: <871rrao1mr.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20200204142733.GI40679@calabresa>
Thadeu Lima de Souza Cascardo <cascardo@canonical.com> writes:
>> > > /*
>> > > @@ -624,6 +625,7 @@ static void __init kvm_guest_init(void)
>> > > kvm_para_has_feature(KVM_FEATURE_STEAL_TIME)) {
>> > > pv_ops.mmu.flush_tlb_others = kvm_flush_tlb_others;
>> > > pv_ops.mmu.tlb_remove_table = tlb_remove_table;
>> > > + pr_info("KVM setup pv remote TLB flush\n");
>> > > }
>> > >
>
> I am more concerned about printing the "KVM setup pv remote TLB flush" message,
> not only when KVM pv is used, but pv TLB flush is not going to be used, but
> also when the system is not even paravirtualized.
Huh? In Wanpeng's patch this print is under
if (kvm_para_has_feature(KVM_FEATURE_PV_TLB_FLUSH) &&
!kvm_para_has_hint(KVM_HINTS_REALTIME) &&
kvm_para_has_feature(KVM_FEATURE_STEAL_TIME))
and if you mean another patch we descussed before which was adding
(!kvm_para_available() || nopv) check than it's still needed. Or,
alternatively, we can make kvm_para_has_feature() check for that.
--
Vitaly
next prev parent reply other threads:[~2020-02-04 14:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 2:34 [PATCH] KVM: Pre-allocate 1 cpumask variable per cpu for both pv tlb and pv ipis Wanpeng Li
2020-02-04 12:57 ` Vitaly Kuznetsov
2020-02-04 13:09 ` Wanpeng Li
2020-02-04 14:27 ` Thadeu Lima de Souza Cascardo
2020-02-04 14:42 ` Vitaly Kuznetsov [this message]
2020-02-04 14:51 ` Thadeu Lima de Souza Cascardo
2020-02-04 14:36 ` Vitaly Kuznetsov
2020-02-05 13:26 ` Wanpeng Li
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=871rrao1mr.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=cascardo@canonical.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=wanpengli@tencent.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 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.