public inbox for kvmarm@lists.cs.columbia.edu
 help / color / mirror / Atom feed
From: Sagar Arun Kamble <sagar.a.kamble@intel.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Chris Wilson <chris@chris-wilson.co.uk>,
	John Stultz <john.stultz@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
	alsa-devel@alsa-project.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct
Date: Mon, 4 Dec 2017 10:43:05 +0530	[thread overview]
Message-ID: <8cfdbb16-7053-1d8f-adae-4ce2487fe4ea@intel.com> (raw)
In-Reply-To: <20171202180458.winwznbstsi355ed@localhost>



On 12/2/2017 11:34 PM, Richard Cochran wrote:
> On Sat, Dec 02, 2017 at 10:01:35AM +0530, Sagar Arun Kamble wrote:
>> There is no real need for the users of timecounters to define cyclecounter
>> and timecounter variables separately. Since timecounter will always be
>> based on cyclecounter, have cyclecounter struct as member of timecounter
>> struct.
> Overall, this is a welcome change.  However, it doesn't go far enough,
> IMHO, and I'll explain that more below.
>
>> diff --git a/drivers/net/ethernet/mellanox/mlx4/en_clock.c b/drivers/net/ethernet/mellanox/mlx4/en_clock.c
>> index 0247885..35987b5 100644
>> --- a/drivers/net/ethernet/mellanox/mlx4/en_clock.c
>> +++ b/drivers/net/ethernet/mellanox/mlx4/en_clock.c
> ...
>
> As it stands now, timecounter_init() is used for two totally different
> reasons.  Some callers only want to set the time, ...
>
>> @@ -207,7 +207,7 @@ static int mlx4_en_phc_settime(struct ptp_clock_info *ptp,
>>   
>>   	/* reset the timecounter */
>>   	write_seqlock_irqsave(&mdev->clock_lock, flags);
>> -	timecounter_init(&mdev->clock, &mdev->cycles, ns);
>> +	timecounter_init(&mdev->clock, ns);
>>   	write_sequnlock_irqrestore(&mdev->clock_lock, flags);
>>   
>>   	return 0;
> ... while others initialize the data structure the first time:
>
>> @@ -274,17 +274,17 @@ void mlx4_en_init_timestamp(struct mlx4_en_dev *mdev)
>>   
>>   	seqlock_init(&mdev->clock_lock);
>>   
>> -	memset(&mdev->cycles, 0, sizeof(mdev->cycles));
>> -	mdev->cycles.read = mlx4_en_read_clock;
>> -	mdev->cycles.mask = CLOCKSOURCE_MASK(48);
>> -	mdev->cycles.shift = freq_to_shift(dev->caps.hca_core_clock);
>> -	mdev->cycles.mult =
>> -		clocksource_khz2mult(1000 * dev->caps.hca_core_clock, mdev->cycles.shift);
>> -	mdev->nominal_c_mult = mdev->cycles.mult;
>> +	memset(&mdev->clock.cc, 0, sizeof(mdev->clock.cc));
>> +	mdev->clock.cc.read = mlx4_en_read_clock;
>> +	mdev->clock.cc.mask = CLOCKSOURCE_MASK(48);
>> +	mdev->clock.cc.shift = freq_to_shift(dev->caps.hca_core_clock);
>> +	mdev->clock.cc.mult =
>> +		clocksource_khz2mult(1000 * dev->caps.hca_core_clock,
>> +				     mdev->clock.cc.shift);
>> +	mdev->nominal_c_mult = mdev->clock.cc.mult;
>>   
>>   	write_seqlock_irqsave(&mdev->clock_lock, flags);
>> -	timecounter_init(&mdev->clock, &mdev->cycles,
>> -			 ktime_to_ns(ktime_get_real()));
>> +	timecounter_init(&mdev->clock, ktime_to_ns(ktime_get_real()));
> I'd like to see two followup patches to this one:
>
> 1. Convert timecounter_init() callers to a new timecounter_reset()
>     function where the intent is to reset the time.
>
> 2. Change timecounter_init() to take the cyclecounter fields as
>     arguments.
>
> 	void timecounter_init(struct timecounter *tc,
> 			      u64 (*read)(const struct cyclecounter *cc),
> 			      u64 mask,
> 			      u32 mult,
> 			      u32 shift,
> 			      u64 start_tstamp);
>
> Then we can clean up all this stuff:
>
> 	mdev->clock.cc.read = mlx4_en_read_clock;
> 	mdev->clock.cc.mask = CLOCKSOURCE_MASK(48);
> 	mdev->clock.cc.shift = freq_to_shift(dev->caps.hca_core_clock);
> 	mdev->clock.cc.mult = clocksource_khz2mult(...);
>
> This second step can be phased in by calling the new function
> timecounter_initialize() and converting the drivers one by one.

Yes. Will make these changes and share new patchset.

Thank you for the review Richard.

Regards,
Sagar

>> diff --git a/include/linux/timecounter.h b/include/linux/timecounter.h
>> index 2496ad4..6daca06 100644
>> --- a/include/linux/timecounter.h
>> +++ b/include/linux/timecounter.h
> ...
>> @@ -98,7 +98,6 @@ static inline void timecounter_adjtime(struct timecounter *tc, s64 delta)
>>   /**
>>    * timecounter_init - initialize a time counter
>>    * @tc:			Pointer to time counter which is to be initialized/reset
>> - * @cc:			A cycle counter, ready to be used.
> This "ready to used" requirement should go.  The init() function
> should make the instance ready to be used all at once.
>
> Thanks,
> Richard

  reply	other threads:[~2017-12-04  5:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02  4:31 [PATCH 1/1] timecounter: Make cyclecounter struct part of timecounter struct Sagar Arun Kamble
2017-12-02 18:04 ` Richard Cochran
2017-12-04  5:13   ` Sagar Arun Kamble [this message]
     [not found] ` <1512189095-28654-1-git-send-email-sagar.a.kamble-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-12-06 16:24   ` [Intel-wired-lan] " Jeff Kirsher
2018-01-06  4:29     ` Brown, Aaron F
  -- strict thread matches above, loose matches on Subject: below --
2017-12-01  7:47 Sagar Arun Kamble
2017-12-01 15:56 ` Richard Cochran

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=8cfdbb16-7053-1d8f-adae-4ce2487fe4ea@intel.com \
    --to=sagar.a.kamble@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=john.stultz@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=sboyd@codeaurora.org \
    --cc=tglx@linutronix.de \
    /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