From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 69F7BC43603 for ; Mon, 9 Dec 2019 14:12:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 390B020726 for ; Mon, 9 Dec 2019 14:12:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727903AbfLIOMq (ORCPT ); Mon, 9 Dec 2019 09:12:46 -0500 Received: from szxga07-in.huawei.com ([45.249.212.35]:38252 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727572AbfLIOMq (ORCPT ); Mon, 9 Dec 2019 09:12:46 -0500 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id D162478339045A5766C6; Mon, 9 Dec 2019 22:12:42 +0800 (CST) Received: from [127.0.0.1] (10.142.68.147) by DGGEMS407-HUB.china.huawei.com (10.3.19.207) with Microsoft SMTP Server id 14.3.439.0; Mon, 9 Dec 2019 22:12:37 +0800 Subject: Re: [RESEND PATCH v21 5/6] target-arm: kvm64: handle SIGBUS signal from kernel or KVM To: Beata Michalska CC: Xiang Zheng , , , Igor Mammedov , , Peter Maydell , "Laszlo Ersek" , , , , , , , , , , , References: <20191111014048.21296-1-zhengxiang9@huawei.com> <20191111014048.21296-6-zhengxiang9@huawei.com> <238ea7b3-9d6d-e3f7-40c9-e3e62b5fb477@huawei.com> From: gengdongjiu Message-ID: <650e26cf-e007-1e31-cd0a-4042bb9fa6a8@huawei.com> Date: Mon, 9 Dec 2019 22:12:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.142.68.147] X-CFilter-Loop: Reflected Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org Archived-At: List-Archive: List-Post: On 2019/12/9 21:05, Beata Michalska wrote: >> Here we set the FnV to not valid, not to set it to valid. >> because Guest will use the physical address that recorded in APEI table. >> > To be precise : the FnV is giving the status of FAR - so what you are setting > here is status of 0b0 which means FAR is valid, not FnV on it's own. > And my point was that you are changing the prototype for syn_data_abort_no_iss > just for this case only so I was just thinking that it might not be > worth that, instead > you could just set it here ... or to be more flexible , provide a way > to set specific bits > on demand. No, I set the FnV to 0b1, not 0b0, the whole esr_el1's value is 0x96000410, as shown below log: I remember changing the prototype for syn_data_abort_no_iss is suggested by Peter Maydell. [1]: [ 62.851830] Internal error: synchronous external abort: 96000410 [#1] PREEMPT SMP [ 62.854465] Modules linked in: >