lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 04 May 2015 17:15:52 -0400 From: Rik van Riel <riel@...hat.com> To: Greg KH <gregkh@...uxfoundation.org> CC: Frederic Weisbecker <fweisbec@...il.com>, Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org, tj@...nel.org, umgwanakikbuti@...il.com, lizefan@...wei.com Subject: Re: [PATCH 1/2] show isolated cpus in sysfs On 04/24/2015 05:49 PM, Greg KH wrote: > 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, riel@...hat.com wrote: >>>> From: Rik van Riel <riel@...hat.com> >>>> >>>> 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 <lizefan@...wei.com> >>>> Signed-off-by: Rik van Riel <riel@...hat.com> >>> >>> 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 <gregkh@...uxfoundation.org> (supporter:DRIVER CORE, >> KOBJ...) >> linux-kernel@...r.kernel.org (open list) > > That's right, I can take this, I missed this the last time Rik sent > these, that's my fault. Ping? Let me harass you before we both forget and this thing falls through the cracks again :) -- All rights reversed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists