From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Mhp0t-0003MV-Ln
	for qemu-devel@nongnu.org; Sun, 30 Aug 2009 14:20:27 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Mhp0t-0003Lm-5O
	for qemu-devel@nongnu.org; Sun, 30 Aug 2009 14:20:27 -0400
Received: from [199.232.76.173] (port=35740 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Mhp0s-0003Lg-Tl
	for qemu-devel@nongnu.org; Sun, 30 Aug 2009 14:20:26 -0400
Received: from ey-out-1920.google.com ([74.125.78.144]:31553)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <blauwirbel@gmail.com>) id 1Mhp0s-0000xw-Ij
	for qemu-devel@nongnu.org; Sun, 30 Aug 2009 14:20:26 -0400
Received: by ey-out-1920.google.com with SMTP id 13so746926eye.14
	for <qemu-devel@nongnu.org>; Sun, 30 Aug 2009 11:20:24 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com>
References: <fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com>
From: Blue Swirl <blauwirbel@gmail.com>
Date: Sun, 30 Aug 2009 21:20:04 +0300
Message-ID: <f43fc5580908301120jd9d0d50g6a901f7716d2d9cd@mail.gmail.com>
Subject: Re: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>, qemu-devel <qemu-devel@nongnu.org>

[added openbios@openbios.org to CC]

On Sun, Aug 30, 2009 at 2:21 AM, Artyom
Tarasenko<atar4qemu@googlemail.com> 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 =C2=A0 =C2=A0( Parameter field: 7680000 )
>
> ok 7680000 map?
> Virtual =C2=A0: 0768.0000
> Context =C2=A0: @ 0.1ffc.0000 =C2=A001ff.afc1 # 0
> Region =C2=A0 : @ 0.1ffa.fc1c =C2=A00000.0000 Invalid
>
> ok 7680000 iomap?
> Virtual =C2=A0: 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 )
  ;