All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v5 1/2] kvm: support -overcommit cpu-pm=on|off
Date: Mon, 25 Jun 2018 10:48:47 +0200	[thread overview]
Message-ID: <87wounjlow.fsf@secure.laptop> (raw)
In-Reply-To: <20180622190936.177827-2-mst@redhat.com> (Michael S. Tsirkin's message of "Fri, 22 Jun 2018 22:09:42 +0300")

"Michael S. Tsirkin" <mst@redhat.com> wrote:
> With this flag, kvm allows guest to control host CPU power state.  This
> increases latency for other processes using same host CPU in an
> unpredictable way, but if decreases idle entry/exit times for the
> running VCPU, so to use it QEMU needs a hint about whether host CPU is
> overcommitted, hence the flag name.
>
> Follow-up patches will expose this capability to guest
> (using mwait leaf).
>
> Based on a patch by Wanpeng Li <kernellwp@gmail.com> .
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

[...]

> diff --git a/migration/migration.c b/migration/migration.c
> index 1e99ec9b7e..e468b50c4f 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -45,6 +45,7 @@
>  #include "migration/colo.h"
>  #include "hw/boards.h"
>  #include "monitor/monitor.h"
> +#include "qemu/ptr_ring.h"
>  
>  #define MAX_THROTTLE  (32 << 20)      /* Migration transfer speed throttling */
>  

Why is this chuck needed?  I can't see a reason.


Thanks, Juan.

WARNING: multiple messages have this Message-ID (diff)
From: Juan Quintela <quintela@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/2] kvm: support -overcommit cpu-pm=on|off
Date: Mon, 25 Jun 2018 10:48:47 +0200	[thread overview]
Message-ID: <87wounjlow.fsf@secure.laptop> (raw)
In-Reply-To: <20180622190936.177827-2-mst@redhat.com> (Michael S. Tsirkin's message of "Fri, 22 Jun 2018 22:09:42 +0300")

"Michael S. Tsirkin" <mst@redhat.com> wrote:
> With this flag, kvm allows guest to control host CPU power state.  This
> increases latency for other processes using same host CPU in an
> unpredictable way, but if decreases idle entry/exit times for the
> running VCPU, so to use it QEMU needs a hint about whether host CPU is
> overcommitted, hence the flag name.
>
> Follow-up patches will expose this capability to guest
> (using mwait leaf).
>
> Based on a patch by Wanpeng Li <kernellwp@gmail.com> .
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

[...]

> diff --git a/migration/migration.c b/migration/migration.c
> index 1e99ec9b7e..e468b50c4f 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -45,6 +45,7 @@
>  #include "migration/colo.h"
>  #include "hw/boards.h"
>  #include "monitor/monitor.h"
> +#include "qemu/ptr_ring.h"
>  
>  #define MAX_THROTTLE  (32 << 20)      /* Migration transfer speed throttling */
>  

Why is this chuck needed?  I can't see a reason.


Thanks, Juan.

  reply	other threads:[~2018-06-25  8:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 19:09 [PATCH v5 0/2] kvm: limited x86 CPU power management Michael S. Tsirkin
2018-06-22 19:09 ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22 19:09 ` [PATCH v5 1/2] kvm: support -overcommit cpu-pm=on|off Michael S. Tsirkin
2018-06-22 19:09   ` [Qemu-devel] " Michael S. Tsirkin
2018-06-25  8:48   ` Juan Quintela [this message]
2018-06-25  8:48     ` Juan Quintela
2018-06-22 19:09 ` [PATCH v5 2/2] i386/cpu: make -cpu host support monitor/mwait Michael S. Tsirkin
2018-06-22 19:09   ` [Qemu-devel] " Michael S. Tsirkin

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=87wounjlow.fsf@secure.laptop \
    --to=quintela@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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.