| /freebsd/sys/kern/ |
| H A D | kern_tslog.c | 51 } timestamps[TSLOGSIZE]; variable
67 if (pos < nitems(timestamps)) { in tslog()
68 timestamps[pos].td = td; in tslog()
69 timestamps[pos].type = type; in tslog()
70 timestamps[pos].f = f; in tslog()
71 timestamps[pos].s = s; in tslog()
72 timestamps[pos].tsc = tsc; in tslog()
105 limit = MIN(nrecs, nitems(timestamps)); in sysctl_debug_tslog()
107 sbuf_printf(sb, "%p", timestamps[i].td); in sysctl_debug_tslog()
109 (unsigned long long)timestamps[i].tsc); in sysctl_debug_tslog()
[all …]
|
| /freebsd/contrib/tzdata/ |
| H A D | NEWS | 8 Changes to future timestamps
16 Changes to past timestamps
35 Changes to future timestamps
40 This affects timestamps starting 2025-03-22, as well as the
43 Changes to past timestamps
45 Correct timestamps for the Philippines before 1900, and from 1937
112 The code now conforms to RFC 8536 for early timestamps.
117 Changes to past timestamps
125 official Mexican decrees. The affected timestamps occur during
139 timestamps between 1977 and 1993 depending on the region. In
[all …]
|
| H A D | theory.html | 40 whose clocks all agree about timestamps that occur after the <a
59 with current and future timestamps in the traditional North
64 Applications that also deal with past timestamps in the mountain time
68 time but differs from other timezones for some timestamps after 1970.
73 because most systems support timestamps before 1970 and could
359 timestamps correctly and it increased maintenance burden.
378 Applications that process only timestamps from now on can instead use the file
506 The others are for timestamps before 1960,
570 Use current abbreviations for older timestamps to avoid confusion.
576 timestamps a
[all...] |
| /freebsd/contrib/tzcode/ |
| H A D | NEWS | 9 The code now conforms to RFC 8536 for early timestamps.
14 Changes to past timestamps
22 official Mexican decrees. The affected timestamps occur during
36 timestamps between 1977 and 1993 depending on the region. In
53 These names, which for post-1970 timestamps mostly just duplicate
56 This affects behavior for TZ='EET' for some pre-1981 timestamps,
57 for TZ='CET' for some pre-1947 timestamps, and for TZ='WET' for
58 some pre-1996 timestamps. Also, TZ='MET' now behaves like
73 with Asia/Tashkent for future timestamps, due to Kazakhstan's
81 timestamps befor
[all...] |
| H A D | tzfile.5 | 150 for all timestamps;
151 otherwise, for timestamps before the first occurrence time,
177 is known to support this feature for timestamps past 2037,
181 and older timestamps need not be handled accurately.
235 timestamps after this expiration are unreliable in that future
237 the added leap seconds will change how post-expiration timestamps are treated.
262 agree with current readers about timestamps within the
272 post-expiration timestamps, or process them as if the expiration
321 made to limit glitches to rarely used timestamps and allow
335 version 2+ data even if the reader's native timestamps hav
[all...] |
| H A D | zic.8 | 67 mishandles timestamps after the year 2038 anyway.
123 Among other things it should not be used for timestamps after the year 2037,
131 to timestamps in the range from
147 omits data intended for negative timestamps (i.e., before the Epoch), and
149 outputs data intended only for nonnegative timestamps that fit into
164 Generate redundant trailing explicit transitions for timestamps
169 This option does not affect the represented timestamps.
239 These compatibility issues affect only timestamps
544 or for timestamps occurring before any rule takes effect.
555 any timestamps tha
[all...] |
| H A D | theory.html | 40 whose clocks all agree about timestamps that occur after the <a
59 with current and future timestamps in the traditional North
64 Applications that also deal with past timestamps in the mountain time
68 time but differs from other timezones for some timestamps after 1970.
73 because most systems support timestamps before 1970 and could
348 timestamps correctly and it increased maintenance burden.
367 Applications that process only timestamps from now on can instead use the file
495 The others are for timestamps before 1960,
559 Use current abbreviations for older timestamps to avoid confusion.
565 timestamps a
[all...] |
| H A D | newctime.3 | 86 The POSIX standard says that timestamps must be nonnegative
88 Many implementations extend POSIX by allowing negative timestamps,
89 and can therefore represent timestamps that predate the
|
| H A D | Makefile | 61 # * It does not work even in tzcode, except for historical timestamps
63 # Hence it typically does not work for current and future timestamps.
285 # This mishandles some past timestamps, as US DST rules have changed.
941 # Check timestamps from now through 28 years from now, to make sure
942 # that zonenow.tab contains all sequences of planned timestamps,
1063 # Set file timestamps deterministically if possible,
1064 # so that tarballs containing the timestamps are reproducible.
1067 # file DEST to the maximum of the timestamps of the files A B C ...,
1085 # downstream 'make' that considers equal timestamps to be out of date.
1092 # Set the timestamps t
[all...] |
| H A D | zdump.8 | 218 which uses UTC for modern timestamps and some other UT flavor for
219 timestamps that predate the introduction of UTC.
224 for older timestamps, partly because the exact date of the
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | varmod-gmtime.mk | 148 TIMESTAMPS+= $t
152 TIMESTAMPS+= $t
156 TIMESTAMPS+= $t
160 TIMESTAMPS+= $t
164 TIMESTAMPS+= $t
166 .for a b in ${TIMESTAMPS:[1]} ${TIMESTAMPS:@t@$t $t@} ${TIMESTAMPS:[-1]}
|
| /freebsd/contrib/pjdfstest/tests/utimensat/ |
| H A D | 06.t | 26 # First check that nobody can't update the timestamps
29 # Now check that the owner can update the timestamps
34 # Now check that the superuser can update the timestamps
37 # Now check that anyone with write permission can update the timestamps
|
| H A D | 07.t | 28 # First check that nobody can't update the timestamps
33 # Now check that a nonowner with write permission can't update the timestamps
39 # Now check that the owner can update the timestamps
44 # Now check that the superuser can update the timestamps
|
| H A D | 01.t | 16 TIME_MARGIN=300 # Allow up to a 5 minute delta between the timestamps
26 sleep 1 # Ensure that future timestamps will be different than this one
|
| /freebsd/sys/contrib/device-tree/Bindings/timestamp/ |
| H A D | hte-consumer.yaml | 15 timestamps:
30 timestamp-names: [ timestamps ]
37 timestamps = <&tegra_hte_aon 0x9>, <&tegra_hte_lic 0x19>;
|
| /freebsd/usr.sbin/fifolog/fifolog_create/ |
| H A D | fifolog.1 | 61 timestamps before it is written to storage, such that it is possible
154 option forces timestamps to be formatted as
171 layer that allows searches to synchronization points based on timestamps
195 Read it back with human readable timestamps:
|
| /freebsd/sbin/dmesg/ |
| H A D | dmesg.8 | 73 variables control how the kernel timestamps entries in the message buffer:
77 If set to 0, no timestamps are added.
84 The timestamps are placed at the start of most lines that the kernel generates.
|
| /freebsd/contrib/kyua/integration/ |
| H A D | utils.sh | 30 # Subcommand to strip out the durations and timestamps in a report.
33 # time deltas are replaced by the fixed string S.UUU and the timestamps are
54 # time deltas are replaced by the fixed string S.UUU and the timestamps are
67 # used along the utils_strip_times function so that the timestamps of
|
| /freebsd/usr.bin/kdump/ |
| H A D | kdump.1 | 60 Display elapsed timestamps (time since beginning of trace).
95 Display relative timestamps (time since previous entry).
104 Display absolute timestamps for each entry (seconds since epoch).
|
| /freebsd/contrib/ntp/html/drivers/ |
| H A D | driver7.html | 37 …des an independent timestamp upon arrival with a potential total of 60 timestamps for each minute.…
47 … that might be decoded at that position. In order to use the character timestamps, it is necessary…
51 …ng with the backdated timestamps accumulated over the minute. A perfect set of eight bursts could …
81 tsmp timestamps captured
91 <dd>Timestamp alarm. Fewer than 20 timestamps have been determined.</dd>
120 …timestamps determined during the most recent minute bursts were received. The values range from 0 …
|
| /freebsd/contrib/llvm-project/lldb/source/Plugins/Trace/intel-pt/ |
| H A D | TraceIntelPTOptions.td | 22 Desc<"Enable the use of TSC timestamps. This is supported on all "
74 "option forces the capture of TSC timestamps (see --tsc). Also, "
100 Desc<"Enable the use of TSC timestamps. This is supported on all "
|
| /freebsd/usr.bin/clang/llvm-ar/ |
| H A D | llvm-ar.1 | 82 By default, \fBllvm\-ar\fP always uses zero for timestamps and UIDs/GIDs
86 \fI\%U\fP modifier to write actual timestamps and UIDs/GIDs.
280 Use zero for timestamps and UIDs/GIDs. This is set by default.
310 timestamps.
315 Use actual timestamps and UIDs/GIDs.
|
| /freebsd/contrib/elftoolchain/libelftc/ |
| H A D | elftc_set_timestamps.3 | 31 .Nd set file timestamps
78 err(EXIT_FAILURE, "timestamps could not be set");
|
| /freebsd/usr.bin/truss/ |
| H A D | truss.1 | 53 Include timestamps in the output showing the time elapsed
56 Include timestamps in the output showing the time elapsed
|
| /freebsd/contrib/llvm-project/llvm/tools/llvm-objcopy/ |
| H A D | CommonOpts.td | 25 "zero for UIDs, GIDs, and timestamps).">;
33 "real values for UIDs, GIDs, and timestamps).">;
39 HelpText<"Preserve access and modification timestamps">;
|