On Tue, 8 Apr 2014 20:56:13 +0200
Frederic Weisbecker wrote:
> So it may indeed be a better idea to first create a standalone
> jiffies_to_nsecs().
> It can then be used to deprecate and replace most (if not all) calls to
> jiffies_to_usecs()
> altogether. Just the conversion must be made one
On Tue, Apr 08, 2014 at 02:15:43PM -0400, Steven Rostedt wrote:
> On Tue, 8 Apr 2014 19:49:51 +0200
> Frederic Weisbecker wrote:
>
> > On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
> > > On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
> > >
> > > > c) If not this ... then what?
On Tue, 8 Apr 2014 19:49:51 +0200
Frederic Weisbecker wrote:
> On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
> > On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
> >
> > > c) If not this ... then what? Separate routine to convert large numbers
> > >of jiffies to usec/nsecs?
On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
> On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
>
> > c) If not this ... then what? Separate routine to convert large numbers
> >of jiffies to usec/nsecs? Should we make the existing one barf when
> >handed a number that
On Mon, 7 Apr 2014 22:34:51 -0700
Tony Luck wrote:
> On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
>
> > c) If not this ... then what? Separate routine to convert large numbers
> >of jiffies to usec/nsecs? Should we make the existing one barf when
> >handed a number that overflows?
On Mon, 7 Apr 2014 22:34:51 -0700
Tony Luck tony.l...@gmail.com wrote:
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck tony.l...@intel.com wrote:
c) If not this ... then what? Separate routine to convert large numbers
of jiffies to usec/nsecs? Should we make the existing one barf when
On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck tony.l...@intel.com wrote:
c) If not this ... then what? Separate routine to convert large numbers
of jiffies to usec/nsecs? Should we make the existing one barf when
handed a
On Tue, 8 Apr 2014 19:49:51 +0200
Frederic Weisbecker fweis...@gmail.com wrote:
On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck tony.l...@intel.com wrote:
c) If not this ... then what? Separate routine to convert large numbers
of
On Tue, Apr 08, 2014 at 02:15:43PM -0400, Steven Rostedt wrote:
On Tue, 8 Apr 2014 19:49:51 +0200
Frederic Weisbecker fweis...@gmail.com wrote:
On Mon, Apr 07, 2014 at 10:34:51PM -0700, Tony Luck wrote:
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck tony.l...@intel.com wrote:
c) If not
On Tue, 8 Apr 2014 20:56:13 +0200
Frederic Weisbecker fweis...@gmail.com wrote:
So it may indeed be a better idea to first create a standalone
jiffies_to_nsecs().
It can then be used to deprecate and replace most (if not all) calls to
jiffies_to_usecs()
altogether. Just the conversion
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck wrote:
> c) If not this ... then what? Separate routine to convert large numbers
>of jiffies to usec/nsecs? Should we make the existing one barf when
>handed a number that overflows?
Having thought about this a bit more - I'm leaning towards
jiffies_to_usecs() returns an "int" so it can only handle times up to
2^32 microseconds (1 hour 11 minutes 34 seconds) before truncation
occurs. This is a problem for the "uptime" trace clock added in
commit 8aacf017b065a805d27467843490c976835eb4a5
tracing: Add "uptime" trace clock that
jiffies_to_usecs() returns an int so it can only handle times up to
2^32 microseconds (1 hour 11 minutes 34 seconds) before truncation
occurs. This is a problem for the uptime trace clock added in
commit 8aacf017b065a805d27467843490c976835eb4a5
tracing: Add uptime trace clock that uses
On Mon, Apr 7, 2014 at 3:25 PM, Tony Luck tony.l...@intel.com wrote:
c) If not this ... then what? Separate routine to convert large numbers
of jiffies to usec/nsecs? Should we make the existing one barf when
handed a number that overflows?
Having thought about this a bit more - I'm
14 matches
Mail list logo
