From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756735AbbCRTvq (ORCPT ); Wed, 18 Mar 2015 15:51:46 -0400 Received: from mail-vc0-f177.google.com ([209.85.220.177]:55369 "EHLO mail-vc0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755201AbbCRTvo (ORCPT ); Wed, 18 Mar 2015 15:51:44 -0400 Date: Wed, 18 Mar 2015 15:51:41 -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: <20150318195141.GD25365@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> <20150318181652.GA25365@htj.duckdns.org> <20150318182318.GF11485@dtor-ws> <20150318182742.GB25365@htj.duckdns.org> <20150318183731.GG11485@dtor-ws> <20150318184550.GC25365@htj.duckdns.org> <20150318193622.GH11485@dtor-ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150318193622.GH11485@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 12:36:22PM -0700, Dmitry Torokhov wrote: > Because they are not inherently problematic. I mean from the kernel POV > they work fine, the question is if your userspace can deal with them or > not. For example ChromeOS userspace is fine. async already provides mechanisms to solve the above problem. This doesn't have to be an either-or thing. I still don't get why we aren't converting drivers properly over to async so that they still follow the ordering rules where necessary. What's wrong with just blacklisting the ones which can't follow ordering rules for now and lifting the blacklist as they get fixed? That'd provide a gradual transition path with the matching incentive for converting the drivers while not disturbing userland. Thanks. -- tejun