From mboxrd@z Thu Jan  1 00:00:00 1970
From: Julien Grall <julien.grall@citrix.com>
Subject: xen/arm: Crash when allocating memory for ACPI table
 (Was Re: Design doc of adding ACPI support for arm64 on Xen - version 2)
Date: Fri, 14 Aug 2015 15:17:32 +0100
Message-ID: <55CDF87C.40103@citrix.com>
References: <55C413D5.7000709@huawei.com> <55CAF41C.1090208@huawei.com>
	<55CB0DC0.4020304@citrix.com> <55CDF5A3.8050201@linaro.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <55CDF5A3.8050201@linaro.org>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Shannon Zhao <shannon.zhao@linaro.org>, Shannon Zhao <zhaoshenglong@huawei.com>, xen-devel <xen-devel@lists.xen.org>, Jan Beulich <jbeulich@suse.com>, Stefano Stabellini <stefano.stabellini@citrix.com>, Ian Campbell <ian.campbell@citrix.com>, Parth Dixit <parth.dixit@linaro.org>, Christoffer Dall <christoffer.dall@linaro.org>
Cc: Hangaohuai <hangaohuai@huawei.com>, "Huangpeng (Peter)" <peter.huangpeng@huawei.com>
List-Id: xen-devel@lists.xenproject.org

(Renaming the subject)

Hi Shannon,

On 14/08/15 15:05, Shannon Zhao wrote:
> 
> 
> On 2015/8/12 17:11, Julien Grall wrote:
>> On 12/08/2015 08:22, Shannon Zhao wrote:
>>> Hi,
>>
>> Hi Shannon,
>>
>> It's not part of the design discussion and we are avoiding to mix
>> discussion. Can you please create another thread (or at least renaming
>> the subject)?
>>
>>> I'm working on re-spinning this patchset while encountering a werid
>>> problem about xzalloc_bytes.
>>>
>>> Since I need to copy some ACPI tables, I need to allocate some memory
>>> for it. So there are a few places calling xzalloc_bytes. And it fails at
>>> the fifth one. The log is shown as following:
>>
>> Do you copy data in the newly allocated memory between 2 xzalloc_bytes?
>>
> 
> No, I just use xzalloc_bytes to allocate some place and copy ACPI to the
> allocated place, modify the content, then call
> raw_copy_to_guest_flush_dcache to copy the modified tables to guest memory.

Can you provide the code and show which call is crashing?

Regards,

-- 
Julien Grall