From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Iy8MT-0003F5-IC
	for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:05:05 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Iy8MR-0003EJ-ON
	for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:05:04 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Iy8MR-0003EF-JE
	for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:05:03 -0500
Received: from tapir.sajinet.com.pe ([66.139.79.212])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <carenas@sajinet.com.pe>) id 1Iy8MQ-0007o3-9e
	for qemu-devel@nongnu.org; Fri, 30 Nov 2007 11:05:02 -0500
Date: Fri, 30 Nov 2007 10:11:19 -0600
From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
Subject: Re: [Qemu-devel] [PATCH] [RESEND] hw/sh7750.c: use TARGET_FMT_plx to
	printf target_phys_addr_t
Message-ID: <20071130161119.GE28369@tapir>
References: <20071111154922.GE25322@tapir> <20071118211837.GA15962@tapir>
	<aec7e5c30711292136h2132ae81k8799694270b6659e@mail.gmail.com>
	<20071130152126.GC28369@tapir>
	<f43fc5580711300737y16a91e9bu3308a26122df4c8e@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <f43fc5580711300737y16a91e9bu3308a26122df4c8e@mail.gmail.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On Fri, Nov 30, 2007 at 05:37:35PM +0200, Blue Swirl wrote:
> On 11/30/07, Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe> wrote:
> > which might not be what was intended originally and might be uncovering a
> > bug somewhere else and based on the fact that apparently (and this gets 
> > confusing as it seems to be inconsistently used everywhere in qemu) :
> >
> >   target_phys_addr_t = physical address of the host
> >   ram_addr_t = physical address of the guest
> 
> No, target_phys_addr_t is the physical address of the emulated target
> system. For host addresses ram_addr_t, unsigned long or even int is
> used. Host addresses are of course virtual, Qemu is a user space
> application until someone makes it run in bare metal without OS.

thanks, that makes much more sense that the convoluted idea I got from the
code, and now that I recovered my sanity can see finally where the bug is.

Carlo