From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:48009)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1W0VA6-0001ak-Fs
	for qemu-devel@nongnu.org; Tue, 07 Jan 2014 06:49:41 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1W0V9x-00059i-E4
	for qemu-devel@nongnu.org; Tue, 07 Jan 2014 06:49:34 -0500
Received: from cantor2.suse.de ([195.135.220.15]:40577 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <afaerber@suse.de>) id 1W0V9x-00059c-6z
	for qemu-devel@nongnu.org; Tue, 07 Jan 2014 06:49:25 -0500
Message-ID: <52CBE9C0.7090909@suse.de>
Date: Tue, 07 Jan 2014 12:49:20 +0100
From: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
MIME-Version: 1.0
References: <1388906864-1083-1-git-send-email-qiaonuohan@cn.fujitsu.com>
	<1388906864-1083-7-git-send-email-qiaonuohan@cn.fujitsu.com>
	<52CBE72E.9070805@redhat.com>
In-Reply-To: <52CBE72E.9070805@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH v6 06/11] dump: add API to write dump header
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Laszlo Ersek <lersek@redhat.com>, Qiao Nuohan <qiaonuohan@cn.fujitsu.com>, Luiz Capitulino <lcapitulino@redhat.com>
Cc: stefanha@gmail.com, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>, kumagai-atsushi@mxc.nes.nec.co.jp, anderson@redhat.com, akong@redhat.com

Am 07.01.2014 12:38, schrieb Laszlo Ersek:
> Also... is it OK to write these fields to the file in host native byte
> order? What happens if an i686 / x86_64 target is emulated on a BE host=
?

For the target-s390x implementation Alex required to take care of
endianness for the s390x-on-x86 case, so it would probably make sense to
handle it for kdump format as well. Thanks for bringing it up!

BTW my original concerns related to CPU seem to have been addressed, so
I'm hoping this can go via the QMP queue once ready.

Regards,
Andreas

--=20
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imend=F6rffer; HRB 16746 AG N=FCrnbe=
rg