qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)


From: Blue Swirl
Subject: Re: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)
Date: Sun, 30 Aug 2009 21:20:04 +0300

[added address@hidden to CC]

On Sun, Aug 30, 2009 at 2:21 AM, Artyom
Tarasenko<address@hidden> wrote:
> is there a generic way to find out mapped device for a virtual
> address? Or at least its physical address?
>
> ok see get-msecs
> value get-msecs    ( Parameter field: 7680000 )
>
> ok 7680000 map?
> Virtual  : 0768.0000
> Context  : @ 0.1ffc.0000  01ff.afc1 # 0
> Region   : @ 0.1ffa.fc1c  0000.0000 Invalid
>
> ok 7680000 iomap?
> Virtual  : 0768.0000 is not a valid I/O address.

You could try to uncomment DEBUG_MMU in helper.c and op_helper.c,
maybe the MMU dump contains the address.

> Looks like the address 0x7680000 is not mapped to anything, but the
> call returns a value:
>
> ok get-msecs .
> 0
> ok get-msecs .
> 0
>
> The value is obviously wrong, but the question is, where does it come
> from? Is it a RAM or is it one of devices? Didn't see anything similar
> in prtconf dumps.
>
> Another related question is, are there any known issues related to
> milliseconds counter?
> In the current OpenBIOS "get-msecs" call doesn't return anything at all.

It's definition in forth/device/other.fs is simply:
: get-msecs    ( -- n )
  ;




reply via email to

[Prev in Thread] Current Thread [Next in Thread]