All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH v4 2/2] i386/cpu: make -cpu host support monitor/mwait
Date: Fri, 22 Jun 2018 15:35:16 -0300	[thread overview]
Message-ID: <20180622183516.GC7451@localhost.localdomain> (raw)
In-Reply-To: <20180622003140.164613-3-mst@redhat.com>

On Fri, Jun 22, 2018 at 03:31:48AM +0300, Michael S. Tsirkin wrote:
> When guest CPU PM is enabled, and with -cpu host, expose the host CPU
> MWAIT leaf in the CPUID so guest can make good PM decisions.
> 
> Note: the result is 100% CPU utilization reported by host as host
> no longer knows that the CPU is halted.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

-- 
Eduardo

WARNING: multiple messages have this Message-ID (diff)
From: Eduardo Habkost <ehabkost@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH v4 2/2] i386/cpu: make -cpu host support monitor/mwait
Date: Fri, 22 Jun 2018 15:35:16 -0300	[thread overview]
Message-ID: <20180622183516.GC7451@localhost.localdomain> (raw)
In-Reply-To: <20180622003140.164613-3-mst@redhat.com>

On Fri, Jun 22, 2018 at 03:31:48AM +0300, Michael S. Tsirkin wrote:
> When guest CPU PM is enabled, and with -cpu host, expose the host CPU
> MWAIT leaf in the CPUID so guest can make good PM decisions.
> 
> Note: the result is 100% CPU utilization reported by host as host
> no longer knows that the CPU is halted.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>

-- 
Eduardo

  reply	other threads:[~2018-06-22 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  0:31 [PATCH v4 0/2] kvm: limited x86 CPU power management Michael S. Tsirkin
2018-06-22  0:31 ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22  0:31 ` [PATCH v4 2/2] i386/cpu: make -cpu host support monitor/mwait Michael S. Tsirkin
2018-06-22  0:31   ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22 18:35   ` Eduardo Habkost [this message]
2018-06-22 18:35     ` Eduardo Habkost
2018-06-22  0:31 ` [PATCH v4 1/2] kvm: support -overcommit cpu-pm=on|off Michael S. Tsirkin
2018-06-22  0:31   ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22 18:22   ` Eduardo Habkost
2018-06-22 18:22     ` [Qemu-devel] " Eduardo Habkost
2018-06-22 18:42     ` Michael S. Tsirkin
2018-06-22 18:42       ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22 18:34   ` Eduardo Habkost
2018-06-22 18:34     ` [Qemu-devel] " Eduardo Habkost
2018-06-22 19:10     ` Michael S. Tsirkin
2018-06-22 19:10       ` [Qemu-devel] " Michael S. Tsirkin
2018-06-22  3:01 ` [PATCH v4 0/2] kvm: limited x86 CPU power management no-reply
2018-06-22  3:01   ` [Qemu-devel] " no-reply

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=20180622183516.GC7451@localhost.localdomain \
    --to=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.