Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 06 Sep 2018 12:46:03 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 231064] vgapci device memory not excluded on ThunderX
Message-ID:  <bug-231064-227-VqNMtadjae@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-231064-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-231064-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231064

--- Comment #3 from Andrew Turner <Andrew@FreeBSD.org> ---
You can try excluding that physical memory from the map by calling
arm_physmem_exclude_region from initarm. It takes the start address, length,
and the EXFLAG_NOALLOC flag, e.g. arm_physmem_exclude_region(0x10000000,
0x01020000, EXFLAG_NOALLOC).

If you put it just after pmap_bootstrap we can still access the memory via =
the
DMAP to see what data is being put into the range.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231064-227-VqNMtadjae>