From: "Wladimir J. van der Laan" <laanwj@gmail.com>
To: etnaviv@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: etnaviv: mmu issue after end of address space reached?
Date: Sat, 10 Dec 2016 12:47:01 +0100 [thread overview]
Message-ID: <20161210114701.GE4766@amethyst.visucore.com> (raw)
In-Reply-To: <20161210110046.GD4766@amethyst.visucore.com>
> <3>[ 549.814025] etnaviv-gpu 130000.gpu: MMU fault status 0x00000002 <- happens almost immediately
> <3>[ 549.819960] etnaviv-gpu 130000.gpu: MMU 0 fault addr 0xe8783040
> <3>[ 549.825889] etnaviv-gpu 130000.gpu: MMU 1 fault addr 0x00000000
> <3>[ 549.831817] etnaviv-gpu 130000.gpu: MMU 2 fault addr 0x00000000
> <3>[ 549.837744] etnaviv-gpu 130000.gpu: MMU 3 fault addr 0x00000000
Okay I just tried to get the same while rendering in Mesa and it doesn't happen.
It reaches the end of the address space, sets last_iova back to 0, and just continues.
So the MMU fault is somehow specific to what I'm doing. Interesting.
> What I find curious, though, is that after the search presumably starts over at
> 0 it returns 0xe8783000 instead of an earlier address. For this reason
> last_iova is stuck near the end of the address space and the problem keeps
> repeating once it's been hit.
This does happen when rendering - it keeps dealing out iovas near the end of the
address space. But that seems harmless, though maybe causes some more MMU
flushes than necessary.
Wladimir
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-12-10 11:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 11:00 etnaviv: mmu issue after end of address space reached? Wladimir J. van der Laan
2016-12-10 11:47 ` Wladimir J. van der Laan [this message]
2016-12-10 17:05 ` Wladimir J. van der Laan
2016-12-12 9:25 ` Lucas Stach
2016-12-12 9:57 ` Wladimir J. van der Laan
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=20161210114701.GE4766@amethyst.visucore.com \
--to=laanwj@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.