Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5032015yba; Mon, 13 May 2019 04:18:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqwlPlqAZstSU54mqy4qqUyjv6Xn5T03csjcUEFlw4UnvHPkKdd/APUZltsXFTkU7TjiNc0N X-Received: by 2002:a17:902:12f:: with SMTP id 44mr30007705plb.193.1557746322917; Mon, 13 May 2019 04:18:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557746322; cv=none; d=google.com; s=arc-20160816; b=reUgljikiCxnvJX5U7DZDL5skFoRpAcgQT+hQiZYZgx5FnrAcOpaCCOzikDw6JMlk1 v2tZv9HZ3uz0JN9u+sTqxdjtIodVuaOyYJU0Z/3QvvPsWXnJO9PZ14KnccgwXVnJ7Eb1 uQ1oiyzUwvPtxfsVwe9Gf6lBdUqllMgdDXdsjmc1ktQZM9wnpLJPwtk1a3G3SVLEasFZ PkAN450yTAVDOyE6ad5Okj8OEXkpHdJ7SOmQOuAkB5Jl5Fb0eWdiU2SFebHqA1yYeL9G UHV/cmsEwy7r7INm4OJ1vygDBQGwmOVLgVjs0aDDnsxQW1eDvImEjgbtMoRA6LIINCm5 LWWg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=tUgY0XyLDOcqBoja8zCBzEuWXSXWQtyNGdsIS8ETdN4=; b=O+6JXbhAYIfRzUijMML8j/32QQiWhIrkJivvpS6hW9l85cJm0B2qmrZPOQ89s7SxP9 MqexnLPnpRg9ze1mLrtIYj/vfylI7fkLBGIQ/mnv7jqk8yq7VnEf1cKhsVJ81dDeL9xF dXzgilgHkKklp84u4U3v6PAyYB+RxsJd1G4pZCKYQ2GXBbo9kUfToH4EsYdEHCIIRAze xQjzHSW1UpcmeEHZuAzN2YuNGp79YfTaXat3+JSVO2FVJ9QVviA7E0mIXLHOxTT+bDuE YGS7JpiXmKqnoydbFBmc2q+0/2LdAegyQ+82Mjks1gQrBkpJ0UeLIFRRREEb8Hi9mCSt xI6Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 67si15875731pfg.177.2019.05.13.04.18.26; Mon, 13 May 2019 04:18:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727982AbfEMKVZ (ORCPT + 99 others); Mon, 13 May 2019 06:21:25 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:37138 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728848AbfEMKUj (ORCPT ); Mon, 13 May 2019 06:20:39 -0400 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id B2A51795AEB80AF6238C; Mon, 13 May 2019 18:20:35 +0800 (CST) Received: from [127.0.0.1] (10.142.68.147) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.439.0; Mon, 13 May 2019 18:20:24 +0800 Subject: Re: [RFC PATCH V2] kvm: arm64: export memory error recovery capability to user space To: Peter Maydell CC: Christoffer Dall , Marc Zyngier , James Morse , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Jonathan Corbet , Catalin Marinas , Will Deacon , kvm-devel , "open list:DOCUMENTATION" , lkml - Kernel Mailing List , arm-mail-list , , "Zheng Xiang" References: <1557728917-49079-1-git-send-email-gengdongjiu@huawei.com> From: gengdongjiu Message-ID: Date: Mon, 13 May 2019 18:20:14 +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: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/5/13 17:44, Peter Maydell wrote: > On Mon, 13 May 2019 at 07:32, Dongjiu Geng wrote: >> >> When user space do memory recovery, it will check whether KVM and >> guest support the error recovery, only when both of them support, >> user space will do the error recovery. This patch exports this >> capability of KVM to user space. >> >> Cc: Peter Maydell >> Signed-off-by: Dongjiu Geng >> --- >> v1->v2: >> 1. check whether host support memory failure instead of RAS capability >> https://patchwork.kernel.org/patch/10730827/ >> >> v1: >> 1. User space needs to check this capability of host is suggested by Peter[1], >> this patch as RFC tag because user space patches are still under review, >> so this kernel patch is firstly sent out for review. >> >> [1]: https://patchwork.codeaurora.org/patch/652261/ >> --- > > I thought the conclusion of the thread on the v1 patch was that > userspace doesn't need to specifically ask the host kernel if > it has support for this -- if it does not, then the host kernel > will just never deliver userspace any SIGBUS with MCEERR code, > which is fine. Or am I still confused? thanks Peter's quick reply. yes, I think so, if it does not support, then the host kernel will just never deliver userspace any SIGBUS with MCEERR code. so maybe we do not need this patch. > > thanks > -- PMM > . >