"Matt D. Robinson" wrote:
>
> Tom, isn't that an SGI specific variable for SGI's BIGMEM patch?
Yes it is. What it's there for is that some low level code gets stuffed
in locore memory and we have to determine the start of locore in order
to make the virtual to physical memory translation (so that we can
disassemble the code). This had to be done to fix some stack trace problems
with certain kernels.
Brian, from your point of view, you need to make sure that you can translate
(in the kl_virtop() function) any kernel address (and possibly user address)
into a physical address. As for the reference to __locore_lmabegin, you can
remove it, replace it with something that makes sense from an Alpha
perspective,
or just ignore it (failure is OK), since we don't currently check the return
value from kl_init_kern_info() (perhaps we should?).
Tom
>
> --Matt
>
> On Mon, 1 May 2000, Brian Hall wrote:
> |>__locore_lmabegin
> |>
> |>What does this kernel symbol refer to for i386? I need to figure out what
> the
> |>closest Alpha equivalent is.
> |>
> |>The LKCD lcrash code in question (lookup for the address of this symbol):
> |>
> |>
> |>if (!(sp = kl_lkup_symname("__locore_lmabegin"))) {
> |> return(3);
> |>}
> |>KL_LOCORE_ADDR = sp->s_addr & KL_PAGE_MASK;
|