linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Borislav Petkov <bp@suse.de>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Len Brown <len.brown@intel.com>, Andi Kleen <ak@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 0/2 v3] cpu hotplug: Preserve topology directory after soft remove event
Date: Tue, 27 Sep 2016 11:26:14 -0400	[thread overview]
Message-ID: <57EA8F96.6030303@redhat.com> (raw)
In-Reply-To: <20160927134957.GB19759@kroah.com>



On 09/27/2016 09:49 AM, Greg Kroah-Hartman wrote:
> On Tue, Sep 27, 2016 at 07:45:56AM -0400, Prarit Bhargava wrote:
>> On 09/26/2016 07:57 AM, Borislav Petkov wrote:
>>> $ echo 0 > /sys/devices/system/cpu/cpu2/online
>>
>> This results in the topology directory being destroyed.  It shouldn't be -- the
>> socket and core are still there.  If you could open up your computer you could
>> touch them.  This is similar to downing a PCI device, or removing !kernel memory
>> DIMM from a system.  The device is still physically there.
> 
> If you remove a PCI device from the system, by turning it off from the
> PCI hotplug interface, it will go away from sysfs, just like this CPU
> device is going away, no matter if you physically remove the device or
> not.
> 

While similar, the thread's device struct, link to structures, and masks in the
kernel are kept in place.  In the PCI case these links are all destroyed which
results in requiring a bus rescan to find the devcie.  The sysfs (soft) removal
of a thread has a very different outcome from PCI.

I see now that the issue is not understanding the difference between physical
and soft thread removal.  I will write that up and get back to everyone.

P.

> Thanks for validating that everything is working the same and correctly
> :)
> 
> greg k-h
> 

  reply	other threads:[~2016-09-27 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 11:39 [PATCH 0/2 v3] cpu hotplug: Preserve topology directory after soft remove event Prarit Bhargava
2016-09-21 11:39 ` [PATCH 1/2 v3] drivers/base: Combine topology.c and cpu.c Prarit Bhargava
2016-09-21 11:39 ` [PATCH 2/2 v3] cpu hotplug: add CONFIG_PERMANENT_CPU_TOPOLOGY Prarit Bhargava
2016-09-21 13:04 ` [PATCH 0/2 v3] cpu hotplug: Preserve topology directory after soft remove event Borislav Petkov
2016-09-21 13:32   ` Prarit Bhargava
2016-09-21 14:01     ` Borislav Petkov
2016-09-22 11:59       ` Prarit Bhargava
2016-09-22 12:10         ` Borislav Petkov
2016-09-26 11:45           ` Prarit Bhargava
2016-09-26 11:57             ` Borislav Petkov
2016-09-27 11:45               ` Prarit Bhargava
2016-09-27 13:49                 ` Greg Kroah-Hartman
2016-09-27 15:26                   ` Prarit Bhargava [this message]
2016-09-28  5:05                     ` Borislav Petkov
2016-09-28  6:48                     ` Peter Zijlstra
2016-09-28 10:06                       ` Prarit Bhargava
2016-09-28  5:02                 ` Borislav Petkov
2016-09-26 11:59             ` Peter Zijlstra
2016-09-27 11:47               ` Prarit Bhargava
2016-09-27 11:57                 ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57EA8F96.6030303@redhat.com \
    --to=prarit@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=bp@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.com \
    --cc=jolsa@redhat.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).