qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Blue Swirl <blauwirbel@gmail.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: The OpenBIOS Mailinglist <openbios@openbios.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] sparc memory/io mapping (and a milliseconds counter)
Date: Sun, 30 Aug 2009 21:20:04 +0300	[thread overview]
Message-ID: <f43fc5580908301120jd9d0d50g6a901f7716d2d9cd@mail.gmail.com> (raw)
In-Reply-To: <fb8d4f70908291621r140af490r662cf3c377f24499@mail.gmail.com>

[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    ( 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	other threads:[~2009-08-30 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-29 23:21 [Qemu-devel] sparc memory/io mapping (and a milliseconds counter) Artyom Tarasenko
2009-08-30 18:20 ` Blue Swirl [this message]

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=f43fc5580908301120jd9d0d50g6a901f7716d2d9cd@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --cc=atar4qemu@googlemail.com \
    --cc=openbios@openbios.org \
    --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).