public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	x86@kernel.org, toshi.kani@hp.com, imammedo@redhat.com,
	huawei.libin@huawei.com, paul.gortmaker@windriver.com,
	linux-kernel@vger.kernel.org, srivatsa.bhat@linux.vnet.ibm.com
Subject: Re: [PATCH] x86,cpu-hotplug: clear llc_shared_mask at CPU hotplug
Date: Thu, 3 Jul 2014 11:51:35 +0200	[thread overview]
Message-ID: <20140703095135.GA21776@pd.tnic> (raw)
In-Reply-To: <53B4E1A4.2050502@jp.fujitsu.com>

On Thu, Jul 03, 2014 at 01:52:52PM +0900, Yasuaki Ishimatsu wrote:
> I think that the reason to apply CPU number to ACPI ID is that CPU is
> used for the application without considering physical CPU. So even if
> CPU number is changed, it is no matter.

I don't think I understand what you're saying here...

> Thus the readded cores is numbered to unused CPU number.

Well, maybe we should use some method to number cores in a stable manner
so that they don't get new numbers when they reappear.

> I think the mask has 2 meanings as follows:
>   - representing CPUs that share same CPU cache.

... that share the last level cache.

>   - representing onlined CPUs

no, for that we have cpu_online_mask.

> So even if we keep their old numbers, we should clear the mask when
> offlinig CPU.

No, cpu_online_mask is for onlined cores. I think the mask which shows
which cores share a last level cache should not be changed *IF* the core
numbers remain stable, that is.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-07-03  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  6:41 [PATCH] x86,cpu-hotplug: clear llc_shared_mask at CPU hotplug Yasuaki Ishimatsu
2014-07-02 11:32 ` Borislav Petkov
2014-07-03  4:52   ` Yasuaki Ishimatsu
2014-07-03  9:51     ` Borislav Petkov [this message]
2014-07-04  0:14       ` Yasuaki Ishimatsu
2014-07-04 10:59         ` Borislav Petkov
2014-07-09  6:46           ` Yasuaki Ishimatsu
2014-07-02 11:45 ` Mike Galbraith

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=20140703095135.GA21776@pd.tnic \
    --to=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=huawei.libin@huawei.com \
    --cc=imammedo@redhat.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=toshi.kani@hp.com \
    --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