public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 08/10] clocksource: add read2() callback
Date: Mon, 01 Dec 2008 20:57:44 +0000	[thread overview]
Message-ID: <1228165064.7176.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20081201103337.26620.38744.sendpatchset@rx1.opensource.se>

On Mon, 2008-12-01 at 19:33 +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
> 
> Add a read2() callback for clocksources. This callback is passing
> a pointer to struct clocksource which makes it easy to share the
> same callback for multiple clocksource instances.
> 
> The function clocksource_read() is modified to prefer read2() over
> read() if initialized.
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>

I'm still not yet totally sold on the reasons we need this change, but I
don't have any issue with this implementation. Hopefully the discussion
around the timer_inc code will help resolve my concerns.

Also, if we're going to go this way, you might want to add read() to the
feature-removal list and add a warning in clocksource_register() for any
clocksource that doesn't implement read2, just so we don't have to keep
both around forever

thanks
-john


> ---
> 
>  include/linux/clocksource.h |    4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> --- 0001/include/linux/clocksource.h
> +++ work/include/linux/clocksource.h	2008-11-27 13:58:25.000000000 +0900
> @@ -43,6 +43,7 @@ struct clocksource;
>   *				The ideal clocksource. A must-use where
>   *				available.
>   * @read:		returns a cycle value
> + * @read2:		returns a cycle value, passes clocksource as argument
>   * @mask:		bitmask for two's complement
>   *			subtraction of non 64 bit counters
>   * @mult:		cycle to nanosecond multiplier (adjusted by NTP)
> @@ -62,6 +63,7 @@ struct clocksource {
>  	struct list_head list;
>  	int rating;
>  	cycle_t (*read)(void);
> +	cycle_t (*read2)(struct clocksource *cs);
>  	cycle_t mask;
>  	u32 mult;
>  	u32 mult_orig;
> @@ -170,7 +172,7 @@ static inline u32 clocksource_hz2mult(u3
>   */
>  static inline cycle_t clocksource_read(struct clocksource *cs)
>  {
> -	return cs->read();
> +	return cs->read2 ? cs->read2(cs) : cs->read();
>  }
> 
>  /**


      reply	other threads:[~2008-12-01 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 10:33 [PATCH 08/10] clocksource: add read2() callback Magnus Damm
2008-12-01 20:57 ` john stultz [this message]

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=1228165064.7176.31.camel@localhost.localdomain \
    --to=johnstul@us.ibm.com \
    --cc=linux-sh@vger.kernel.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