Eric Saxe wrote: >> >> I'm proposing that we create a new mdb routine - mdb_get_lbolt() - to >> provide the value those consumers expect. >> >> I think you answered my first question. Since cyclics don't fire when >> booted into kmdb, we can safely return a lbolt value of zero. > I don't think that will work. The genunix module (for example) reads > lbolt, and figures a delta for the last time a thread switched off the > CPU...so using 0 for that won't work. I think this again highlights the need for (even with a tickless lbolt service) to have a reliable clock_t based reference time available...and this is true within the context of the debugger looking at a stopped kernel, and also to keep in crash dumps (more of a concern for savecore -L since figuring panic_lbolt while panicking is easy enough). It would be ideal to stash this in a demand based fashion, so updating something either when savecore -L is run, or when making the transition into the debugger. Then perhaps that thing that is stashed could be what a ::time dcmd provides...
-Eric
