linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Cc: pbonzini@redhat.com, rkrcmar@redhat.com, agraf@suse.com,
	corbet@lwn.net, kvm@vger.kernel.org, linux-doc@vger.kernel.org,
	kvm-ppc@vger.kernel.org, paulus@samba.org,
	linuxppc-dev@lists.ozlabs.org, sam.bobroff@au1.ibm.com
Subject: Re: [PATCH 0/6] kvm: powerpc halt polling updates
Date: Fri, 14 Oct 2016 17:27:30 +1100	[thread overview]
Message-ID: <20161014172730.127ed3fb@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <1476406404-32752-1-git-send-email-sjitindarsingh@gmail.com>

On Fri, 14 Oct 2016 11:53:18 +1100
Suraj Jitindar Singh <sjitindarsingh@gmail.com> wrote:

> This patch series makes some updates and bug fixes to the powerpc kvm-hv
> halt polling code.
> 
> The first two patches are concerned with exporting the generic kvm module
> parameter variables and accessing these from the powerpc specific code.
> 
> The third patch fixes a bug where changing the global max halt polling
> interval module parameter can sometimes have no effect.
> 
> The fourth patch decreases the default global max halt polling interval
> to something more sensible.
> 
> The fifth patch contains generic fixups with no functional effect.
> 
> The last patch adds halt polling documentation.

I want to enable polling idle in Linux for SPLPAR/KVM as we do for
dedicated mode. Essentially the guest OS will spin for a small time
before ceding.

There will be a lot of interaction between this and halt polling. I
think guest polling may still be worthwhile if you have halt polling in
the host, although it might be less effective. We should set up some
performance testing with various guest/host parameters and see what
works best. What have you been testing with so far?

Thanks,
Nick

      parent reply	other threads:[~2016-10-14  6:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  0:53 [PATCH 0/6] kvm: powerpc halt polling updates Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 1/6] kvm: export kvm module parameter variables Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 2/6] powerpc/kvm: Use generic kvm module parameters in kvm-hv Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 3/6] powerpc/kvm: Add check for module parameter halt_poll_ns Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 4/6] powerpc/kvm: Decrease the powerpc default halt poll max value Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 5/6] powerpc/kvm: Comment style and print format fixups Suraj Jitindar Singh
2016-10-14  0:53 ` [PATCH 6/6] doc/kvm: Add halt polling documentation Suraj Jitindar Singh
2016-10-14  1:16   ` Wanpeng Li
2016-10-14  2:32     ` Suraj Jitindar Singh
2016-10-14  3:28 ` [PATCH 0/6] kvm: powerpc halt polling updates Sam Bobroff
2016-10-14  6:27 ` Nicholas Piggin [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=20161014172730.127ed3fb@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=agraf@suse.com \
    --cc=corbet@lwn.net \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=sam.bobroff@au1.ibm.com \
    --cc=sjitindarsingh@gmail.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).