linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linmiaohe <linmiaohe@huawei.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Sean Christopherson <sean.j.christopherson@intel.com>,
	Wanpeng Li <wanpengli@tencent.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
	LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] KVM: Pre-allocate 1 cpumask variable per cpu for both pv tlb and pv ipis
Date: Tue, 11 Feb 2020 02:26:51 +0000	[thread overview]
Message-ID: <5d472766470e44e1b91fe1e5b2f247f8@huawei.com> (raw)

Hi:
>From: Wanpeng Li <wanpengli@tencent.com>
>
>This patch fixes it by pre-allocate 1 cpumask variable per cpu and use it for both pv tlb and pv ipis..
>
>Reported-by: Nick Desaulniers <ndesaulniers@google.com>
>Acked-by: Nick Desaulniers <ndesaulniers@google.com>
>Cc: Peter Zijlstra <peterz@infradead.org>
>Cc: Nick Desaulniers <ndesaulniers@google.com>
>Signed-off-by: Wanpeng Li <wanpengli@tencent.com>

Looks fine for me. Thanks.
Reviewed-by: Miaohe Lin <linmiaohe@huawei.com>


             reply	other threads:[~2020-02-11  2:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11  2:26 linmiaohe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-10  6:38 [PATCH v2 2/2] KVM: Pre-allocate 1 cpumask variable per cpu for both pv tlb and pv ipis Wanpeng Li
2020-02-17 12:46 ` Vitaly Kuznetsov
2020-02-17 13:15   ` Wanpeng Li
2020-02-17 14:16     ` Vitaly Kuznetsov
2020-02-17 17:11 ` Paolo Bonzini
2020-02-18  1:23   ` 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=5d472766470e44e1b91fe1e5b2f247f8@huawei.com \
    --to=linmiaohe@huawei.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=vkuznets@redhat.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 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).