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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65B21C433EF for ; Sat, 7 May 2022 09:23:07 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 63E586B0085; Sat, 7 May 2022 05:23:06 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5C7446B0087; Sat, 7 May 2022 05:23:06 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 466D86B0088; Sat, 7 May 2022 05:23:06 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0012.hostedemail.com [216.40.44.12]) by kanga.kvack.org (Postfix) with ESMTP id 32DCD6B0085 for ; Sat, 7 May 2022 05:23:06 -0400 (EDT) Received: from smtpin31.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay11.hostedemail.com (Postfix) with ESMTP id EBBAC806D9 for ; Sat, 7 May 2022 09:23:05 +0000 (UTC) X-FDA: 79438407930.31.5ADAA10 Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by imf03.hostedemail.com (Postfix) with ESMTP id 57C1920002 for ; Sat, 7 May 2022 09:22:58 +0000 (UTC) Received: by mail-pf1-f182.google.com with SMTP id x23so8178203pff.9 for ; Sat, 07 May 2022 02:23:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=HsmL70Uxpre+Yuw44Bhf/DXDbaU8ZDKhOhdy778k+yo=; b=mlR3d80AhkwzzC9PKqaXsMDhWbQVXMEC6MCnzg1peU4Wr/mTRivGCNYgM7QRHTa0ub Z3V6OvjENlJU/wkZN2dPGw8DjSuZcoNR2oGUlIRRhQBVH/J/SmIEO4cp5zUEAua7DtmH km6VJHxTPXPOkXf28Bfd8y2Oj/hJ5Li/5hWOGMIjZcnUHnrxLi2Ce7b4K6swCToXCf7T kja+3ZAT4xc4qTctp1GdxZRAwko+jFMeVBxA7mgxWtFLT8zu8kr3WjghwHOyLiP52hWs ZvWYhgOn07sFKhQ0KVq2vNxuL3N6cigDdOzFwBCEHPNwFpfeLQXgfP/Z5DqDonJBga7k jzjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=HsmL70Uxpre+Yuw44Bhf/DXDbaU8ZDKhOhdy778k+yo=; b=hdQsNIkIM8yXVDLWSpppOTPwIFuD0INY0SEhHM1LeV4W7WG1CT6DKcLqFYvSzJL9iF NsKNWeJGsu1GZp3rYGRmklFy5GHQfJkI6Y4fCe80U+VZnRd/+Tk1kLn/GDLTN5cboNL8 qQVCuhenq9BLM6io2022TCLr1HZ/cjckc0IrjUoV9vBAQXUzkIqrxUgCb8ZQK0xX88nU XgzFYADrcX+DxJKGmna0B0OpHd1KdDgGH2o0UF6DDeCd+YzNzcMNaYUgWw0IOfQvNhV3 ir3IZQ2HYpghL0CqaVANo3okQ622fP3B16/on0XLr8YYonZn64oPZBYhqll9kk8cXzul Biqw== X-Gm-Message-State: AOAM532NJcaPuBuVtVyVEQYj1tN6pnrMh0HU3F4tAre1QSTHBOgVgA/z py+2mgVenMSguaGMcW2+XaYqdg== X-Google-Smtp-Source: ABdhPJyw3bAQ9HgqBVfd9NCUfNAz6xXstkZXK2fVR31183kcyPUZrKZY1G88F0L6iyNceYsna1Hw0Q== X-Received: by 2002:a63:c013:0:b0:3c1:df82:c8b3 with SMTP id h19-20020a63c013000000b003c1df82c8b3mr6045188pgg.141.1651915383734; Sat, 07 May 2022 02:23:03 -0700 (PDT) Received: from [10.255.89.252] ([139.177.225.239]) by smtp.gmail.com with ESMTPSA id y9-20020a17090322c900b0015e8d4eb2e7sm3216427plg.305.2022.05.07.02.22.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 07 May 2022 02:23:02 -0700 (PDT) Message-ID: <23e06fc6-84fe-122e-fc07-02c5bfa7d50b@bytedance.com> Date: Sat, 7 May 2022 17:19:09 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: Re: Re: [PATCH 3/4] mm/memofy-failure.c: optimize hwpoison_filter Content-Language: en-US To: Naoya Horiguchi Cc: David Hildenbrand , akpm@linux-foundation.org, naoya.horiguchi@nec.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wu Fengguang , "Michael S. Tsirkin" , Jason Wang , "virtualization@lists.linux-foundation.org" References: <20220429142206.294714-1-pizhenwei@bytedance.com> <20220429142206.294714-4-pizhenwei@bytedance.com> <20220506085920.GC1356094@u2004> <3c0e25fb-695d-4a29-6de4-c892f89cea7a@bytedance.com> <20220507082045.GA1716199@u2004> From: zhenwei pi In-Reply-To: <20220507082045.GA1716199@u2004> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 57C1920002 Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=mlR3d80A; spf=pass (imf03.hostedemail.com: domain of pizhenwei@bytedance.com designates 209.85.210.182 as permitted sender) smtp.mailfrom=pizhenwei@bytedance.com; dmarc=pass (policy=none) header.from=bytedance.com X-Rspam-User: X-Stat-Signature: 8ajd59463qjicnta9ymy8zwudkdsajek X-HE-Tag: 1651915378-281418 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 5/7/22 16:20, Naoya Horiguchi wrote: > On Sat, May 07, 2022 at 08:28:05AM +0800, zhenwei pi wrote: >> >> On 5/7/22 00:28, David Hildenbrand wrote: >>> On 06.05.22 15:38, zhenwei pi wrote: >>>> >>>> >>>> On 5/6/22 16:59, Naoya Horiguchi wrote: >>>>> On Fri, Apr 29, 2022 at 10:22:05PM +0800, zhenwei pi wrote: >>>>>> In the memory failure procedure, hwpoison_filter has higher priority, >>>>>> if memory_filter() filters the error event, there is no need to do >>>>>> the further work. >>>>> >>>>> Could you clarify what problem you are trying to solve (what does >>>>> "optimize" mean in this context or what is the benefit)? >>>>> >>>> >>>> OK. The background of this work: >>>> As well known, the memory failure mechanism handles memory corrupted >>>> event, and try to send SIGBUS to the user process which uses this >>>> corrupted page. >>>> >>>> For the virtualization case, QEMU catches SIGBUS and tries to inject MCE >>>> into the guest, and the guest handles memory failure again. Thus the >>>> guest gets the minimal effect from hardware memory corruption. >>>> >>>> The further step I'm working on: >>>> 1, try to modify code to decrease poisoned pages in a single place >>>> (mm/memofy-failure.c: simplify num_poisoned_pages_dec in this series). > > This is fine to me. > >>>> >>>> 2, try to use page_handle_poison() to handle SetPageHWPoison() and >>>> num_poisoned_pages_inc() together. It would be best to call >>>> num_poisoned_pages_inc() in a single place too. I'm not sure if this is >>>> possible or not, please correct me if I misunderstand. > > SetPageHWPoison() can be cancelled in memory_failure(), so simply bundling > it with num_poisoned_pages_inc() might not be optimal. I think that > action_result() is supposed to be called when memory error handling is > effective (not filtered, not cancelled). So moving num_poisoned_pages_inc() > (and notification code in your plan) into this function might be good. > OK, I'll remove this patch(mm/memofy-failure.c: optimize hwpoison_filter) from this series, and fix the other 3 patches in the v2 version. Then try to implement/test as your suggestion in another series. >>>> >>>> 3, introduce memory failure notifier list in memory-failure.c: notify >>>> the corrupted PFN to someone who registers this list. >>>> If I can complete [1] and [2] part, [3] will be quite easy(just call >>>> notifier list after increasing poisoned page). >>>> >>>> 4, introduce memory recover VQ for memory balloon device, and registers >>>> memory failure notifier list. During the guest kernel handles memory >>>> failure, balloon device gets notified by memory failure notifier list, >>>> and tells the host to recover the corrupted PFN(GPA) by the new VQ. >>> >>> Most probably you might want to do that asynchronously, and once the >>> callback succeeds, un-poison the page. >>> >> Yes! >> >>>> >>>> 5, host side remaps the corrupted page(HVA), and tells the guest side to >>>> unpoison the PFN(GPA). Then the guest fixes the corrupted page(GPA) >>>> dynamically. >>> >>> I think QEMU already does that during reboots. Now it would be triggered >>> by the guest for individual pages. >>> >> Yes, currently QEMU supports to un-poison corrupted pages during >> reset/reboot. We can reuse some code to do the work in this case, this >> allows a VM to fix corrupted pages as soon as possible(also no need to >> reset/reboot). > > So this finally allows to replace broken page mapped to guest with > a healthy page without rebooting the guest. That sounds helpful. > > Thanks, > Naoya Horiguchi > Yes, it's my plan. Thanks for your suggestions! >> >>>> >>>> Because [4] and [5] are related to balloon device, also CC Michael, >>>> David and Jason. >>> >>> Doesn't sound too crazy for me, although it's a shame that we always >>> have to use virtio-balloon for such fairly balloon-unrelated things. >>> >> Thanks! >> >> -- >> zhenwei pi -- zhenwei pi