From: "Andreas Färber" <afaerber@suse.de>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sanity
Date: Tue, 07 Feb 2012 23:18:46 +0100 [thread overview]
Message-ID: <4F31A346.9050300@suse.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1202072213140.10788@linmac>
Am 07.02.2012 19:22, schrieb malc:
> This is a 32bit machine, the target is i386-softmmu, yet,
> libhw32 is mostly empty and libhw64 is populated,
[snip]
I believe some people felt a need to emulate PAE or something which
needed a physical address space of 36 bits, therefore i386 was switched
from 32 bits to 64 bits.
Similar for ppc recently.
Lately there was also some discussion about dropping libhw32 and
target_phys_addr_t altogether and making all devices 64-bit.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-02-07 22:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 18:22 [Qemu-devel] Sanity malc
2012-02-07 22:11 ` Stefan Weil
2012-02-07 22:18 ` Andreas Färber [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=4F31A346.9050300@suse.de \
--to=afaerber@suse.de \
--cc=av1474@comtv.ru \
--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).