On Fri, Apr 24, 2015 at 05:22:12PM -0400, Rik van Riel wrote: > On 04/24/2015 05:11 PM, Frederic Weisbecker wrote: > > On Fri, Apr 24, 2015 at 03:24:27PM -0400, [email protected] wrote: > >> From: Rik van Riel <[email protected]> > >> > >> After system bootup, there is no totally reliable way to see > >> which CPUs are isolated, because the kernel may modify the > >> CPUs specified on the isolcpus= kernel command line option. > >> > >> Export the CPU list that actually got isolated in sysfs, > >> specifically in the file /sys/devices/system/cpu/isolated > >> > >> This can be used by system management tools like libvirt, > >> openstack, and others to ensure proper placement of tasks. > >> > >> Suggested-by: Li Zefan <[email protected]> > >> Signed-off-by: Rik van Riel <[email protected]> > > > > This patch should go through Peterz. > > Oh, fun. That's what I get for getting the get_maintainer.pl > script, which told me to go through Greg KH instead :) > > $ ./scripts/get_maintainer.pl -f drivers/base/cpu.c > Greg Kroah-Hartman <[email protected]> (supporter:DRIVER CORE, > KOBJ...) > [email protected] (open list)
That's right, I can take this, I missed this the last time Rik sent these, that's my fault. thanks, greg k-h -- 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/
