From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ming Lei <ming.lei@redhat.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-block@vger.kernel.org>,
Laurence Oberman <loberman@redhat.com>
Subject: Re: [PATCH V3 0/4] genirq/affinity: irq vector spread among online CPUs as far as possible
Date: Wed, 14 Mar 2018 11:30:56 +0800 [thread overview]
Message-ID: <b054b7da-baf0-3040-ffd4-47cab3300d51@cn.fujitsu.com> (raw)
In-Reply-To: <CAJZ5v0hKYJY9W3Gjo-KZzmfXhT7JqBxbe=AGPSQOSd4DCThJVA@mail.gmail.com>
Hi Rafael,
Thank you so much for your reply.
At 03/13/2018 05:25 PM, Rafael J. Wysocki wrote:
> On Tue, Mar 13, 2018 at 4:11 AM, Dou Liyang <douly.fnst@cn.fujitsu.com> wrote:
>> Hi Thomas,
>>
>> At 03/09/2018 11:08 PM, Thomas Gleixner wrote:
>> [...]
>>>
>>>
>>> I'm not sure if there is a clear indicator whether physcial hotplug is
>>> supported or not, but the ACPI folks (x86) and architecture maintainers
>>
>> +cc Rafael
>>
>>> should be able to answer that question. I have a machine which says:
>>>
>>> smpboot: Allowing 128 CPUs, 96 hotplug CPUs
>>>
>>> There is definitely no way to hotplug anything on that machine and sure
>>> the
>>
>>
>> AFAIK, in ACPI based dynamic reconfiguration, there is no clear
>> indicator. In theory, If the ACPI tables have the hotpluggable
>> CPU resources, the OS can support physical hotplug.
>
> In order for the ACPI-based CPU hotplug (I mean physical, not just the
> software offline/online we do in the kernel) to work, there have to be
> objects in the ACPI namespace corresponding to all of the processors
> in question.
>
> If they are not present, there is no way to signal insertion and eject
> the processors safely.
Yes, I see.
Thanks
dou
>
>
>
next prev parent reply other threads:[~2018-03-14 3:31 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 10:53 Ming Lei
2018-03-08 10:53 ` [PATCH V3 1/4] genirq/affinity: rename *node_to_possible_cpumask as *node_to_cpumask Ming Lei
2018-04-06 21:52 ` [tip:irq/core] genirq/affinity: Rename " tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 2/4] genirq/affinity: move actual irq vector spread into one helper Ming Lei
2018-04-06 21:53 ` [tip:irq/core] genirq/affinity: Move actual irq vector spreading into a helper function tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 3/4] genirq/affinity: support to do irq vectors spread starting from any vector Ming Lei
2018-04-06 21:53 ` [tip:irq/core] genirq/affinity: Allow irq spreading from a given starting point tip-bot for Ming Lei
2018-03-08 10:53 ` [PATCH V3 4/4] genirq/affinity: irq vector spread among online CPUs as far as possible Ming Lei
2018-04-03 13:32 ` Thomas Gleixner
2018-04-03 16:00 ` Ming Lei
2018-04-04 8:25 ` Thomas Gleixner
2018-04-04 12:45 ` Thomas Gleixner
2018-04-04 15:20 ` Ming Lei
2018-04-05 10:12 ` Thomas Gleixner
2018-04-04 15:08 ` Ming Lei
2018-04-04 19:38 ` Thomas Gleixner
2018-04-06 9:13 ` Ming Lei
2018-04-06 9:46 ` Thomas Gleixner
2018-04-06 21:49 ` Thomas Gleixner
2018-04-08 3:19 ` Ming Lei
2018-04-06 21:54 ` [tip:irq/core] genirq/affinity: Spread irq vectors among present " tip-bot for Ming Lei
2018-03-08 13:18 ` [PATCH V3 0/4] genirq/affinity: irq vector spread among online " Artem Bityutskiy
2018-03-08 13:25 ` Artem Bityutskiy
2018-03-08 13:34 ` Ming Lei
2018-03-08 23:20 ` Thomas Gleixner
2018-03-09 1:24 ` Ming Lei
2018-03-09 7:00 ` Artem Bityutskiy
2018-03-09 7:33 ` Ming Lei
2018-03-09 10:08 ` Thomas Gleixner
2018-03-09 12:08 ` Ming Lei
2018-03-09 15:08 ` Thomas Gleixner
2018-03-13 3:11 ` Dou Liyang
2018-03-13 7:38 ` Artem Bityutskiy
2018-03-13 8:35 ` Ming Lei
2018-03-13 8:39 ` Artem Bityutskiy
2018-03-13 9:35 ` Rafael J. Wysocki
2018-03-14 3:29 ` Dou Liyang
2018-03-14 4:11 ` Dou Liyang
2018-03-14 9:07 ` Artem Bityutskiy
2018-03-14 9:47 ` Dou Liyang
2018-03-13 9:25 ` Rafael J. Wysocki
2018-03-14 3:30 ` Dou Liyang [this message]
2018-03-30 3:15 ` Ming Lei
2018-04-03 12:55 ` Thomas Gleixner
2018-03-26 8:39 ` Thorsten Leemhuis
2018-03-28 6:15 ` Artem Bityutskiy
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=b054b7da-baf0-3040-ffd4-47cab3300d51@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=axboe@kernel.dk \
--cc=dedekind1@gmail.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=ming.lei@redhat.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®