Re: [PATCH 6/8] amd64_edac: enforce synchronous probe

[Tejun Heo]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/