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 16:38:21 +0100 [thread overview]
Message-ID: <C66D4CFD.E5A7%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <E2263E4A5B2284449EEBD0AAB751098402CCF824F8@PDSMSX501.ccr.corp.intel.com>
On 28/06/2009 14:59, "Jiang, Yunhong" <yunhong.jiang@intel.com> wrote:
>> I think the PGC_ flags could be extended to do this, yes.
>> Maybe I will look
>> into that.
>
> Thanks. We try to do this way in the beginning , but in the end gives up
> because currently too many direct operation to count_info without any macro
> wrapper, and I'm not confident to take over ALL of them.
This should already have been dealt with when PGC_offlining/broken/offlined
were added. Thus I think it should be straightforward to make the change.
Also this flag would only be set for pages which belong to the page
allocator. Noone else would ever set the flag since they do not own the bit.
So I think the patch is straightforward to construct.
Actually it'd be nice to get rid of the allocator bitmap altogether, since
hardly anyone uses it. That will just require some care in bringing up the
frametable and its mappings, which the main allocator is dependent on.
-- Keir
next prev parent reply other threads:[~2009-06-28 15:38 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
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 [this message]
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=C66D4CFD.E5A7%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.