From: "Andreas Färber" <afaerber@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
"Anthony Liguori" <aliguori@us.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Alexander Graf" <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/2] memory: Fix 'Kill old-style I/O dispatch'
Date: Sun, 08 Jan 2012 18:13:51 +0100 [thread overview]
Message-ID: <4F09CECF.4020309@suse.de> (raw)
In-Reply-To: <4F0979FA.5050001@redhat.com>
Am 08.01.2012 12:11, schrieb Avi Kivity:
> On 01/07/2012 10:45 AM, Andreas Färber wrote:
>> This series fixes endianness issues in the memory core.
>> Apparently the actual byte swapping had not yet been tested.
>
> /me hangs head. But strangely, sparc-test, mips-test, and
> ppc-virtex-ml507 (after the idstr fix) all boot for me.
IIUC the byte swaps only have to happen when some MemoryRegion has an
endianness other than the target.
So when CHRP uses BE and native I/O exclusively it may work, whereas
someone once summarized PReP as "a PC with a PowerPC CPU". ;)
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-01-08 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-07 8:45 [Qemu-devel] [PATCH 0/2] memory: Fix 'Kill old-style I/O dispatch' Andreas Färber
2012-01-07 8:45 ` [Qemu-devel] [PATCH 1/2] memory: Fix memory_region_wrong_endianness() Andreas Färber
2012-01-07 8:45 ` [Qemu-devel] [PATCH 2/2] memory: Fix adjust_endianness() Andreas Färber
2012-01-07 19:46 ` [Qemu-devel] [PATCH 0/2] memory: Fix 'Kill old-style I/O dispatch' Aurelien Jarno
2012-01-08 11:11 ` Avi Kivity
2012-01-08 17:13 ` 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=4F09CECF.4020309@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).