qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Jan Kiszka <jan.kiszka@web.de>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH v3 0/7] RTC: New logic to emulate RTC
Date: Wed, 14 Mar 2012 09:54:16 +0100	[thread overview]
Message-ID: <4F605CB8.20200@redhat.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E095B91@SHSMSX101.ccr.corp.intel.com>

Il 14/03/2012 09:52, Zhang, Yang Z ha scritto:
>>>>> Is there any comments with the version 3?
>>> 
>>> Can you explain why you dropped the logic to set the timer to the
>>> next event?
> Do you mean why I change the rtc logic? The reason is that: When a
> guest is idle, the main activity inside qemu is the rtc update
> timer(2 per second). In our experience(running 64 rhel6u1 guests), it
> will decrease pkg C6 residency about 6%(6% means 2 watts in my box).
> And normally, the guest will not use the update-end interrupt and
> alarm. So there has no need to run a periodic timer when guest isn't
> using it.

No, why you're keeping roughly the same logic as current QEMU, instead
of the more radical changes that were in v2.

Paolo

  reply	other threads:[~2012-03-14  8:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  0:00 [Qemu-devel] [PATCH v3 0/7] RTC: New logic to emulate RTC Zhang, Yang Z
2012-03-14  8:34 ` Paolo Bonzini
2012-03-14  8:52   ` Zhang, Yang Z
2012-03-14  8:54     ` Paolo Bonzini [this message]
2012-03-15  0:06       ` Zhang, Yang Z
2012-03-15  9:34         ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2012-03-02  6:58 Zhang, Yang Z

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=4F605CB8.20200@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yang.z.zhang@intel.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).