From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-acpi@vger.kernel.org, intel-linux-acpi@linux.intel.com,
kamezawa.hiroyu@jp.fujitsu.com, "Yu,
Luming" <luming.yu@intel.com>,
Kristen Accardi <kristen.c.accardi@intel.com>
Subject: Re: [PATCH] acpi_memoryhotplug.c needs not to walk whole namespace twice to register notify handler
Date: Fri, 24 Feb 2006 14:31:04 +0900 [thread overview]
Message-ID: <20060224122247.B225.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <200602230625.58671.trenn@suse.de>
Hello.
Thomas-san.
> > This is how it is currently done in memhotplug:
> > Driver_register is invoked. There the HID is searched and device pointer passed
> > if a memory hotplug device is found.
> > Then a second search for the same HID (by walk_namespace) is done in memhotplug
> > and the notify handler is registered for those.
I'd misunderstood for long time. Indeed, I agree it was redundant.
I tested your patch on Tiger4 with memory hotplug emulation.
It works well. ;-) Thanks.
> > BTW: How is this memory hotplugging supposed to work. It only reacts on ACPI notifies, my machine
> > only has "Check" notify events for mem. What kind of hardware do I need to test this and
> > how will the eject request be initiated?
I don't have any real machine yet. Now, our firmware team is making
effort to develop it for our new box.
But, Intel might have real box which can use memory hotplug....
Bye.
--
Yasunori Goto
prev parent reply other threads:[~2006-02-24 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 0:03 [PATCH] acpi_memoryhotplug.c needs not to walk whole namespace twice to register notify handler Thomas Renninger
2006-02-23 5:25 ` Thomas Renninger
2006-02-24 5:31 ` Yasunori Goto [this message]
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=20060224122247.B225.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=intel-linux-acpi@linux.intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=luming.yu@intel.com \
--cc=trenn@suse.de \
/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