From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53212) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dn4SY-0003fM-B6 for qemu-devel@nongnu.org; Wed, 30 Aug 2017 10:59:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dn4SU-0003lY-6a for qemu-devel@nongnu.org; Wed, 30 Aug 2017 10:59:14 -0400 References: <1504100343-26607-1-git-send-email-thuth@redhat.com> From: Thomas Huth Message-ID: <52928093-36d5-89cf-bb89-ab5abf54b8f0@redhat.com> Date: Wed, 30 Aug 2017 16:59:03 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH for-2.11] hw/misc/ivshmem: Fix ivshmem_recv_msg() to also work on big endian systems List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , qemu-devel@nongnu.org Cc: qemu-trivial@nongnu.org, David Gibson , Laurent Vivier , =?UTF-8?Q?Marc-Andr=c3=a9_Lureau?= On 30.08.2017 16:53, Philippe Mathieu-Daud=C3=A9 wrote: > On 08/30/2017 10:39 AM, Thomas Huth wrote: >> The "slow" ivshmem-tests currently fail when they are running on a >> big endian host: >> >> $ uname -m >> ppc64 >> $ V=3D1 QTEST_QEMU_BINARY=3Dx86_64-softmmu/qemu-system-x86_64 >> tests/ivshmem-test -m slow >> /x86_64/ivshmem/single: OK >> /x86_64/ivshmem/hotplug: OK >> /x86_64/ivshmem/memdev: OK >> /x86_64/ivshmem/pair: OK >> /x86_64/ivshmem/server-msi: qemu-system-x86_64: >> =C2=A0 -device ivshmem-doorbell,chardev=3Dchr0,vectors=3D2: server sen= t invalid >> ID message >> Broken pipe >> >> The problem is that the server side code in ivshmem_server_send_one_ms= g() >> correctly translates all messages IDs into little endian 64-bit values= , >> but the client side code in the ivshmem_recv_msg() function does not s= wap >> the byte order back. Fix it by passing the value through le64_to_cpu()= . >=20 > Yes, we lack BE testing :( As far as I know, some people are already running the tests on s390x and ppc64 ... the problem is that apparently nobody is running with SPEED=3Dslow there - that's why this problem slipped through so far. Maybe we should switch to the SPEED=3Dslow by default in the Makefile? Thomas