From: john stultz <johnstul@us.ibm.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] generic clocksource updates
Date: Fri, 07 Apr 2006 14:08:45 -0700 [thread overview]
Message-ID: <1144444126.2745.125.camel@leatherman> (raw)
In-Reply-To: <Pine.LNX.4.64.0604072239110.32445@scrub.home>
On Fri, 2006-04-07 at 22:43 +0200, Roman Zippel wrote:
> Hi,
>
> On Thu, 6 Apr 2006, Thomas Gleixner wrote:
>
> > > Currently this field isn't needed and as soon we have a need for it, we
> > > can add proper capability information.
> >
> > Is there a reason, why requirements which are known from existing
> > experience must be discarded to be reintroduced later ?
>
> Then please explain these requirements.
> This field shouldn't have been added in first place, I guess I managed to
> confuse John when I talked about handling of continuous vs. tick based
> clocks. Currently no user should even care about this, it's an
> implementation detail of the clock.
I don't think you confused me on this issue (although, I admit I'm prone
to confusion).
The is_continuous flag on the clocksource is used so other systems can
query if timekeeping is able to function without regular timer ticks.
This would be necessary for the HRT patchset, as well as the dynamic
tick patches, as they both reprograms the tick frequency, and need to
know if that will affect time.
I can reasonably drop this bit from the current patches, but it is very
small and and will be needed shortly, so I'm not sure its that big of a
deal.
thanks
-john
next prev parent reply other threads:[~2006-04-07 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 19:55 [PATCH 1/5] generic clocksource updates Roman Zippel
2006-04-06 10:06 ` Thomas Gleixner
2006-04-06 19:00 ` Roman Zippel
2006-04-06 19:32 ` Thomas Gleixner
2006-04-07 20:43 ` Roman Zippel
2006-04-07 21:08 ` john stultz [this message]
2006-04-07 22:40 ` Thomas Gleixner
2006-04-12 11:16 ` Roman Zippel
2006-04-07 18:38 ` john stultz
2006-04-27 20:41 ` Roman Zippel
2006-05-06 2:27 ` john stultz
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=1144444126.2745.125.camel@leatherman \
--to=johnstul@us.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zippel@linux-m68k.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 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.