Date: Wed, 11 Dec 2013 08:51:49 -0800 From: Justin Hibbits <chmeeedalf@gmail.com> To: Nathan Whitehorn <nwhitehorn@freebsd.org> Cc: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org> Subject: Re: powerpc64 memory translations Message-ID: <20131211085149.05695606@zhabar.gateway.2wire.net> In-Reply-To: <C53E0CF3-6AC1-4309-8D72-F557F80E6C83@freebsd.org> References: <20131210223546.27d2b45d@zhabar.gateway.2wire.net> <C53E0CF3-6AC1-4309-8D72-F557F80E6C83@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm. It looks like something must have been messed up with firewire, because redoing it it now looks right. - Justin On Wed, 11 Dec 2013 07:31:54 -0600 Nathan Whitehorn <nwhitehorn@freebsd.org> wrote: > Where does it write instead? powerpc64 uses a 1:1 direct map of all > physical memory. powerpc32 sometimes, but not always, does this. > -Nathan > > On Dec 11, 2013, at 12:35 AM, Justin Hibbits wrote: > > > I'm trying to fix a problem with DTrace FBT (it just flat hangs), > > and want to use the oldest trick in the book -- writing to a known > > address at various points. Problem I have, though, is that writing > > to 0x10 virtual, unlike with powerpc32, doesn't write to 0x10 > > physical. Is there any way to get the mapping for the first page > > of physical memory, > > so I can do this debugging? And to make it always available, so > > that I don't have to worry about mapping it when I need to? > > > > Thanks, > > Justin > > _______________________________________________ > > freebsd-ppc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-ppc > > To unsubscribe, send any mail to > > "freebsd-ppc-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131211085149.05695606>