From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH 16/27] tools/libxl: Infrastructure for reading a libxl migration v2 stream Date: Wed, 17 Jun 2015 18:49:13 +0800 Message-ID: <558150A9.70003@cn.fujitsu.com> References: <1434375880-30914-1-git-send-email-andrew.cooper3@citrix.com> <1434375880-30914-17-git-send-email-andrew.cooper3@citrix.com> <5580E4F7.4090705@cn.fujitsu.com> <1434536151.13744.299.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1434536151.13744.299.camel@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: Wei Liu , Andrew Cooper , Ian Jackson , Xen-devel , Ross Lagerwall , Yang Hongyang List-Id: xen-devel@lists.xenproject.org On 06/17/2015 06:15 PM, Ian Campbell wrote: > On Wed, 2015-06-17 at 11:09 +0800, Wen Congyang wrote: >>> + if (hdr->options & RESTORE_OPT_BIG_ENDIAN) { >>> + ret = ERROR_FAIL; >>> + LOG(ERROR, "Unable to handle big endian streams"); >>> + goto err; >> >> I think it is better to check if the host is big endian or not. > > It's not, there are no big endian ports of Xen today. I think encoding > that here is fine. IIRC, arm supports big endian. Do we only use arm+little endian? If so, it is OK now. Thanks Wen Congyang > > > . >