Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: m/B67G93Bk3fupKUvEg1iWlU8j/y3QUnlxwl62q+NfTJqptC5iGDBhw2+/4vX55voeGet2ya9t
 hXI4O81s94Bg==
IronPort-SDR: 3CDholy5BJ7Vmf/JABB6RxzlkV8ggywUriuMcaB/y7SyzqRMVjkN1ynKFnTrCSsiruMRTHwOG8
 YCuSZX0e10mQ==
From:   "Luck, Tony" <tony.luck@intel.com>
To:     Aili Yao <yaoaili@kingsoft.com>,
        =?iso-2022-jp?B?SE9SSUdVQ0hJIE5BT1lBKBskQktZOH0hIUQ+TGkbKEIp?= 
        <naoya.horiguchi@nec.com>
CC:     Naoya Horiguchi <nao.horiguchi@gmail.com>,
        "linux-mm@kvack.org" <linux-mm@kvack.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        "Oscar Salvador" <osalvador@suse.de>,
        David Hildenbrand <david@redhat.com>,
        Borislav Petkov <bp@alien8.de>,
        Andy Lutomirski <luto@kernel.org>, Jue Wang <juew@google.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "yaoaili126@gmail.com" <yaoaili126@gmail.com>
Subject: RE: [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action
 Required MCE
Thread-Topic: [PATCH v3 0/3] mm,hwpoison: fix sending SIGBUS for Action
 Required MCE
Thread-Index: AQHXNklUtDziI1+1ZUqZsXGvSliLyarXX3UAgAAW4VCAAJTpAIAAYa8A///72gCAAQaCAIACu56g
Date:   Mon, 10 May 2021 03:28:07 +0000
Message-ID: <ad43e2df993e477cbe5d2db44ebbcad5@intel.com>
References: <20210421005728.1994268-1-nao.horiguchi@gmail.com>
        <d09f178272df4c82b8c090ba79d222b5@intel.com>
        <87ba79daaba1416589b203118be096cb@intel.com>
        <20210507052422.GB2158342@hori.linux.bs1.fc.nec.co.jp>
        <20210507191400.6258dee6@alex-virtual-machine>
        <e6577ace06ca4ce9bbfb8195d7a2bfb7@intel.com>
 <20210508103842.7dc6e8b1@alex-virtual-machine>
In-Reply-To: <20210508103842.7dc6e8b1@alex-virtual-machine>
Accept-Language: en-US
Content-Language: en-US
dlp-product: dlpe-windows
dlp-reaction: no-action
dlp-version: 11.5.1.3
Content-Type: text/plain; charset="iso-2022-jp"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Precedence: bulk

> Sorry, I am not sure if the stress test in my server is same with yours.

It's better if you test different things ... that's how we get better coverage.

> Usually, I will do one RAS stress test from mce-test/cases/stress before post something.
> Maybe this test is not general useful or you have tested it and passed or you may think
> the test is not proper though or you tested and you don't think it's one real issue,
> then just ignore it please.

I haven't re-run the mce-test cases for a while. The test that was run on these patches
involves a multi-threaded application running on all logical CPUs. When poison is injected
many of the CPUs can hit the poison close together. So it's a good stress test for the new
series.

-Tony