[Info-vax] Current expected range for x86-64 first boot date ?

[clair.grant@vmssoftware.com]

On Sunday, November 11, 2018 at 8:29:11 PM UTC-5, Simon Clubley wrote:
> On 2018-11-10, clair.grant at vmssoftware.com <clairgrant71 at gmail.com> wrote:
> >
> > We have now had eight fairly solid weeks of debug and things are moving quickly. The combination of Virtual Box (and its snapshot facility) and our booting from memory disk makes everything so much faster than anything we have ever had in the past.
> >
> > We have loaded all the images necessary for First Boot and executed their initialization routines. 
> >
> > First Boot? No idea. We are not on a schedule at this point, just debugging as fast as possible.
> >
> 
> Thank you for the update Clair.
> 
> Seeing reports like this are very useful as they tell us where you are
> in the development cycle so thanks for posting it.
> 
> Simon.
> 
> -- 
> Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
> Microsoft: Bringing you 1980s technology to a 21st century world

Another look at bringing up the system is the overall environment. Getting to the end of EXEC_INIT is a big deal; many things have to be working. You are in kernel mode and at IPL31.

Calling SCHED$INIT unleashes the beginnings of a much bigger environment, namely lowering IPL and changing modes. This brings into play much more of the newly-written x86-specific code, in particular page tables for the outer modes, switching modes, and creating a process. Here is recent (yesterday) output including temporary develop helpers.

%EXECINIT-I-ACTIVESET, joining ACTIVE set
%EXECINIT-S-CIAO, transferring to the scheduler
Lowering ipl to 3
Acquiring SCHED lock at IPL 8
Find next process to schedule; curktb = 0
New ktb: 800a9718
Find structures for new thread
Mark cpu active
Switch context
SWPCTX   FFFFFFFF858B4620
FNDHWPCB
LOG IT
SAVExSP
SAVEUNQ
SAVEASTx
SAVERSP
SAVEIDEP
SWPCC
LOADPTBR
  NEWPCB FFFFFFFF800A8880
     ASN 00000000000003FF
    PTBR 0000000000EDC000
     CR3 0000000000EDC3FF
LOADRSP
LOADASTx
LOADHPCB
LOADIDEP
LOADUNQ
LOADxSP
LOG IT
FIRSTUSE
XRSTOR   FFFF8300103484C0
CLRREGS
FUNC
    FUNC FFFFFFFF858B4620
Never scheduled
find structures again
Release sched lock
Lower ipl to ASTDEL
newhwpcb: 800a8880
sch$ar_swppcb(800a9718)->pcb$l_phd(800a8800)->phd$q_hwpcb(@800a8880)
Enter swapper main loop
%SWAPPER-I-SHUFFLE, executing SWAPPER initialization code
%SWAPPER-I-POOL, initializing paged pool
%SWAPPER-I-INIT, calling initialization routines
%SWAPPER-I-RSDM, joining system resource domain
%SWAPPER-I-P1, initializing SWAPPER P1 cells
%SWAPPER-I-PAGED, paged system initialization
%SWAPPER-I-HASH, creating the logical name hash tables
%SWAPPER-I-DEFINE, defining the system logical names
 
Another significant factor is that we are now up far enough that a number of things can be debugged
in parallel. A few weeks ago it was really a straight line of single stepping execution but now we
usually have at least five paths of debugging going on without serious dependencies on one another.

Clair