linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jerry <uulinux@gmail.com>
To: Minchan Kim <minchan@kernel.org>, Wen Congyang <wency@cn.fujitsu.com>
Cc: linux-s390@vger.kernel.org, linux-ia64@vger.kernel.org,
	len.brown@intel.com, linux-acpi@vger.kernel.org,
	linux-sh@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, cmetcalf@tilera.com,
	Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
	linux-mm@kvack.org,
	Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>,
	paulus@samba.org, kosaki.motohiro@jp.fujitsu.com,
	rientjes@google.com, sparclinux@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	linuxppc-dev@lists.ozlabs.org, cl@linux.com, liuj97@gmail.com
Subject: Re: [RFC v8 PATCH 00/20] memory-hotplug: hot-remove physical memory
Date: Tue, 11 Sep 2012 13:18:24 +0800	[thread overview]
Message-ID: <CAAV+Mu4hb0qbW2Ry6w5FAGUM06puDH0v_H-jr584-G9CzJqSGw@mail.gmail.com> (raw)
In-Reply-To: <20120911012345.GD14205@bbox>

[-- Attachment #1: Type: text/plain, Size: 4464 bytes --]

Hi Kim,

Thank you for your kindness. Let me clarify this:

On ARM architecture, there are 32 bits physical addresses space. However,
the addresses space is divided into 8 banks normally. Each bank
disabled/enabled by a chip selector signal. In my platform, bank0 connects
a DDR chip, and bank1 also connects another DDR chip. And each DDR chip
whose capability is 512MB is integrated into the main board. So, it could
not be removed by hand. We can disable/enable each bank by peripheral
device controller registers.

When system enter suspend state, if all the pages allocated could be
migrated to one bank, there are no valid data in the another bank. In this
time, I could disable the free bank. It isn't necessary to provided power
to this chip in the suspend state. When system resume, I just need to
enable it again.

Hi Wen,

I am sorry for that I doesn't know the "_PSx support" means. Maybe I
needn't it.

Thanks,
Jerry

2012/9/11 Minchan Kim <minchan@kernel.org>

> Hi Jerry,
>
> On Tue, Sep 11, 2012 at 08:27:40AM +0800, Jerry wrote:
> > Hi Wen,
> >
> > I have been arranged a job related memory hotplug on ARM architecture.
> > Maybe I know some new issues about memory hotplug on ARM architecture. I
> > just enabled it on ARM, and it works well in my Android tablet now.
> > However, I have not send out my patches. The real reason is that I don't
> > know how to do it. Maybe I need to read
> "Documentation/SubmittingPatches".
> >
> > Hi Andrew,
> > This is my first time to send you a e-mail. I am so nervous about if I
> have
> > some mistakes or not.
>
> Don't be afraid.
> If you might make a mistake, it's very natural to newbie.
> I am sure anyone doesn't blame you. :)
> If you have a good patch, please send out.
>
> >
> > Some peoples maybe think memory hotplug need to be supported by special
> > hardware. Maybe it means memory physical hotplug. Some times, we just
> need
> > to use memory logical hotplug, doesn't remove the memory in physical. It
> is
> > also usefully for power saving in my platform. Because I doesn't want
> > the offline memory is in *self-refresh* state.
>
> Just out of curiosity.
> What's the your scenario and gain?
> AFAIK, there were some effort about it in embedded side but gain isn't
> rather big
> IIRC.
>
> >
> > Any comments are appreciated.
> >
> > Thanks,
> > Jerry
> >
> > 2012/9/10 Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
> >
> > > Hi,
> > >
> > > On Mon, Sep 10, 2012 at 10:01:44AM +0800, Wen Congyang wrote:
> > > > At 09/10/2012 09:46 AM, Yasuaki Ishimatsu Wrote:
> > > > > Hi Wen,
> > > > >
> > > > > 2012/09/01 5:49, Andrew Morton wrote:
> > > > >> On Tue, 28 Aug 2012 18:00:07 +0800
> > > > >> wency@cn.fujitsu.com wrote:
> > > > >>
> > > > >>> This patch series aims to support physical memory hot-remove.
> > > > >>
> > > > >> I doubt if many people have hardware which permits physical memory
> > > > >> removal?  How would you suggest that people with regular hardware
> can
> > > > >> test these chagnes?
> > > > >
> > > > > How do you test the patch? As Andrew says, for hot-removing memory,
> > > > > we need a particular hardware. I think so too. So many people may
> want
> > > > > to know how to test the patch.
> > > > > If we apply following patch to kvm guest, can we hot-remove memory
> on
> > > > > kvm guest?
> > > > >
> > > > > http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg01389.html
> > > >
> > > > Yes, if we apply this patchset, we can test hot-remove memory on kvm
> > > guest.
> > > > But that patchset doesn't implement _PS3, so there is some
> restriction.
> > >
> > > the following repos contain the patchset above, plus 2 more patches
> that
> > > add
> > > PS3 support to the dimm devices in qemu/seabios:
> > >
> > > https://github.com/vliaskov/seabios/commits/memhp-v2
> > > https://github.com/vliaskov/qemu-kvm/commits/memhp-v2
> > >
> > > I have not posted the PS3 patches yet in the qemu list, but will post
> them
> > > soon for v3 of the memory hotplug series. If you have issues testing,
> let
> > > me
> > > know.
> > >
> > > thanks,
> > >
> > > - Vasilis
> > >
> > > --
> > > To unsubscribe, send a message with 'unsubscribe linux-mm' in
> > > the body to majordomo@kvack.org.  For more info on Linux MM,
> > > see: http://www.linux-mm.org/ .
> > > Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> > >
> >
> >
> >
> > --
> > I love linux!!!
>
> --
> Kind regards,
> Minchan Kim
>



-- 
I love linux!!!

[-- Attachment #2: Type: text/html, Size: 6648 bytes --]

  reply	other threads:[~2012-09-11  5:18 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 10:00 [RFC v8 PATCH 00/20] memory-hotplug: hot-remove physical memory wency
2012-08-28 10:00 ` [RFC v8 PATCH 01/20] memory-hotplug: rename remove_memory() to offline_memory()/offline_pages() wency
2012-08-28 10:00 ` [RFC v8 PATCH 02/20] memory-hotplug: implement offline_memory() wency
2012-08-28 10:00 ` [RFC v8 PATCH 03/20] memory-hotplug: store the node id in acpi_memory_device wency
2012-08-28 10:00 ` [RFC v8 PATCH 04/20] memory-hotplug: offline and remove memory when removing the memory device wency
2012-08-31 20:55   ` Andrew Morton
2012-09-03  1:30     ` Wen Congyang
2012-08-28 10:00 ` [RFC v8 PATCH 05/20] memory-hotplug: check whether memory is present or not wency
2012-08-28 10:00 ` [RFC v8 PATCH 06/20] memory-hotplug: export the function acpi_bus_remove() wency
2012-08-28 10:00 ` [RFC v8 PATCH 07/20] memory-hotplug: call acpi_bus_remove() to remove memory device wency
2012-08-28 10:00 ` [RFC v8 PATCH 08/20] memory-hotplug: remove /sys/firmware/memmap/X sysfs wency
2012-08-31 21:06   ` Andrew Morton
2012-09-03  5:51     ` Wen Congyang
2012-09-04 23:16       ` Andrew Morton
2012-09-05  1:41         ` Wen Congyang
2012-09-03  7:31     ` Wen Congyang
2012-08-28 10:00 ` [RFC v8 PATCH 09/20] memory-hotplug: does not release memory region in PAGES_PER_SECTION chunks wency
2012-08-28 10:00 ` [RFC v8 PATCH 10/20] memory-hotplug: add memory_block_release wency
2012-08-28 10:00 ` [RFC v8 PATCH 11/20] memory-hotplug: remove_memory calls __remove_pages wency
2012-08-28 10:00 ` [RFC v8 PATCH 12/20] memory-hotplug: introduce new function arch_remove_memory() wency
2012-08-28 10:00 ` [RFC v8 PATCH 13/20] memory-hotplug: check page type in get_page_bootmem wency
2012-08-31 21:30   ` Andrew Morton
2012-09-04  3:46     ` Wen Congyang
2012-09-04  9:54       ` Yasuaki Ishimatsu
2012-08-28 10:00 ` [RFC v8 PATCH 14/20] memory-hotplug: move register_page_bootmem_info_node and put_page_bootmem for sparse-vmemmap wency
2012-08-28 10:00 ` [RFC v8 PATCH 15/20] memory-hotplug: implement register_page_bootmem_info_section of sparse-vmemmap wency
2012-08-28 10:00 ` [RFC v8 PATCH 16/20] memory-hotplug: free memmap " wency
2012-08-28 10:00 ` [RFC v8 PATCH 17/20] memory_hotplug: clear zone when the memory is removed wency
2012-08-28 10:00 ` [RFC v8 PATCH 18/20] memory-hotplug: add node_device_release wency
2012-08-28 10:00 ` [RFC v8 PATCH 19/20] memory-hotplug: remove sysfs file of node wency
2012-08-28 10:00 ` [RFC v8 PATCH 20/20] memory-hotplug: clear hwpoisoned flag when onlining pages wency
2012-08-31 20:49 ` [RFC v8 PATCH 00/20] memory-hotplug: hot-remove physical memory Andrew Morton
2012-09-10  1:46   ` Yasuaki Ishimatsu
2012-09-10  2:01     ` Wen Congyang
2012-09-10 13:52       ` Vasilis Liaskovitis
2012-09-11  0:27         ` Jerry
2012-09-11  1:23           ` Minchan Kim
2012-09-11  5:18             ` Jerry [this message]
2012-09-11  5:39               ` Wen Congyang
2012-09-12  6:17               ` Minchan Kim
2012-09-11  1:25           ` Wen Congyang
2012-09-12  5:20         ` Wen Congyang
2012-09-12 17:18           ` Vasilis Liaskovitis
2012-09-18  9:39             ` Wen Congyang
2012-09-19 17:02               ` Vasilis Liaskovitis

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=CAAV+Mu4hb0qbW2Ry6w5FAGUM06puDH0v_H-jr584-G9CzJqSGw@mail.gmail.com \
    --to=uulinux@gmail.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@kernel.org \
    --cc=paulus@samba.org \
    --cc=rientjes@google.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=vasilis.liaskovitis@profitbricks.com \
    --cc=wency@cn.fujitsu.com \
    --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;
as well as URLs for NNTP newsgroup(s).