linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
To: wency@cn.fujitsu.com
Cc: linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org,
	linux-acpi@vger.kernel.org, len.brown@intel.com,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
	cmetcalf@tilera.com, linux-mm@kvack.org,
	isimatu.yasuaki@jp.fujitsu.com, paulus@samba.org,
	minchan.kim@gmail.com, kosaki.motohiro@jp.fujitsu.com,
	rientjes@google.com, cl@linux.com, linuxppc-dev@lists.ozlabs.org,
	akpm@linux-foundation.org, liuj97@gmail.com
Subject: Re: [RFC PATCH V6 04/19] memory-hotplug: offline and remove memory when removing the memory device
Date: Thu, 9 Aug 2012 17:41:04 +0200	[thread overview]
Message-ID: <CAFEPiEY7gBeLoEJggSjFsF92X1Lw9DzPvEfCxhBx75NKCiL6XQ@mail.gmail.com> (raw)
In-Reply-To: <1343980161-14254-5-git-send-email-wency@cn.fujitsu.com>

Hi,

> We should offline and remove memory when removing the memory device.
> The memory device can be removed by 2 ways:
> 1. send eject request by SCI
> 2. echo 1 >/sys/bus/pci/devices/PNP0C80:XX/eject
>

[snip]

> +
> +static int acpi_memory_disable_device(struct acpi_memory_device *mem_device)
> +{
> +       int result;
> +
> +       /*
> +        * Ask the VM to offline this memory range.
> +        * Note: Assume that this function returns zero on success
> +        */
> +       result = acpi_memory_device_remove_memory(mem_device);
> +

here we should check the result of acpi_memory_device_remove_memory()
and not continue if it failed.

>         /* Power-off and eject the device */
>         result = acpi_memory_powerdown_device(mem_device);
>         if (result) {

thanks,

- Vasilis

  reply	other threads:[~2012-08-09 15:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03  7:49 [RFC PATCH V6 00/19] memory-hotplug: hot-remove physical memory wency
2012-08-03  7:49 ` [RFC PATCH V6 01/19] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages() wency
2012-08-03  7:49 ` [RFC PATCH V6 02/19] memory-hotplug: implement offline_memory() wency
2012-08-03  7:49 ` [RFC PATCH V6 03/19] memory-hotplug: store the node id in acpi_memory_device wency
2012-08-03  7:49 ` [RFC PATCH V6 04/19] memory-hotplug: offline and remove memory when removing the memory device wency
2012-08-09 15:41   ` Vasilis Liaskovitis [this message]
2012-08-03  7:49 ` [RFC PATCH V6 05/19] memory-hotplug: check whether memory is present or not wency
2012-08-03  7:49 ` [RFC PATCH V6 06/19] memory-hotplug: export the function acpi_bus_remove() wency
2012-08-03  7:49 ` [RFC PATCH V6 07/19] memory-hotplug: call acpi_bus_remove() to remove memory device wency
2012-08-03  7:49 ` [RFC PATCH V6 08/19] memory-hotplug: remove /sys/firmware/memmap/X sysfs wency
2012-08-03  7:49 ` [RFC PATCH V6 09/19] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks wency
2012-08-03  7:49 ` [RFC PATCH V6 10/19] memory-hotplug: add memory_block_release wency
2012-09-06  7:06   ` wujianguo
2012-08-03  7:49 ` [RFC PATCH V6 11/19] memory-hotplug: remove_memory calls __remove_pages wency
2012-08-03  7:49 ` [RFC PATCH V6 12/19] memory-hotplug: introduce new function arch_remove_memory() wency
2012-08-03  7:49 ` [RFC PATCH V6 13/19] memory-hotplug: check page type in get_page_bootmem wency
2012-08-07  5:31   ` Wen Congyang
2012-08-03  7:49 ` [RFC PATCH V6 14/19] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap wency
2012-08-03  7:49 ` [RFC PATCH V6 15/19] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap wency
2012-08-07  3:48   ` Wen Congyang
2012-08-03  7:49 ` [RFC PATCH V6 16/19] memory-hotplug: free memmap " wency
2012-08-07  5:17   ` Wen Congyang
2012-08-03  7:49 ` [RFC PATCH V6 17/19] memory_hotplug: clear zone when the memory is removed wency
2012-08-03  7:49 ` [RFC PATCH V6 18/19] memory-hotplug: add node_device_release wency
2012-08-03  7:49 ` [RFC PATCH V6 19/19] memory-hotplug: remove sysfs file of node wency

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=CAFEPiEY7gBeLoEJggSjFsF92X1Lw9DzPvEfCxhBx75NKCiL6XQ@mail.gmail.com \
    --to=vasilis.liaskovitis@profitbricks.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=cmetcalf@tilera.com \
    --cc=isimatu.yasuaki@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=liuj97@gmail.com \
    --cc=minchan.kim@gmail.com \
    --cc=paulus@samba.org \
    --cc=rientjes@google.com \
    --cc=wency@cn.fujitsu.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).