From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MhXFO-0001Xj-5r
	for qemu-devel@nongnu.org; Sat, 29 Aug 2009 19:22:14 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MhXFJ-0001TU-KK
	for qemu-devel@nongnu.org; Sat, 29 Aug 2009 19:22:13 -0400
Received: from [199.232.76.173] (port=47583 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MhXFJ-0001TR-F0
	for qemu-devel@nongnu.org; Sat, 29 Aug 2009 19:22:09 -0400
Received: from mail-gx0-f211.google.com ([209.85.217.211]:41368)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <atar4qemu@googlemail.com>) id 1MhXFJ-0007Sb-7T
	for qemu-devel@nongnu.org; Sat, 29 Aug 2009 19:22:09 -0400
Received: by gxk7 with SMTP id 7so4262213gxk.8
	for <qemu-devel@nongnu.org>; Sat, 29 Aug 2009 16:22:08 -0700 (PDT)
MIME-Version: 1.0
From: Artyom Tarasenko <atar4qemu@googlemail.com>
Date: Sun, 30 Aug 2009 01:21:48 +0200
Message-ID: <fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)
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: qemu-devel <qemu-devel@nongnu.org>

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.

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.