linux-kernel - Re: [PATCH 2/2] cpu hotplug, add CONFIG_PERMANENT_CPU

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <57D16B76.2070303@redhat.com>
Date:   Thu, 08 Sep 2016 09:45:26 -0400
From:   Prarit Bhargava <prarit@...hat.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Len Brown <len.brown@...el.com>, Borislav Petkov <bp@...e.de>,
        Andi Kleen <ak@...ux.intel.com>, Jiri Olsa <jolsa@...hat.com>,
        Juergen Gross <jgross@...e.com>
Subject: Re: [PATCH 2/2] cpu hotplug, add CONFIG_PERMANENT_CPU_TOPOLOGY



On 09/08/2016 03:45 AM, Peter Zijlstra wrote:
> On Wed, Sep 07, 2016 at 07:44:17AM -0400, Prarit Bhargava wrote:
>> The information in /sys/devices/system/cpu/cpuX/topology
>> directory is useful for userspace monitoring applications and in-tree
>> utilities like cpupower & turbostat.
>>
>> When down'ing a CPU the /sys/devices/system/cpu/cpuX/topology directory is
>> removed during the CPU_DEAD hotplug callback in the kernel.  The problem
>> with this model is that the CPU has not been physically removed and the
>> data in the topology directory is still valid and the cpu's location is
>> now lost to userspace.
>>
>> This patch adds CONFIG_PERMANENT_CPU_TOPOLOGY, and is Y by default for
>> x86, an N for all other arches.  When enabled the kernel is modified so
>> that the topology directory is added to the core cpu sysfs files so that
>> the topology directory exists while the CPU is physically present.  When
>> disabled, the behavior of the current kernel is maintained (that is, the
>> topology directory is removed on a soft down and added on an soft up).
>> Adding CONFIG_PERMANENT_CPU_TOPOLOGY may require additional architecture
>> so that the cpumask data the CPU's topology is not cleared during a CPU
>> down.
> 
> So how do you physically remove things and how does the information then
> get removed?
> 

Physical hotremove was done with a toggle switch enabled test box.

The topology directory gets removed when either common_cpu_attr_groups
(!CONFIG_HOTPLUG_CPU) or hotplugable_cpu_attr_groups (CONFIG_HOTPLUG_CPU) are
destroyed.  The cpu device's attributes are set in register_cpu() and the device
is destroyed in unregister_cpu().

IOW, the patch expands the lifetime of the topology directories to match that of
the device.

> Also, why is that an x86 only feature?

The only arch that I could test on was x86 and I wasn't able to test to see if
topology fields are valid for other arches on a soft remove.  So x86 by default
for now and other arches can make their decisions.

P.