On 08/01/2013 09:28 PM, Michael Ellerman wrote: > On Wed, Jul 24, 2013 at 01:36:34PM -0500, Nathan Fontenot wrote: >> Memory I/O resources need to be marked as busy or else we cannot remove >> them when doing memory hot remove. > > I would have thought it was the opposite?
Me too. As it turns out the code in kernel/resource.c checks to make sure the IORESOURCE_BUSY flag is set when trying to release a resource. -Nathan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
