qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] fw_cfg: fix endianness in fw_cfg_data_mem_read(


From: Laszlo Ersek
Subject: Re: [Qemu-devel] [PATCH] fw_cfg: fix endianness in fw_cfg_data_mem_read() / _write()
Date: Wed, 31 Dec 2014 18:58:53 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0

On 12/31/14 18:44, Peter Maydell wrote:
> On 31 December 2014 at 17:17, Peter Maydell <address@hidden> wrote:
>> Unpatched QEMU + QEMU_EFI.fd.v4 : doesn't boot (doesn't load kernel)
>> Patched QEMU + QEMU_EFI.fd.v4_noswizzle : boots OK (dracut-initqueue
>> starts downloading things).
> 
> Just noticed you asked for the full matrix of tests:
> patched QEMU + fd.v4 : doesn't boot (doesn't load kernel)
> unpatched + noswizzle : boots OK
> 
> That's a bit confusing...

It's not confusing. When you run unpatched qemu *on a big endian host*,
that's identical to what the patched code does *on a big endian host*.

The full matrix actually has 8 elements (3 dimensions with 2 values per
dimension) -- host endianness, patched qemu vs. unpatched qemu, and
swizzling vs. non-swizzling firmware.

Thanks,
Laszlo




reply via email to

[Prev in Thread] Current Thread [Next in Thread]