All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: cl@linux.com, mika.j.penttila@gmail.com, mingo@redhat.com,
	akpm@linux-foundation.org, rjw@rjwysocki.net, hpa@zytor.com,
	yasu.isimatu@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
	gongzhaogang@inspur.com, len.brown@intel.com, lenb@kernel.org,
	tglx@linutronix.de, chen.tang@easystack.cn, rafael@kernel.org,
	x86@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v8 7/7] Provide the interface to validate the proc_id which they give
Date: Tue, 19 Jul 2016 14:53:20 -0400	[thread overview]
Message-ID: <20160719185320.GN3078@mtj.duckdns.org> (raw)
In-Reply-To: <1468913288-16605-8-git-send-email-douly.fnst@cn.fujitsu.com>

On Tue, Jul 19, 2016 at 03:28:08PM +0800, Dou Liyang wrote:
> When we want to identify whether the proc_id is unreasonable or not, we
> can call the "acpi_processor_validate_proc_id" function. It will search
> in the duplicate IDs. If we find the proc_id in the IDs, we return true
> to the call function. Conversely, false represents available.
> 
> When we establish all possible cpuid <-> nodeid mapping, we will use the
> proc_id from ACPI table.
> 
> We do validation when we get the proc_id. If the result is true, we will
> stop the mapping.

The patch title probably should include "acpi:" header.  I can't tell
much about the specifics of the acpi changes but I think this is the
right approach for handling cpu hotplugs.

Thanks.

-- 
tejun

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Dou Liyang <douly.fnst@cn.fujitsu.com>
Cc: cl@linux.com, mika.j.penttila@gmail.com, mingo@redhat.com,
	akpm@linux-foundation.org, rjw@rjwysocki.net, hpa@zytor.com,
	yasu.isimatu@gmail.com, isimatu.yasuaki@jp.fujitsu.com,
	kamezawa.hiroyu@jp.fujitsu.com, izumi.taku@jp.fujitsu.com,
	gongzhaogang@inspur.com, len.brown@intel.com, lenb@kernel.org,
	tglx@linutronix.de, chen.tang@easystack.cn, rafael@kernel.org,
	x86@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v8 7/7] Provide the interface to validate the proc_id which they give
Date: Tue, 19 Jul 2016 14:53:20 -0400	[thread overview]
Message-ID: <20160719185320.GN3078@mtj.duckdns.org> (raw)
In-Reply-To: <1468913288-16605-8-git-send-email-douly.fnst@cn.fujitsu.com>

On Tue, Jul 19, 2016 at 03:28:08PM +0800, Dou Liyang wrote:
> When we want to identify whether the proc_id is unreasonable or not, we
> can call the "acpi_processor_validate_proc_id" function. It will search
> in the duplicate IDs. If we find the proc_id in the IDs, we return true
> to the call function. Conversely, false represents available.
> 
> When we establish all possible cpuid <-> nodeid mapping, we will use the
> proc_id from ACPI table.
> 
> We do validation when we get the proc_id. If the result is true, we will
> stop the mapping.

The patch title probably should include "acpi:" header.  I can't tell
much about the specifics of the acpi changes but I think this is the
right approach for handling cpu hotplugs.

Thanks.

-- 
tejun

  reply	other threads:[~2016-07-19 18:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  7:28 [PATCH v8 0/7] Make cpuid <-> nodeid mapping persistent Dou Liyang
2016-07-19  7:28 ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 1/7] x86, memhp, numa: Online memory-less nodes at boot time Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19 18:50   ` Tejun Heo
2016-07-19 18:50     ` Tejun Heo
2016-07-20  1:52     ` Dou Liyang
2016-07-20  1:52       ` Dou Liyang
2016-07-20  2:28     ` Dou Liyang
2016-07-20  2:28       ` Dou Liyang
2016-07-20  2:28       ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 2/7] x86, acpi, cpu-hotplug: Enable acpi to register all possible cpus " Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 3/7] x86, acpi, cpu-hotplug: Introduce cpuid_to_apicid[] array to store persistent cpuid <-> apicid mapping Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 4/7] x86, acpi, cpu-hotplug: Enable MADT APIs to return disabled apicid Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 5/7] x86, acpi, cpu-hotplug: Set persistent cpuid <-> nodeid mapping when booting Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19 20:06   ` Rafael J. Wysocki
2016-07-19 20:06     ` Rafael J. Wysocki
2016-07-20  1:25     ` Dou Liyang
2016-07-20  1:25       ` Dou Liyang
2016-07-20  1:25       ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 6/7] Provide the mechanism to validate processors in the ACPI tables Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19  7:28 ` [PATCH v8 7/7] Provide the interface to validate the proc_id which they give Dou Liyang
2016-07-19  7:28   ` Dou Liyang
2016-07-19 18:53   ` Tejun Heo [this message]
2016-07-19 18:53     ` Tejun Heo
2016-07-20  0:55     ` Dou Liyang
2016-07-20  0:55       ` Dou Liyang
2016-07-20  0:55       ` Dou Liyang

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=20160719185320.GN3078@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chen.tang@easystack.cn \
    --cc=cl@linux.com \
    --cc=douly.fnst@cn.fujitsu.com \
    --cc=gongzhaogang@inspur.com \
    --cc=hpa@zytor.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=len.brown@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mika.j.penttila@gmail.com \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=yasu.isimatu@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.