From: Julien Grall <julien.grall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>
Cc: Keir Fraser <keir@xen.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Ian Campbell <Ian.Campbell@eu.citrix.com>
Subject: Re: [PATCH] x86/NUMA: make init_node_heap() respect Xen heap limit
Date: Thu, 3 Sep 2015 21:58:02 +0100 [thread overview]
Message-ID: <55E8B45A.2040909@citrix.com> (raw)
In-Reply-To: <55E8A716.3080109@citrix.com>
On 03/09/2015 21:01, Julien Grall wrote:
> Hi Jan,
>
> On 27/08/2015 09:37, Jan Beulich wrote:
>> On NUMA systems, where we try to use node local memory for the basic
>> control structures of the buddy allocator, this special case needs to
>> take into consideration a possible address width limit placed on the
>> Xen heap. In turn this (but also other, more abstract considerations)
>> requires that xenheap_max_mfn() not be called more than once (at most
>> we might permit it to be called a second time with a larger value than
>> was passed the first time), and be called only before calling
>> end_boot_allocator().
>>
>> While inspecting all the involved code, a couple of off-by-one issues
>> were found (and are being corrected here at once):
>> - arch_init_memory() cleared one too many page table slots
>> - the highmem_start based invocation of xenheap_max_mfn() passed too
>> big a value
>> - xenheap_max_mfn() calculated the wrong bit count in edge cases
>>
>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> This patch is breaking boot on aarch64 platform (particularly X-gene).
>
> I think this should be considered as a block until I find a way to
> fix it.
And found why! The last xenheap_bits changed from 39 to 38.
On x-gene the last max mfn used for the xenheap is 0x4400000, which the
new computation, it will give 38 bits which doesn't cover the entire
xenheap range.
I have wrote a patch to fix the issue, but I'm not sure that it's
the right things to do (see below).
Regards,
commit d1f2e47326da87c55f3165156407f224d684bccd
Author: Julien Grall <julien.grall@citrix.com>
Date: Thu Sep 3 21:49:31 2015 +0100
xen: pagealloc: Correctly calculate the number of xenheap bits
The commit 88e3ed61642bb393458acc7a9bd2f96edc337190 "x86/NUMA: make
init_node_heap() respect Xen heap limit" breaks boot on the arm64 board
X-Gene.
This is because the last xen heaf MFN is 0x4400000. Which the new way to
calculate the number bits, the result would 38 bits which doesn't cover
all the xenheap. Fix it by dropping the -1 in the expression.
Signed-off-by: Julien Grall <julien.grall@citrix.com>
diff --git a/xen/common/page_alloc.c b/xen/common/page_alloc.c
index 74fc1de..24fb09c 100644
--- a/xen/common/page_alloc.c
+++ b/xen/common/page_alloc.c
@@ -1558,7 +1558,7 @@ void __init xenheap_max_mfn(unsigned long mfn)
ASSERT(!first_node_initialised);
ASSERT(!xenheap_bits);
BUILD_BUG_ON(PADDR_BITS >= BITS_PER_LONG);
- xenheap_bits = min(flsl(mfn + 1) - 1 + PAGE_SHIFT, PADDR_BITS);
+ xenheap_bits = min(flsl(mfn + 1) + PAGE_SHIFT, PADDR_BITS);
printk(XENLOG_INFO "Xen heap: %u bits\n", xenheap_bits);
}
--
Julien Grall
next prev parent reply other threads:[~2015-09-03 21:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:37 [PATCH] x86/NUMA: make init_node_heap() respect Xen heap limit Jan Beulich
2015-08-27 9:25 ` Wei Liu
2015-08-27 10:11 ` Andrew Cooper
2015-08-27 14:43 ` Wei Liu
2015-09-01 10:28 ` Ian Campbell
2015-09-03 20:01 ` Julien Grall
2015-09-03 20:58 ` Julien Grall [this message]
2015-09-04 7:37 ` Jan Beulich
2015-09-04 8:27 ` Ian Campbell
2015-09-04 8:39 ` Jan Beulich
2015-09-04 8:52 ` Ian Campbell
2015-09-04 9:09 ` Jan Beulich
2015-09-04 11:29 ` Julien Grall
2015-09-04 12:02 ` Jan Beulich
2015-09-04 12:05 ` Wei Liu
2015-09-04 12:50 ` Julien Grall
2015-09-04 12:57 ` Ian Campbell
2015-09-04 12:52 ` Ian Campbell
2015-09-04 12:53 ` Julien Grall
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=55E8B45A.2040909@citrix.com \
--to=julien.grall@citrix.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.