From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)
Date: Sun, 30 Aug 2009 01:21:48 +0200 [thread overview]
Message-ID: <fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com> (raw)
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.
next reply other threads:[~2009-08-29 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-29 23:21 Artyom Tarasenko [this message]
2009-08-30 18:20 ` [Qemu-devel] sparc memory/io mapping (and a milliseconds counter) Blue Swirl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).