All of lore.kernel.org
 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: [PATCH v2 0/4] RTC: New logic to emulate RTC
Date: Thu, 23 Feb 2012 07:51:52 +0100	[thread overview]
Message-ID: <4F45E208.4020101@redhat.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E07946F@SHSMSX101.ccr.corp.intel.com>

On 02/23/2012 02:49 AM, Zhang, Yang Z wrote:
>> > 6) Setting the clock after 500 ms happens not on every set, but only when moving
>> > out of divider reset (register A bits 5-7 moving from 110 or 111 to 010).  As far as
>> > I can read, SET prevents the registers from changing value, but keeps the internal
>> > sub-second counters running.
> Do we really need this logic? It sounds like senseless. 

It doesn't seem hard to do, see my branch.

Paolo

WARNING: multiple messages have this Message-ID (diff)
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 v2 0/4] RTC: New logic to emulate RTC
Date: Thu, 23 Feb 2012 07:51:52 +0100	[thread overview]
Message-ID: <4F45E208.4020101@redhat.com> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E07946F@SHSMSX101.ccr.corp.intel.com>

On 02/23/2012 02:49 AM, Zhang, Yang Z wrote:
>> > 6) Setting the clock after 500 ms happens not on every set, but only when moving
>> > out of divider reset (register A bits 5-7 moving from 110 or 111 to 010).  As far as
>> > I can read, SET prevents the registers from changing value, but keeps the internal
>> > sub-second counters running.
> Do we really need this logic? It sounds like senseless. 

It doesn't seem hard to do, see my branch.

Paolo

  reply	other threads:[~2012-02-23  6:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-20  0:24 [PATCH v2 0/4] RTC: New logic to emulate RTC Zhang, Yang Z
2012-02-20  0:24 ` [Qemu-devel] " Zhang, Yang Z
2012-02-20  7:41 ` Paolo Bonzini
2012-02-20  7:41   ` [Qemu-devel] " Paolo Bonzini
2012-02-21  0:00   ` Zhang, Yang Z
2012-02-21  0:00     ` [Qemu-devel] " Zhang, Yang Z
2012-02-22 11:19     ` Paolo Bonzini
2012-02-22 11:19       ` [Qemu-devel] " Paolo Bonzini
2012-02-23  1:49       ` Zhang, Yang Z
2012-02-23  1:49         ` [Qemu-devel] " Zhang, Yang Z
2012-02-23  6:51         ` Paolo Bonzini [this message]
2012-02-23  6:51           ` Paolo Bonzini
2012-02-23  7:43         ` Paolo Bonzini
2012-02-23  7:43           ` [Qemu-devel] " Paolo Bonzini
2012-02-24  0:55       ` Zhang, Yang Z
2012-02-24  0:55         ` [Qemu-devel] " Zhang, Yang Z
2012-02-24  6:56         ` Paolo Bonzini
2012-02-24  6:56           ` [Qemu-devel] " 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=4F45E208.4020101@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 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.