From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: ian.campbell@citrix.com, akpm@linux-foundation.org,
andi.kleen@intel.com, haicheng.li@linux.intel.com,
fengguang.wu@intel.com, jeremy@goop.org, konrad.wilk@oracle.com,
dan.magenheimer@oracle.com, v.tolstov@selfip.ru, pasik@iki.fi,
wdauchy@gmail.com, rientjes@google.com,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH R4 7/7] xen/balloon: Memory hotplug support for Xen balloon driver
Date: Tue, 08 Mar 2011 16:02:19 -0800 [thread overview]
Message-ID: <1299628939.9014.3499.camel@nimitz> (raw)
In-Reply-To: <20110308215049.GH27331@router-fw-old.local.net-space.pl>
On Tue, 2011-03-08 at 22:50 +0100, Daniel Kiper wrote:
> +static enum bp_state reserve_additional_memory(long credit)
> +{
> + int rc;
> + unsigned long balloon_hotplug = credit;
> +
> + balloon_hotplug <<= PAGE_SHIFT;
> +
> + rc = add_virtual_memory((u64 *)&balloon_hotplug);
This would work if all 'unsigned long's were 64-bits. It'll break on
32-bit kernels in a very bad way by overwriting 4 bytes of stack.
> + if (rc) {
> + pr_info("xen_balloon: %s: add_virtual_memory() failed: %i\n", __func__, rc);
> + return BP_EAGAIN;
> + }
> +
> + balloon_hotplug >>= PAGE_SHIFT;
> +
> + balloon_hotplug -= credit;
> +
> + balloon_stats.hotplug_pages += credit;
> + balloon_stats.balloon_hotplug = balloon_hotplug;
> +
> + return BP_DONE;
> +}
> +
> +static int xen_online_page_notifier(struct notifier_block *nb, unsigned long val, void *v)
> +{
> + struct page *page = v;
> + unsigned long pfn = page_to_pfn(page);
> +
> + if (pfn >= num_physpages)
> + num_physpages = pfn + 1;
> +
> + inc_totalhigh_pages();
> +
> +#ifdef CONFIG_FLATMEM
> + max_mapnr = max(pfn, max_mapnr);
> +#endif
I really don't like that this is a direct copy of online_page() up to
this point. They're already subtly different. I'm also curious if this
breaks on 32-bit kernels because of the unconditional
inc_totalhigh_pages().
If it's done this way, I'd almost guarantee that the first time someone
fixes a bug or adds a generic feature in online_page() that Xen gets
missed.
> + mutex_lock(&balloon_mutex);
> +
> + __balloon_append(page);
> +
> + if (balloon_stats.hotplug_pages)
> + --balloon_stats.hotplug_pages;
> + else
> + --balloon_stats.balloon_hotplug;
> +
> + mutex_unlock(&balloon_mutex);
> +
> + return NOTIFY_STOP;
> +}
I'm not a _huge_ fan of these notifier chains, but I guess it works.
However, if you're going to use these notifier chains, then we probably
should use them to full effect. Have a notifier list like this:
1. generic online_page()
2. xen_online_page_notifier() (returns NOTIFY_STOP)
3. free_online_page()
Where finish_online_page() does something like this:
finish_online_page(...)
{
ClearPageReserved(page);
init_page_count(page);
__free_page(page);
}
These patches are definitely getting there. Just another round or two,
and they should be ready to go.
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-03-09 0:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:50 [PATCH R4 7/7] xen/balloon: Memory hotplug support for Xen balloon driver Daniel Kiper
2011-03-09 0:02 ` Dave Hansen [this message]
2011-03-10 9:02 ` Daniel Kiper
2011-03-10 14:59 ` Dave Hansen
2011-03-09 20:14 ` [Xen-devel] " Konrad Rzeszutek Wilk
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=1299628939.9014.3499.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=dan.magenheimer@oracle.com \
--cc=dkiper@net-space.pl \
--cc=fengguang.wu@intel.com \
--cc=haicheng.li@linux.intel.com \
--cc=ian.campbell@citrix.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasik@iki.fi \
--cc=rientjes@google.com \
--cc=v.tolstov@selfip.ru \
--cc=wdauchy@gmail.com \
--cc=xen-devel@lists.xensource.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).