From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: qemu-devel@nongnu.org, kvm <kvm@vger.kernel.org>,
gcosta@redhat.com, Anthony Liguori <anthony@codemonkey.ws>,
aliguori@us.ibm.com
Subject: Re: [PATCH 3/3] alleviate time drift with HPET periodic timers
Date: Tue, 22 Mar 2011 11:08:10 +0100 [thread overview]
Message-ID: <4D88750A.4050304@siemens.com> (raw)
In-Reply-To: <996058219.455940.1300788200730.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
On 2011-03-22 11:03, Ulrich Obergfell wrote:
>
>>> Part 3 of the patch implements the following options for the
>>> 'configure' script.
>>>
>>> --disable-hpet-driftfix
>>> --enable-hpet-driftfix
>>
>> I see no benefit in this configurability. Just make the driftfix
>> unconditionally available, runtime-disabled by default for now until it
>> matured and there is no downside in enabling it all the time.
>
>
> Many Thanks Jan,
>
> I enclosed the code in '#ifdef CONFIG_HPET_DRIFTFIX ... #endif'
> so that it can be easily identified (and removed if the generic API
> would be implemented some day). Since the ifdef's are already there
> I added the configuration option for convenience. As you don't see
> any benefit in this option, I can remove that part of the patch.
> However, I'd suggest to keep the ifdef's and do the following:
>
> - Rename to '#ifdef HPET_DRIFTFIX ... #endif' to make it clear that
> this is not controlled via a configuration option.
>
> - Add '#define HPET_DRIFTFIX' to hw/hpet_emul.h.
>
> Do you agree ?
Thanks to versioning control and feature-oriented commits, it's not very
hard to identify what code changes relate to which feature additions. So
I still don't see a need for that.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Ulrich Obergfell <uobergfe@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
kvm <kvm@vger.kernel.org>,
gcosta@redhat.com
Subject: [Qemu-devel] Re: [PATCH 3/3] alleviate time drift with HPET periodic timers
Date: Tue, 22 Mar 2011 11:08:10 +0100 [thread overview]
Message-ID: <4D88750A.4050304@siemens.com> (raw)
In-Reply-To: <996058219.455940.1300788200730.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
On 2011-03-22 11:03, Ulrich Obergfell wrote:
>
>>> Part 3 of the patch implements the following options for the
>>> 'configure' script.
>>>
>>> --disable-hpet-driftfix
>>> --enable-hpet-driftfix
>>
>> I see no benefit in this configurability. Just make the driftfix
>> unconditionally available, runtime-disabled by default for now until it
>> matured and there is no downside in enabling it all the time.
>
>
> Many Thanks Jan,
>
> I enclosed the code in '#ifdef CONFIG_HPET_DRIFTFIX ... #endif'
> so that it can be easily identified (and removed if the generic API
> would be implemented some day). Since the ifdef's are already there
> I added the configuration option for convenience. As you don't see
> any benefit in this option, I can remove that part of the patch.
> However, I'd suggest to keep the ifdef's and do the following:
>
> - Rename to '#ifdef HPET_DRIFTFIX ... #endif' to make it clear that
> this is not controlled via a configuration option.
>
> - Add '#define HPET_DRIFTFIX' to hw/hpet_emul.h.
>
> Do you agree ?
Thanks to versioning control and feature-oriented commits, it's not very
hard to identify what code changes relate to which feature additions. So
I still don't see a need for that.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2011-03-22 10:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1225303441.421235.1300462107604.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2011-03-18 15:55 ` [PATCH 3/3] alleviate time drift with HPET periodic timers Ulrich Obergfell
2011-03-18 15:55 ` [Qemu-devel] " Ulrich Obergfell
2011-03-19 9:44 ` Jan Kiszka
2011-03-19 9:44 ` [Qemu-devel] " Jan Kiszka
2011-03-22 10:03 ` Ulrich Obergfell
2011-03-22 10:03 ` [Qemu-devel] " Ulrich Obergfell
2011-03-22 10:08 ` Jan Kiszka [this message]
2011-03-22 10:08 ` Jan Kiszka
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=4D88750A.4050304@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=gcosta@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=uobergfe@redhat.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.