kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <kernellwp@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>, kvm <kvm@vger.kernel.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>
Subject: Re: [PATCH v4 0/3] KVM: Yield to IPI target if necessary
Date: Fri, 28 Jun 2019 15:29:58 +0800	[thread overview]
Message-ID: <CANRm+Cz6vX587uLV__FheXuiOe7pzfGeUZb++ZJ1y9Cmk6GkoA@mail.gmail.com> (raw)
In-Reply-To: <CANRm+CwfXViF34eLma5ZnqjT96Sq=XehpBiTZTj1TfJnkevVMA@mail.gmail.com>

ping again,
On Tue, 18 Jun 2019 at 17:00, Wanpeng Li <kernellwp@gmail.com> wrote:
>
> ping, :)
> On Tue, 11 Jun 2019 at 20:23, Wanpeng Li <kernellwp@gmail.com> wrote:
> >
> > The idea is from Xen, when sending a call-function IPI-many to vCPUs,
> > yield if any of the IPI target vCPUs was preempted. 17% performance
> > increasement of ebizzy benchmark can be observed in an over-subscribe
> > environment. (w/ kvm-pv-tlb disabled, testing TLB flush call-function
> > IPI-many since call-function is not easy to be trigged by userspace
> > workload).
> >
> > v3 -> v4:
> >  * check map->phys_map[dest_id]
> >  * more cleaner kvm_sched_yield()
> >
> > v2 -> v3:
> >  * add bounds-check on dest_id
> >
> > v1 -> v2:
> >  * check map is not NULL
> >  * check map->phys_map[dest_id] is not NULL
> >  * make kvm_sched_yield static
> >  * change dest_id to unsinged long
> >
> > Wanpeng Li (3):
> >   KVM: X86: Yield to IPI target if necessary
> >   KVM: X86: Implement PV sched yield hypercall
> >   KVM: X86: Expose PV_SCHED_YIELD CPUID feature bit to guest
> >
> >  Documentation/virtual/kvm/cpuid.txt      |  4 ++++
> >  Documentation/virtual/kvm/hypercalls.txt | 11 +++++++++++
> >  arch/x86/include/uapi/asm/kvm_para.h     |  1 +
> >  arch/x86/kernel/kvm.c                    | 21 +++++++++++++++++++++
> >  arch/x86/kvm/cpuid.c                     |  3 ++-
> >  arch/x86/kvm/x86.c                       | 21 +++++++++++++++++++++
> >  include/uapi/linux/kvm_para.h            |  1 +
> >  7 files changed, 61 insertions(+), 1 deletion(-)
> >
> > --
> > 2.7.4
> >

  reply	other threads:[~2019-06-28  7:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 12:23 [PATCH v4 0/3] KVM: Yield to IPI target if necessary Wanpeng Li
2019-06-11 12:23 ` [PATCH v4 1/3] KVM: X86: " Wanpeng Li
2019-06-11 12:23 ` [PATCH v4 2/3] KVM: X86: Implement PV sched yield hypercall Wanpeng Li
2019-06-11 12:23 ` [PATCH v4 3/3] KVM: X86: Expose PV_SCHED_YIELD CPUID feature bit to guest Wanpeng Li
2019-06-18  9:00 ` [PATCH v4 0/3] KVM: Yield to IPI target if necessary Wanpeng Li
2019-06-28  7:29   ` Wanpeng Li [this message]
2019-07-02 16:49 ` Paolo Bonzini

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=CANRm+Cz6vX587uLV__FheXuiOe7pzfGeUZb++ZJ1y9Cmk6GkoA@mail.gmail.com \
    --to=kernellwp@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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).