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 S1752806AbcI1FGZ (ORCPT <rfc822;w@1wt.eu>);
        Wed, 28 Sep 2016 01:06:25 -0400
Received: from mx2.suse.de ([195.135.220.15]:56577 "EHLO mx2.suse.de"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752208AbcI1FGR (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 28 Sep 2016 01:06:17 -0400
Date: Wed, 28 Sep 2016 07:05:48 +0200
From: Borislav Petkov <bp@suse.de>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        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
Message-ID: <20160928050548.GC6590@nazgul.tnic>
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=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <57EA8F96.6030303@redhat.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
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.

No need - we understand the issue.

What I don't understand is what information you need *exactly* in sysfs
from the offlined cores and why. Something like "I need to know the id
of the thread on core X on socket Y because..."

I've been trying to get it out of you but I've failed so far at it.

-- 
Regards/Gruss,
    Boris.

SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--