>Before I go tracing the IPL myself, does anyone know off the top of
>their head whether the kernel starting address has changed in 2.6?  Or
>maybe its initial internal memory map?
The linking of a 2.6. kernel works quite different from 2.4. We did not
try the old-style NSS because
we do not support it. Please be patient for a while, we're planning to
work on a nicer way to get the
kernel into NSS...

with kind regards
Carsten Otte
--
I saw screens of green, red messages too, then came blue, shubidu
And i think to myself, what a wonderful world




Adam Thornton <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
28/04/2004 11:39 PM
Please respond to Linux on 390 Port


        To:     [EMAIL PROTECTED]
        cc:
        Subject:        2.6 kernels and NSSes



I was wondering whether anyone else had built a 2.6 kernel into an NSS
yet.

I used my old reliable SAVELX exec; the guts of it are this:

/* Figure out DEFSYS command... */
/* Requires Class E privileges */
/* First and fourth megabytes: RW, exclusive */
/* Second and third megabytes: RO, shared */
/* Rest of storage up machine size, RO, shared */
dodef = 'CP DEFSYS' lxname '0-FF EW 100-2FF SR 300-5FF EW'
dodef = dodef 'MINSIZE=' || storsize
dodef = dodef 'PARMREGS=0-15'
say dodef
dodef
/* Set breakpoint at 010000: when we get there, savesys and quit */
/* (control is handed to the Linux kernel at 010000) */
setsave = 'CP TRACE I R 010000 CMD SAVESYS' lxname
setsave = setsave || myend 'TRACE END ALL'
say setsave
setsave

When I try to IPL the resulting NSS, I get:
HCPGIR453W CP entered; program interrupt loop

That makes me suspect that maybe 010000 is no longer the starting
address of the kernel.

When I IPL from DASD as usual, I see
Memory: 39808k/262144k available (3118k kernel code, 0k reserved, 1237k
data, 80k init)

So the 4M of space I'm saving for the kernel ought to be plenty.

Before I go tracing the IPL myself, does anyone know off the top of
their head whether the kernel starting address has changed in 2.6?  Or
maybe its initial internal memory map?

Adam

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to