From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [PATCH, RFC] Smarter compilation for target devices
Date: Tue, 28 Apr 2009 18:25:40 +0100 [thread overview]
Message-ID: <200904281825.41235.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580904280918v7bbfc480v9124a9896880a63d@mail.gmail.com>
> > former. Duplicating this logic is both cpu.h and configure is also
> > asking for trouble. At minimum the build should fail if they disagree.
>
> Which logic?
The logic that determines TARGET_PHYS_ADDR_BITS.
By my reading TARGET_PHYS_ADDR_BITS is alway 64 on 64-bit hosts, so there's no
reason to build separate libraries there.
On a related note, the current big/little endian handling is fairly
findamentally broken. It kinda works for the current set of targets. However
for other targets (e.g. big-endian arm, in particular ixp4xx) it doesn't work
because the endianess of the device depends which bus it's connected to. We
really need to push the byte swapping down to the softmmu/iotlb code.
Paul
prev parent reply other threads:[~2009-04-28 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 19:34 [Qemu-devel] [PATCH, RFC] Smarter compilation for target devices Blue Swirl
2009-04-28 13:32 ` Paul Brook
2009-04-28 16:18 ` Blue Swirl
2009-04-28 17:25 ` Paul Brook [this message]
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=200904281825.41235.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=blauwirbel@gmail.com \
--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).