From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: david.vrabel@citrix.com, jgross@suse.com,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] xen/x86: Convert to hotplug state machine
Date: Fri, 26 Aug 2016 15:37:38 -0400 [thread overview]
Message-ID: <d7086558-1750-6a2e-bf23-ece9117b1a43@oracle.com> (raw)
In-Reply-To: <20160817083309.fmkksdchqexaxncz@linutronix.de>
On 08/17/2016 04:33 AM, Sebastian Andrzej Siewior wrote:
> On 2016-08-15 10:46:46 [-0400], Boris Ostrovsky wrote:
>> Switch to new CPU hotplug infrastructure.
>>
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>> ---
>> arch/x86/xen/enlighten.c | 115 +++++++++++++++++++++++++-------------------
>> include/linux/cpuhotplug.h | 2 +
>> 2 files changed, 67 insertions(+), 50 deletions(-)
>>
>> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
>> index c7f6b1f..2283976 100644
>> --- a/arch/x86/xen/enlighten.c
>> +++ b/arch/x86/xen/enlighten.c
>> @@ -1541,6 +1543,24 @@ static void __init xen_dom0_set_legacy_features(void)
>> x86_platform.legacy.rtc = 1;
>> }
>>
>> +static int xen_cpuhp_setup(void)
>> +{
>> + int rc;
>> +
>> + rc = cpuhp_setup_state_nocalls(CPUHP_XEN_PREPARE,
>> + "XEN_HVM_GUEST_PREPARE",
>> + xen_cpu_up_prepare, xen_cpu_up_cancel);
> The old states UP_CANCEL is different from UP_PREPARE. The latter was
> invoked only in the error case while your new callback is always
> invoked. From looking at the code you free memory in
> xen_cpu_up_cancel() which was allocated in xen_cpu_up_prepare() and
> therefore I would name it xen_cpu_dead().
Yes, "cancel" is wrong term to use here.
> If you do find the time, you might manage to rework the code to avoid
> using the _nocalls() function. If see this right, you use
> xen_setup_vcpu_info_placement() for the init in the first place. This
> uses for_each_possible_cpu macro. The cpuhp_setup_state() function would
> perform the init for all CPUs before they come up.
I am not sure I see what this would buy us.
Besides, cpuhp_setup_state() uses for_each_present_cpu().
>
>> + if (!rc) {
>> + rc = cpuhp_setup_state_nocalls(CPUHP_AP_XEN_ONLINE,
> If there is no need to run this after KVM's CLK callback please use
> CPUHP_AP_ONLINE_DYN. If there is such a need then please document it.
OK.
-boris
>
>> + "XEN_HVM_GUEST_PREPARE",
>> + xen_cpu_up_online, NULL);
>> + if (rc)
>> + cpuhp_remove_state_nocalls(CPUHP_XEN_PREPARE);
>> + }
>> +
>> + return rc;
>> +}
>> +
>> /* First C function to be called on Xen boot */
>> asmlinkage __visible void __init xen_start_kernel(void)
>> {
> Sebastian
next prev parent reply other threads:[~2016-08-26 19:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 14:46 [PATCH 0/2] Convert to new CPU hotplug framework Boris Ostrovsky
2016-08-15 14:46 ` [PATCH 1/2] xen/x86: Convert to hotplug state machine Boris Ostrovsky
2016-08-17 8:33 ` Sebastian Andrzej Siewior
2016-08-26 19:37 ` Boris Ostrovsky [this message]
2016-08-31 16:15 ` Sebastian Andrzej Siewior
2016-09-02 2:03 ` Boris Ostrovsky
2016-08-15 14:46 ` [PATCH 2/2] xen/events: " Boris Ostrovsky
2016-08-15 15:06 ` [Xen-devel] " David Vrabel
2016-08-15 15:58 ` Boris Ostrovsky
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=d7086558-1750-6a2e-bf23-ece9117b1a43@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bigeasy@linutronix.de \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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®