From: Thomas Renninger <trenn@suse.de>
To: chen gong <gong.chen@linux.intel.com>
Cc: ykzhao <yakui.zhao@intel.com>,
Prarit Bhargava <prarit@redhat.com>,
Matthew Garrett <mjg@redhat.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
trenn@novell.com
Subject: Re: [RFC PATCH]: ACPI: Automatically online hot-added memory
Date: Fri, 12 Mar 2010 14:18:14 +0100 [thread overview]
Message-ID: <201003121418.14204.trenn@suse.de> (raw)
In-Reply-To: <4B98AA89.4060609@linux.intel.com>
On Thursday 11 March 2010 09:32:09 chen gong wrote:
> On 2010-3-11 16:07, ykzhao wrote:
...
> BTW, how about using UDEV rules to do this operation. It looks more smooth. I know some
> Novell guy is working on it.
I also know this guy :)
These would be the udev rules to automatically add memory/cpus:
SUBSYSTEM=="cpu", ACTION=="add", TEST=="online", ATTR{online}=="0", ATTR{online}="1", RUN+="/bin/logger onlining cpu: $env{DEVPATH}"
SUBSYSTEM=="memory", ACTION=="add", TEST=="state", ATTR{state}=="offline", ATTR{state}="online", RUN+="/bin/logger onlining memory: $env{DEVPATH}"
But this should be the same as you suggest (at least the memory rule)
to do in the kernel:
automatically online the memory, once hotadded.
I would not add any udev rules before this does not work
reliably and currently it is totally broken, mainly because:
- not being able to alloc memory on foreign nodes (at least with slab)
- C-state, throttling and cpufreq set up is done without valid
cpu_data(new_cpu) resulting in wrong C-state (and other) info
Thomas
next prev parent reply other threads:[~2010-03-12 13:18 UTC|newest]
Thread overview: 23+ 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
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 [this message]
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: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=201003121418.14204.trenn@suse.de \
--to=trenn@suse.de \
--cc=gong.chen@linux.intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=prarit@redhat.com \
--cc=trenn@novell.com \
--cc=yakui.zhao@intel.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).