From: Matthew Garrett <mjg@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [RFC PATCH]: ACPI: Automatically online hot-added memory
Date: Tue, 9 Mar 2010 15:42:43 +0000 [thread overview]
Message-ID: <20100309154243.GA26520@srcf.ucam.org> (raw)
In-Reply-To: <20100309141203.10037.62453.sendpatchset@prarit.bos.redhat.com>
On Tue, Mar 09, 2010 at 09:12:03AM -0500, Prarit Bhargava wrote:
> New sockets have on-die memory controllers. This means that in certain
> HW configurations the memory behind the socket comes and goes as the socket
> is physically enabled and disabled.
>
> Since the cpu bringup code does on node memory allocations, the memory on the
> added socket must be onlined first.
>
> Add a .config option to automatically online hot added memory, and enable it
> in the acpi memory add path.
This seems like the right thing to do.
> +config ACPI_HOTPLUG_MEMORY_AUTO_ONLINE
> + bool "Automatically online hotplugged memory"
> + depends on ACPI_HOTPLUG_MEMORY
> + default n
default !S390? default x86?
> + result = online_pages(info->start_addr >> PAGE_SHIFT,
> + info->length >> PAGE_SHIFT);
> + if (!result)
> + set_memory_state(info->start_addr, MEM_ONLINE);
> + else
> + printk("Memory online failed.\n");
That probably wants to be more descriptive and have a loglevel. What
happens if this fails? The CPU presumably can't be brought up?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2010-03-09 15:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 14:12 [RFC PATCH]: ACPI: Automatically online hot-added memory Prarit Bhargava
2010-03-09 15:42 ` Matthew Garrett [this message]
2010-03-09 18:27 ` Prarit Bhargava
2010-03-10 1:57 ` ykzhao
2010-03-10 13:28 ` Prarit Bhargava
2010-03-11 0:55 ` ykzhao
2010-03-11 2:18 ` Prarit Bhargava
2010-03-11 8:07 ` ykzhao
2010-03-11 8:32 ` chen gong
2010-03-11 11:25 ` Prarit Bhargava
2010-03-12 13:18 ` Thomas Renninger
2010-03-17 18:47 ` Prarit Bhargava
2010-03-19 16:55 ` Thomas Renninger
2010-03-19 17:23 ` Prarit Bhargava
2010-03-20 20:51 ` Thomas Renninger
2010-03-24 14:40 ` Thomas Renninger
2010-03-24 15:16 ` Prarit Bhargava
2010-03-11 11:18 ` Prarit Bhargava
2010-03-12 1:31 ` ykzhao
2010-03-12 13:01 ` Thomas Renninger
2010-03-17 15:24 ` Prarit Bhargava
2010-03-09 19:10 ` Alex Chiang
2010-03-09 19:10 ` Alex Chiang
2010-03-09 19:15 ` Prarit Bhargava
2010-03-09 19:15 ` Prarit Bhargava
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=20100309154243.GA26520@srcf.ucam.org \
--to=mjg@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=prarit@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.