But then the all-knowing Time-Keepers emerged, bringing peace by reorganizing the multiverse into a single timeline, the ‘sacred timeline’.” Countless unique timelines battled each other for supremacy, nearly resulting in the total destruction of, well, everything. “Long ago, there was a vast multiversal war. Statues of the three figures are basically everywhere you look, and their faces hang over Judge Ravonna Renslayer ( Gugu Mbatha-Raw) as she attempts to sentence Loki - before Mobius steps in with his idea to use Loki instead of disintegrating him.īut their origin within the MCU is explained by the adorable cartoon character Miss Minutes, who reveals that before the Timekeepers came along, a multiverse existed: The Time-Keepers are introduced in the first episode of Loki, looming over every aspect of the TVA without actually being revealed. And in the comics, they often use a pawn who goes by the name Immortus to do their bidding, although Immortus sometimes listens and sometimes betrays the Timekeepers, so Immortus has been both friend and foe to the Avengers. In fact, their first interaction with the main Marvel timeline found them trying to break up the Avengers before Earth’s Mightiest Heroes could threaten their authority. He Who Remains created and put the Timekeepers in place just as the universe was about to end, in an attempt to course-correct the time-flow of the universe.īut the Timekeepers have not necessarily been viewed as “the good guys” through their time in the comics. The origin of these three beings is tied to the origin of the TVA, as in the comics the Timekeepers were actually created by a character named He Who Remains, the very last director of the Time Variance Authority from the last reality. Thread overview: 2+ messages (download: mbox.In Marvel Comics lore, the Timekeepers as characters first appeared in an issue of Thor way back in 1979. ^ raw reply 2+ messages in threadĮnd of thread, other threads: Void ktime_get_coarse_real_ts64(struct timespec64 *ts) ![]() Int -1409,7 +1409,7 int timekeeping_notify(struct clocksource *clock) Void ktime_get_snapshot(struct system_time_snapshot *systime_snapshot) Ktime_t ktime_mono_to_any(ktime_t tmono, enum tk_offsets offs)ĭo -960,7 +960,7 time64_t _ktime_get_real_seconds(void) Struct timekeeper *tk = &tk_core.timekeeper Void ktime_get_real_ts64(struct timespec64 *ts) +++ -720,7 +720,7 static void timekeeping_forward_now(struct timekeeper *tk) * Read jiffies and the time when jiffies were updated last */ĭiff -git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c U64 basemono, next_tick, next_tmr, next_rcu, delta, expires Static ktime_t tick_nohz_next_event(struct tick_sched *ts, int cpu) +++ -645,7 +645,8 static inline bool local_timer_softirq_pending(void) +++ -149,7 +149,7 void tick_setup_periodic(struct clock_event_device *dev, int broadcast)Ĭlockevents_switch_state(dev, CLOCK_EVT_STATE_PERIODIC) ĭiff -git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c + unsigned int seq = raw_read_seqcount(&cd.seq) ĭiff -git a/kernel/time/tick-common.c b/kernel/time/tick-common.c unsigned long seq = raw_read_seqcount(&cd.seq) Static u64 notrace suspended_sched_clock_read(void) Unsigned long long notrace sched_clock(void)ĭo -267,7 +267,7 void _init generic_sched_clock_init(void) Since the seqlock.h API isĮntirely based on unsigned int, use that throughout.ĭiff -git a/kernel/time/sched_clock.c b/kernel/time/sched_clock.c ![]() Int" for the seqcount snapshots (ratio 14:12). The timekeeping code uses a random mix of "unsigned long" and "unsigned Timekeeping: Consistently use unsigned int for seqcount snapshot +++ -63,7 +63,7 _cacheline_aligned_in_smp DEFINE_SEQLOCK(jiffies_lock) Kernel/time/timekeeping.c | 18 +++++++++-ĥ files changed, 15 insertions(+), 14 deletions(-)ĭiff -git a/kernel/time/jiffies.c b/kernel/time/jiffies.c Seqlock.h API is entirely based on unsigned (int), use that "unsigned int" for the seqcount snapshots (ratio 14:12). The timekeeping code uses a random mix of "unsigned long" and To: Frederic Weisbecker, Thomas Gleixner, Ingo Molnar, John Stultz, ![]() ![]() 10:46 ` timekeeping: Consistently " tip-bot for Rasmus VillemoesĠ siblings, 1 reply 2+ messages in threadįrom: Rasmus Villemoes 19:55 UTC ( / raw) Timekeeping: consistently use unsigned int for seqcount snapshot LKML Archive on help / color / mirror / Atom feed * timekeeping: consistently use unsigned int for seqcount snapshot 19:55 Rasmus Villemoes
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |