From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756501AbbCRSRG (ORCPT ); Wed, 18 Mar 2015 14:17:06 -0400 Received: from mail-vc0-f181.google.com ([209.85.220.181]:44690 "EHLO mail-vc0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750756AbbCRSRC (ORCPT ); Wed, 18 Mar 2015 14:17:02 -0400 Date: Wed, 18 Mar 2015 14:16:52 -0400 From: Tejun Heo To: Dmitry Torokhov Cc: Greg Kroah-Hartman , "Luis R . Rodriguez" , linux-kernel@vger.kernel.org, Arjan van de Ven , Rusty Russell , Olof Johansson , Tetsuo Handa Subject: Re: [PATCH 6/8] amd64_edac: enforce synchronous probe Message-ID: <20150318181652.GA25365@htj.duckdns.org> References: <1421451197-19723-1-git-send-email-dmitry.torokhov@gmail.com> <1421451197-19723-7-git-send-email-dmitry.torokhov@gmail.com> <20150318165618.GB21564@htj.duckdns.org> <20150318174544.GD11485@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150318174544.GD11485@dtor-ws> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, On Wed, Mar 18, 2015 at 10:45:44AM -0700, Dmitry Torokhov wrote: > Without the debug options how can we do that? I will definitely not be > able to go through all the in-tree drivers myself and see if they can be > asynchronously probed or not. The most I can do is to try enabling the > option on our side and fixing the drivers/subsystems that fail with > asynchronous probing. This will be iterative process for some time and > then we'll drop the debug option and flip the flag to do asynchronous > probing by default. Is this even useful for most drivers? If not, let's just stick with whitelisting. If it is useful, I worry that we're quite unlikely to build working blacklist with this approach. idk, having both white and blacklists tend to end badly. Thanks. -- tejun