From: Dor Laor <dlaor@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCHv2] Add rtc reset function.
Date: Tue, 09 Jun 2009 14:43:13 +0300 [thread overview]
Message-ID: <4A2E4AD1.2080900@redhat.com> (raw)
In-Reply-To: <20090609103941.GV27210@redhat.com>
Gleb Natapov wrote:
> On Tue, Jun 09, 2009 at 12:23:21PM +0200, Jan Kiszka wrote:
>
>>> +static void rtc_reset(void *opaque)
>>> +{
>>> + RTCState *s = opaque;
>>> +
>>> + s->cmos_data[RTC_REG_B] &= ~(REG_B_PIE | REG_B_AIE | REG_B_SQWE);
>>> + s->cmos_data[RTC_REG_C] &= ~(REG_C_UF | REG_C_IRQF | REG_C_PF | REG_C_AF);
>>> +
>>> + qemu_irq_lower(s->irq);
>>> +
>>> +#ifdef TARGET_I386
>>> + if (rtc_td_hack)
>>> + s->irq_coalesced = 0;
>>>
>> Sorry, missed that on first run: Isn't it safer, clearer, more beautiful
>> to reset this unconditionally?
>>
>>
> It doesn't really matter. From safety point of view the code is safe.
>
>
Actually we should drop this rtc-td-hack flag entirely.
The time drift fix is now only compiled for x86 so it will be harmless
for other arch.
Users are affected by not calling it although it is a must for every OS
that uses rtc clock source
and cannot deal with drifts (aka all windows, and some of the Linux guests).
Anthony, will you accept such a patch to remove rtc-td-hack or at least
change it's default?
> --
> Gleb.
>
>
>
next prev parent reply other threads:[~2009-06-09 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 9:26 [Qemu-devel] [PATCHv2] Add rtc reset function Gleb Natapov
2009-06-09 10:23 ` [Qemu-devel] " Jan Kiszka
2009-06-09 10:39 ` Gleb Natapov
2009-06-09 11:43 ` Dor Laor [this message]
2009-06-09 15:45 ` [Qemu-devel] " Marcelo Tosatti
2009-06-09 15:48 ` Gleb Natapov
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=4A2E4AD1.2080900@redhat.com \
--to=dlaor@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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).