From: Paul Mackerras <paulus@samba.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
linuxppc-dev@ozlabs.org, anton@au1.ibm.com
Subject: Re: [RFC][PATCH] remove section mappinng
Date: Thu, 7 Feb 2008 11:09:43 +1100 [thread overview]
Message-ID: <18346.19527.92063.259932@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <1201558765.29357.1.camel@dyn9047017100.beaverton.ibm.com>
Badari Pulavarty writes:
> Thank you for your input and suggestions. Does this look reasonable
> to you ?
>
> Thanks,
> Badari
>
> For memory remove, we need to clean up htab mappings for the
> section of the memory we are removing.
>
> This patch implements support for removing htab bolted mappings
> for ppc64 lpar. Other sub-archs, may need to implement similar
> functionality for the hotplug memory remove to work.
Looks OK to me.
Paul.
prev parent reply other threads:[~2008-02-07 0:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 16:05 [RFC][PATCH] remove section mappinng Badari Pulavarty
2008-01-26 1:24 ` Paul Mackerras
2008-01-28 22:19 ` Badari Pulavarty
2008-02-07 0:09 ` Paul Mackerras [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=18346.19527.92063.259932@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=anton@au1.ibm.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pbadari@us.ibm.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).