From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1750849AbcI1Gsv (ORCPT <rfc822;w@1wt.eu>);
        Wed, 28 Sep 2016 02:48:51 -0400
Received: from merlin.infradead.org ([205.233.59.134]:42684 "EHLO
        merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750714AbcI1Gsn (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 28 Sep 2016 02:48:43 -0400
Date: Wed, 28 Sep 2016 08:48:23 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        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,
        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
Message-ID: <20160928064823.GR2794@worktop>
References: <20160921130428.2e7bprll64vs6h2r@pd.tnic>
 <57E28BFF.8060107@redhat.com>
 <20160921140135.i5emid4qno2o6cre@pd.tnic>
 <57E3C78C.5040400@redhat.com>
 <20160922121039.l6lnhb53os2af27x@pd.tnic>
 <57E90A61.60402@redhat.com>
 <20160926115728.sdnvjaz3ty6xpsvr@pd.tnic>
 <57EA5BF4.1060508@redhat.com>
 <20160927134957.GB19759@kroah.com>
 <57EA8F96.6030303@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <57EA8F96.6030303@redhat.com>
User-Agent: Mutt/1.5.22.1 (2013-10-16)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Sep 27, 2016 at 11:26:14AM -0400, Prarit Bhargava wrote:
> 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.

You don't seem to understand that from the kernels POV there is no such
distinction.

There is only one unplug operation that caters to both cases. Therefore
unplug needs to assume the most stringent (ie. physical) for things to
work right.

There is no 'soft thread removal', except maybe in the userspace API,
you're the one that is confused.