From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RESEND] hw/sh7750.c: use TARGET_FMT_plx to printf target_phys_addr_t
Date: Fri, 30 Nov 2007 10:11:19 -0600 [thread overview]
Message-ID: <20071130161119.GE28369@tapir> (raw)
In-Reply-To: <f43fc5580711300737y16a91e9bu3308a26122df4c8e@mail.gmail.com>
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
next prev parent reply other threads:[~2007-11-30 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-11 15:49 [Qemu-devel] [PATCH] hw/sh7750.c: use TARGET_FMT_plx to printf target_phys_addr_t Carlo Marcelo Arenas Belon
2007-11-18 21:18 ` [Qemu-devel] [PATCH] [RESEND] " Carlo Marcelo Arenas Belon
2007-11-30 5:36 ` Magnus Damm
2007-11-30 15:21 ` Carlo Marcelo Arenas Belon
2007-11-30 15:37 ` Blue Swirl
2007-11-30 16:11 ` Carlo Marcelo Arenas Belon [this message]
2007-11-30 16:50 ` Paul Brook
2007-11-30 17:16 ` Blue Swirl
2007-11-30 17:42 ` Paul Brook
2007-11-30 18:45 ` Blue Swirl
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=20071130161119.GE28369@tapir \
--to=carenas@sajinet.com.pe \
--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).