From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Yasunori Goto <y-goto@jp.fujitsu.com>,
ACPI-ML <linux-acpi@vger.kernel.org>,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
"Brown, Len" <len.brown@intel.com>
Subject: [PATCH: 000/002] Catch notification of memory add event of ACPI via container driver.
Date: Thu, 23 Mar 2006 22:41:05 +0900 [thread overview]
Message-ID: <20060323221810.8A0B.Y-GOTO@jp.fujitsu.com> (raw)
Hi.
These 2 patches are to catch notification of new node's hot-add event via ACPI.
They were members of v4 of new node hot-add patches.
However, I would like to merge them at first before other patch.
Because, if these 2 patches are merged into mainline, all new node's memory
can be added to node 0. If not, no memory is added even if other patches are
merged. In addition, there is no opposition to these patches.
To tell the truth, I've posted similer patches a few times to ACPI-ML.
But, unfortunately, there was no response.
So, could you apply these patches to -mm tree?
This patch is for 2.6.16-mm1.
I tested on my ia64 Tiger4 box with my node emulation.
In addition, our firmware team provided us new firmware which can allow hot-add.
These patches worked well on it. :-)
Bye.
------------------------------------------
These 2 patches are to catch notification of new node's hot-add event
via ACPI.
If a new node is added, notification of ACPI reaches container device
which means node, and container driver scans belonging devices.
To call memory device's driver, start function of acpi memory device is
necessary. First patch is to register its function.
In addition, the scanning of memory devices and call add_memory() works
even if memory is registered at boottime.
Second patch is to avoid redundant call of add_memory().
--
Yasunori Goto
next reply other threads:[~2006-03-23 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 13:41 Yasunori Goto [this message]
2006-03-23 13:42 ` [PATCH: 001/002] Catch notification of memory add event of ACPI via container driver. (register start func for memory device) Yasunori Goto
2006-03-23 13:44 ` [PATCH: 002/002] Catch notification of memory add event of ACPI via container driver.(avoid redundant call add_memory) Yasunori Goto
2006-03-23 23:38 ` [PATCH: 000/002] Catch notification of memory add event of ACPI via container driver KAMEZAWA Hiroyuki
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=20060323221810.8A0B.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=akpm@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.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