From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.25.208.211 with SMTP id h202csp1017281lfg; Fri, 11 Mar 2016 05:22:33 -0800 (PST) X-Received: by 10.66.191.225 with SMTP id hb1mr15134129pac.78.1457702553357; Fri, 11 Mar 2016 05:22:33 -0800 (PST) Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id tw5si2706747pac.131.2016.03.11.05.22.33; Fri, 11 Mar 2016 05:22:33 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of kvm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of kvm-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=kvm-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752735AbcCKNWb (ORCPT + 7 others); Fri, 11 Mar 2016 08:22:31 -0500 Received: from e06smtp08.uk.ibm.com ([195.75.94.104]:54870 "EHLO e06smtp08.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752272AbcCKNWa (ORCPT ); Fri, 11 Mar 2016 08:22:30 -0500 Received: from localhost by e06smtp08.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 11 Mar 2016 13:22:28 -0000 Received: from d06dlp01.portsmouth.uk.ibm.com (9.149.20.13) by e06smtp08.uk.ibm.com (192.168.101.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Fri, 11 Mar 2016 13:22:26 -0000 X-IBM-Helo: d06dlp01.portsmouth.uk.ibm.com X-IBM-MailFrom: borntraeger@de.ibm.com X-IBM-RcptTo: kvm@vger.kernel.org Received: from b06cxnps4076.portsmouth.uk.ibm.com (d06relay13.portsmouth.uk.ibm.com [9.149.109.198]) by d06dlp01.portsmouth.uk.ibm.com (Postfix) with ESMTP id CE4BC17D8056 for ; Fri, 11 Mar 2016 13:22:54 +0000 (GMT) Received: from d06av02.portsmouth.uk.ibm.com (d06av02.portsmouth.uk.ibm.com [9.149.37.228]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id u2BDMP4u61931674 for ; Fri, 11 Mar 2016 13:22:25 GMT Received: from d06av02.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av02.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id u2BDMOPA028230 for ; Fri, 11 Mar 2016 06:22:25 -0700 Received: from oc1450873852.ibm.com (sig-9-83-187-232.evts.uk.ibm.com [9.83.187.232]) by d06av02.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id u2BDMLje028096; Fri, 11 Mar 2016 06:22:21 -0700 Subject: Re: [PATCH] Replacing (and removing) get_ticks_per_sec() function with NANOSECONDS_PER_SECOND Signed-off-by: Rutuja Shah To: Paolo Bonzini , rutu.shah.26@gmail.com, qemu-devel@nongnu.org References: <1457638209-14218-1-git-send-email-rutu.shah.26@gmail.com> <56E2AFA1.5010201@de.ibm.com> <56E2B4EA.4050305@redhat.com> <56E2B629.7080405@de.ibm.com> <56E2B984.2050300@redhat.com> Cc: kraxel@redhat.com, samuel.thibault@ens-lyon.org, stefanha@redhat.com, kwolf@redhat.com, crosthwaite.peter@gmail.com, rth@twiddle.net, mst@redhat.com, imammedo@redhat.com, peter.maydell@linaro.org, balrogg@gmail.com, jsnow@redhat.com, alistair.francis@xilinx.com, agraf@suse.de, jasowang@redhat.com, blauwirbel@gmail.co, mark.cave-ayland@ilande.co.uk, cornelia.huck@de.ibm.com, lcapitulino@redhat.com, armbru@redhat.com, qemu-block@nongnu.org, qemu-arm@nongnu.org, qemu-ppc@nongnu.org, kvm@vger.kernel.org From: Christian Borntraeger Message-ID: <56E2C68D.4010502@de.ibm.com> Date: Fri, 11 Mar 2016 14:22:21 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E2B984.2050300@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16031113-0033-0000-0000-0000063BA276 Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org X-TUID: TXVne6260CAH On 03/11/2016 01:26 PM, Paolo Bonzini wrote: > > > On 11/03/2016 13:12, Christian Borntraeger wrote: >> On 03/11/2016 01:07 PM, Paolo Bonzini wrote: >>> >>> >>> On 11/03/2016 12:44, Christian Borntraeger wrote: >>>>> - s->tick_offset_vmstate = s->tick_offset + delta / get_ticks_per_sec(); >>>>>> + s->tick_offset_vmstate = s->tick_offset + delta / NANOSECONDS_PER_SECOND; >>>> [...] >>>> >>>> While technically correct, I do not like these changes. The interfaces expect "ticks", >>>> and the fact that this happens to be a nanosecond does not help regarding >>>> readability. >>> >>> Actually, I think usage of "tick" in this file is just for historical >>> reasons. >> >> So in essence the patch is ok and we should try to get rid of the "tick" word in future >> patches? > > Not necessarily. The patch stops overloading the word "tick", so that > "tick" means "whatever the timer device counts". > > In fact, you and I were both confused by the appearance of the word > "tick" in get_ticks_per_sec(). [...] > the plus meant nanoseconds. And I got confused *despite being the > author of that line* (commit b0f2663, "pl031: switch clock base to > rtc_clock", 2012-03-30). Given the confusion, the patch description should contain some of these examples and an explanation why this is the right thing to do. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH] Replacing (and removing) get_ticks_per_sec() function with NANOSECONDS_PER_SECOND Signed-off-by: Rutuja Shah Date: Fri, 11 Mar 2016 14:22:21 +0100 Message-ID: <56E2C68D.4010502@de.ibm.com> References: <1457638209-14218-1-git-send-email-rutu.shah.26@gmail.com> <56E2AFA1.5010201@de.ibm.com> <56E2B4EA.4050305@redhat.com> <56E2B629.7080405@de.ibm.com> <56E2B984.2050300@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: peter.maydell@linaro.org, kvm@vger.kernel.org, mst@redhat.com, jasowang@redhat.com, mark.cave-ayland@ilande.co.uk, lcapitulino@redhat.com, kraxel@redhat.com, qemu-block@nongnu.org, agraf@suse.de, samuel.thibault@ens-lyon.org, balrogg@gmail.com, alistair.francis@xilinx.com, qemu-arm@nongnu.org, stefanha@redhat.com, cornelia.huck@de.ibm.com, rth@twiddle.net, kwolf@redhat.com, crosthwaite.peter@gmail.com, armbru@redhat.com, blauwirbel@gmail.co, qemu-ppc@nongnu.org, imammedo@redhat.com To: Paolo Bonzini , rutu.shah.26@gmail.com, qemu-devel@nongnu.org Return-path: In-Reply-To: <56E2B984.2050300@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-block-bounces+gceqb-qemu-block=m.gmane.org@nongnu.org Sender: qemu-block-bounces+gceqb-qemu-block=m.gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 03/11/2016 01:26 PM, Paolo Bonzini wrote: > > > On 11/03/2016 13:12, Christian Borntraeger wrote: >> On 03/11/2016 01:07 PM, Paolo Bonzini wrote: >>> >>> >>> On 11/03/2016 12:44, Christian Borntraeger wrote: >>>>> - s->tick_offset_vmstate = s->tick_offset + delta / get_ticks_per_sec(); >>>>>> + s->tick_offset_vmstate = s->tick_offset + delta / NANOSECONDS_PER_SECOND; >>>> [...] >>>> >>>> While technically correct, I do not like these changes. The interfaces expect "ticks", >>>> and the fact that this happens to be a nanosecond does not help regarding >>>> readability. >>> >>> Actually, I think usage of "tick" in this file is just for historical >>> reasons. >> >> So in essence the patch is ok and we should try to get rid of the "tick" word in future >> patches? > > Not necessarily. The patch stops overloading the word "tick", so that > "tick" means "whatever the timer device counts". > > In fact, you and I were both confused by the appearance of the word > "tick" in get_ticks_per_sec(). [...] > the plus meant nanoseconds. And I got confused *despite being the > author of that line* (commit b0f2663, "pl031: switch clock base to > rtc_clock", 2012-03-30). Given the confusion, the patch description should contain some of these examples and an explanation why this is the right thing to do. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47789) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeN1U-0002Ys-ED for qemu-devel@nongnu.org; Fri, 11 Mar 2016 08:22:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aeN1S-00071z-JU for qemu-devel@nongnu.org; Fri, 11 Mar 2016 08:22:32 -0500 Received: from e06smtp09.uk.ibm.com ([195.75.94.105]:47602) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aeN1S-00070G-Ax for qemu-devel@nongnu.org; Fri, 11 Mar 2016 08:22:30 -0500 Received: from localhost by e06smtp09.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Fri, 11 Mar 2016 13:22:28 -0000 References: <1457638209-14218-1-git-send-email-rutu.shah.26@gmail.com> <56E2AFA1.5010201@de.ibm.com> <56E2B4EA.4050305@redhat.com> <56E2B629.7080405@de.ibm.com> <56E2B984.2050300@redhat.com> From: Christian Borntraeger Message-ID: <56E2C68D.4010502@de.ibm.com> Date: Fri, 11 Mar 2016 14:22:21 +0100 MIME-Version: 1.0 In-Reply-To: <56E2B984.2050300@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Replacing (and removing) get_ticks_per_sec() function with NANOSECONDS_PER_SECOND Signed-off-by: Rutuja Shah List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini , rutu.shah.26@gmail.com, qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, kvm@vger.kernel.org, mst@redhat.com, jasowang@redhat.com, mark.cave-ayland@ilande.co.uk, lcapitulino@redhat.com, kraxel@redhat.com, qemu-block@nongnu.org, agraf@suse.de, samuel.thibault@ens-lyon.org, alistair.francis@xilinx.com, qemu-arm@nongnu.org, stefanha@redhat.com, cornelia.huck@de.ibm.com, jsnow@redhat.com, rth@twiddle.net, kwolf@redhat.com, crosthwaite.peter@gmail.com, armbru@redhat.com, blauwirbel@gmail.co, qemu-ppc@nongnu.org, imammedo@redhat.com On 03/11/2016 01:26 PM, Paolo Bonzini wrote: > > > On 11/03/2016 13:12, Christian Borntraeger wrote: >> On 03/11/2016 01:07 PM, Paolo Bonzini wrote: >>> >>> >>> On 11/03/2016 12:44, Christian Borntraeger wrote: >>>>> - s->tick_offset_vmstate = s->tick_offset + delta / get_ticks_per_sec(); >>>>>> + s->tick_offset_vmstate = s->tick_offset + delta / NANOSECONDS_PER_SECOND; >>>> [...] >>>> >>>> While technically correct, I do not like these changes. The interfaces expect "ticks", >>>> and the fact that this happens to be a nanosecond does not help regarding >>>> readability. >>> >>> Actually, I think usage of "tick" in this file is just for historical >>> reasons. >> >> So in essence the patch is ok and we should try to get rid of the "tick" word in future >> patches? > > Not necessarily. The patch stops overloading the word "tick", so that > "tick" means "whatever the timer device counts". > > In fact, you and I were both confused by the appearance of the word > "tick" in get_ticks_per_sec(). [...] > the plus meant nanoseconds. And I got confused *despite being the > author of that line* (commit b0f2663, "pl031: switch clock base to > rtc_clock", 2012-03-30). Given the confusion, the patch description should contain some of these examples and an explanation why this is the right thing to do.