From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: "Tolentino,
Matthew E"
<matthew.e.tolentino-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"S,
Naveen B" <naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: ACPI memory hotplug driver
Date: 17 Feb 2005 02:45:00 -0500 [thread overview]
Message-ID: <1108626299.2096.491.camel@d845pe> (raw)
In-Reply-To: <D36CE1FCEFD3524B81CA12C6FE5BCAB008D17348-oCDej+MBycNZtRGVdHMbwrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
applied to acpi-test.
thanks,
-Len
On Mon, 2005-01-17 at 17:07, Tolentino, Matthew E wrote:
> This is a reposting of the ACPI memory hotplug driver posted by
> Naveen a couple of months back. This has been maintained in the
> memory hotplug tree since then and unless there's additional
> feedback resultant to this post, we're resubmitting it for
> upstream inclusion. Patch is against 2.6.11-rc1.
>
> I also elaborated a bit in the Kconfig help section based on
> Grant's post on the container driver over the weekend... ;-)
>
> matt
>
> Below description also included at the top of the attached patch:
>
> The ACPI based memory hot plug driver patch supports physical hotplug
> operations on memory. This driver fields notifications for memory add
> and remove operations from firmware and notifies the VM of the affected
> memory ranges. Accordingly, this driver also maintains and updates the
> states of all the memory ranges. This driver is useful on hardware which
> helps firmware generating ACPI events for every physical hotplug
> operation of memory boards on the system during runtime.
>
> Signed-off-by: Matt Tolentino <matthew.e.tolentino-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Naveen B S <naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Signed-off-by: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
prev parent reply other threads:[~2005-02-17 7:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 22:07 ACPI memory hotplug driver Tolentino, Matthew E
[not found] ` <D36CE1FCEFD3524B81CA12C6FE5BCAB008D17348-oCDej+MBycNZtRGVdHMbwrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2005-02-17 7:45 ` Len Brown [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=1108626299.2096.491.camel@d845pe \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=matthew.e.tolentino-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=naveen.b.s-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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