linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	lenb@kernel.org, toshi.kani@hp.com
Subject: Re: [PATCH v3 2/3 RESEND] acpi : prevent cpu from becoming online
Date: Fri, 13 Jul 2012 15:24:57 +0900	[thread overview]
Message-ID: <4FFFBF39.10202@jp.fujitsu.com> (raw)
In-Reply-To: <4FFEC60B.7040800@linux.vnet.ibm.com>

2012/07/12 21:41, Srivatsa S. Bhat wrote:
> On 07/12/2012 05:10 PM, Yasuaki Ishimatsu wrote:
>> Even if acpi_processor_handle_eject() offlines cpu, there is a chance
>> to online the cpu after that. So the patch closes the window by using
>> get/put_online_cpus().
>>
>> Why does the patch change _cpu_up() logic?
>>
>> The patch cares the race of hot-remove cpu and _cpu_up(). If the patch
>> does not change it, there is the following race.
>>
>> hot-remove cpu                         |  _cpu_up()
>> ------------------------------------- ------------------------------------
>> call acpi_processor_handle_eject()     |
>>       call cpu_down()                   |
>>       call get_online_cpus()            |
>>                                         | call cpu_hotplug_begin() and stop here
>>       call arch_unregister_cpu()        |
>>       call acpi_unmap_lsapic()          |
>>       call put_online_cpus()            |
>>                                         | start and continue _cpu_up()
>>       return acpi_processor_remove()    |
>> continue hot-remove the cpu            |
>>
>> So _cpu_up() can continue to itself. And hot-remove cpu can also continue
>> itself. If the patch changes _cpu_up() logic, the race disappears as below:
>>
>> hot-remove cpu                         | _cpu_up()
>> -----------------------------------------------------------------------
>> call acpi_processor_handle_eject()     |
>>       call cpu_down()                   |
>>       call get_online_cpus()            |
>>                                         | call cpu_hotplug_begin() and stop here
>>       call arch_unregister_cpu()        |
>>       call acpi_unmap_lsapic()          |
>>            cpu's cpu_present is set     |
>>            to false by set_cpu_present()|
>>       call put_online_cpus()            |
>>                                         | start _cpu_up()
>>                                         | check cpu_present() and return -EINVAL
>>       return acpi_processor_remove()    |
>> continue hot-remove the cpu            |
>>
>> Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
>>
> 
> Please consider fixing the grammar issue below (since it is a user-visible
> print statement). Other than that, everything looks fine.
> 
> Reviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>
>   
>> ---
>>   drivers/acpi/processor_driver.c |   14 ++++++++++++++
>>   kernel/cpu.c                    |    8 +++++---
>>   2 files changed, 19 insertions(+), 3 deletions(-)
>>
>> Index: linux-3.5-rc6/drivers/acpi/processor_driver.c
>> ===================================================================
>> --- linux-3.5-rc6.orig/drivers/acpi/processor_driver.c	2012-07-12 20:34:29.438289841 +0900
>> +++ linux-3.5-rc6/drivers/acpi/processor_driver.c	2012-07-12 20:39:29.190542257 +0900
>> @@ -850,8 +850,22 @@ static int acpi_processor_handle_eject(s
>>   			return ret;
>>   	}
>>
>> +	get_online_cpus();
>> +	/*
>> +	 * The cpu might become online again at this point. So we check whether
>> +	 * the cpu has been onlined or not. If the cpu became online, it means
>> +	 * that someone wants to use the cpu. So acpi_processor_handle_eject()
>> +	 * returns -EAGAIN.
>> +	 */
>> +	if (unlikely(cpu_online(pr->id))) {
>> +		put_online_cpus();
>> +		printk(KERN_WARNING "Failed to remove CPU %d, "
>> +		       "since someone onlines the cpu\n" , pr->id);
> 
> How about:
> "Failed to remove CPU %d, because some other task brought the CPU back online\n"

Looks good to me. I'll update it.

Thanks,
Yasuaki Ishimatsu

> 
> Regards,
> Srivatsa S. Bhat
> 
>> +		return -EAGAIN;
>> +	}
>>   	arch_unregister_cpu(pr->id);
>>   	acpi_unmap_lsapic(pr->id);
>> +	put_online_cpus();
>>   	return ret;
>>   }
>>   #else
>> Index: linux-3.5-rc6/kernel/cpu.c
>> ===================================================================
>> --- linux-3.5-rc6.orig/kernel/cpu.c	2012-07-12 20:34:29.438289841 +0900
>> +++ linux-3.5-rc6/kernel/cpu.c	2012-07-12 20:34:35.040219535 +0900
>> @@ -343,11 +343,13 @@ static int __cpuinit _cpu_up(unsigned in
>>   	unsigned long mod = tasks_frozen ? CPU_TASKS_FROZEN : 0;
>>   	struct task_struct *idle;
>>
>> -	if (cpu_online(cpu) || !cpu_present(cpu))
>> -		return -EINVAL;
>> -
>>   	cpu_hotplug_begin();
>>
>> +	if (cpu_online(cpu) || !cpu_present(cpu)) {
>> +		ret =  -EINVAL;
>> +		goto out;
>> +	}
>> +
>>   	idle = idle_thread_get(cpu);
>>   	if (IS_ERR(idle)) {
>>   		ret = PTR_ERR(idle);
>>
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2012-07-13  6:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 11:22 [PATCH v3 1/3] acpi : cpu hot-remove returns error when cpu_down() fails Yasuaki Ishimatsu
2012-07-12 11:27 ` [PATCH v3 2/3] acpi : prevent cpu from becoming online Yasuaki Ishimatsu
2012-07-12 11:40   ` [PATCH v3 2/3 RESEND] " Yasuaki Ishimatsu
2012-07-12 12:41     ` Srivatsa S. Bhat
2012-07-13  6:24       ` Yasuaki Ishimatsu [this message]
2012-07-12 16:49     ` Toshi Kani
2012-07-13  6:27       ` Yasuaki Ishimatsu
2012-07-12 11:28 ` [PATCH v3 3/3] acpi : acpi_bus_trim() stops removing devices when failing to remove the device Yasuaki Ishimatsu
2012-07-12 16:50   ` Toshi Kani
2012-07-13  7:16     ` Yasuaki Ishimatsu
2012-10-09  8:02   ` Wen Congyang
2012-10-09  8:24     ` Yasuaki Ishimatsu
2012-07-12 12:32 ` [PATCH v3 1/3] acpi : cpu hot-remove returns error when cpu_down() fails Srivatsa S. Bhat
2012-07-13  6:29   ` Yasuaki Ishimatsu
2012-07-12 16:48 ` Toshi Kani
2012-07-13  6:26   ` Yasuaki Ishimatsu

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=4FFFBF39.10202@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=toshi.kani@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).