From: Sasha Levin <sasha.levin@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-kernel@vger.kernel.org, penberg@kernel.org
Subject: Re: [PATCH] x86, smpboot: allow manual hotplug of CPUs
Date: Wed, 21 Nov 2012 14:35:50 -0500 [thread overview]
Message-ID: <50AD2D16.7050304@oracle.com> (raw)
In-Reply-To: <50AD2A85.7030705@zytor.com>
On 11/21/2012 02:24 PM, H. Peter Anvin wrote:
> On 11/21/2012 11:19 AM, Sasha Levin wrote:
>>>
>>> So, are there any mptables platforms which support hotplug? If the
>>> answer is "KVM" then the answer is that KVM needs to move to ACPI to get
>>> the proper functionality; putting a hack in is really not okay.
>>
>> There are no platforms which support actual hotplug, but you can still set
>> existing processors as disabled in the table and without this patch there's
>> no way enable them.
>>
>> I'm not sure if it's a "hack" though - the presentation of hotpluggable cpus
>> is the almost the same between mptable and acpi, and acpi provides a way to
>> manually probe/release cpus as well. The only difference is that acpi also
>> provides notifications about such events.
>>
>> Actually, maybe acpi should start using probe/release as well... hmm...
>>
>
> The bottom line is that I don't want the underlying implementation to
> end up with a user-visible difference... therein lies madness and lots
> of bugs.
Okay, so if in the case of ACPI, 'probe' will call acpi_processor_add()
and 'release' would call acpi_processor_remove() so the behaviour
would be the same for both ACPI and mptables. Is this okay?
Thanks,
Sasha
next prev parent reply other threads:[~2012-11-21 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 18:22 Sasha Levin
2012-11-21 18:25 ` H. Peter Anvin
2012-11-21 18:35 ` Sasha Levin
2012-11-21 18:38 ` H. Peter Anvin
2012-11-21 19:19 ` Sasha Levin
2012-11-21 19:24 ` H. Peter Anvin
2012-11-21 19:35 ` Sasha Levin [this message]
2012-11-21 19:39 ` H. Peter Anvin
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=50AD2D16.7050304@oracle.com \
--to=sasha.levin@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®