Re: [PATCH 1/2] RFC cyclictest: clean up --latency ordering in getopt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is the resulting message on the ARM panda with a 'bad'
32khz timer:


  # cyclictest -q -p 80 -t -n -l 10 -h ${hist_bins} -R 100
  reported clock resolution: 1 nsec
  measured clock resolution less than: 30517 nsec


A possible follow on patch would be to generate a hard
error (fail the test) if the measured resolution was
above some unreasonable value (perhaps > 1 msec), but
allow the hard fail to be overridden with yet another
command line option.  Any opinions about that?

-Frank

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux