[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB6083C2295753E7EDAE0EFA0FFC2D9@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Fri, 21 Oct 2022 03:57:33 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Miaohe Lin <linmiaohe@...wei.com>
CC: Naoya Horiguchi <naoya.horiguchi@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
Michael Ellerman <mpe@...erman.id.au>,
Nicholas Piggin <npiggin@...il.com>,
Christophe Leroy <christophe.leroy@...roup.eu>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Shuai Xue <xueshuai@...ux.alibaba.com>
Subject: RE: [PATCH v2] mm, hwpoison: Try to recover from copy-on write faults
>> + INIT_WORK(&p->work, do_sched_memory_failure);
>> + p->pfn = pfn;
>> + schedule_work(&p->work);
>
> There is already memory_failure_queue() that can do this. Can we use it directly?
Miaohe Lin,
Yes, can use that. A thousand thanks for pointing it out. I just tried it, and it works
perfectly.
I think I'll need to add an empty stub version for the CONFIG_MEMORY_FAILURE=n
build. But that's trivial.
-Tony
Powered by blists - more mailing lists