From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
Jan Beulich <jbeulich@novell.com>,
Tim Deegan <Tim.Deegan@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 2/6] Change the boot allocator function to support memory add
Date: Sun, 28 Jun 2009 10:50:24 +0100 [thread overview]
Message-ID: <C66CFB70.E563%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CCF824CF@PDSMSX501.ccr.corp.intel.com>
On 28/06/2009 10:27, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
> This patch extend the boot allocator to support memory add.
>
> We take different method for boot allocator bitmap for 32/64 system. In x32 ,
> we allocate 512K bitmap to support the whole 16G memory. In x86_64, we don't
> change the allocation when system bootup, instead, we try to remap the
> allocator bitmap to some pre-defined virtual address if hot-add happen.
>
> We also add several API to allocate the handle boot page from some range.
The undelrying implementation ideas may be okay, but calling these
extensions to the 'boot allocator' makes no sense. The boot allocator only
exists during boot. The fact that the bitmap it uses persists beyond boot is
an implementation detail. Perhaps you just need to change the name of your
new allocator interface functions to something more suitable.
-- Keir
next prev parent reply other threads:[~2009-06-28 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 9:27 [PATCH 2/6] Change the boot allocator function to support memory add Jiang, Yunhong
2009-06-28 9:50 ` Keir Fraser [this message]
2009-06-28 13:24 ` Jiang, Yunhong
2009-06-28 13:43 ` Keir Fraser
2009-06-28 13:59 ` Jiang, Yunhong
2009-06-28 15:38 ` Keir Fraser
2009-06-29 2:04 ` Jiang, Yunhong
2009-06-29 7:34 ` Keir Fraser
2009-06-29 7:45 ` Jiang, Yunhong
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=C66CFB70.E563%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.