From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756582Ab3APRiu (ORCPT ); Wed, 16 Jan 2013 12:38:50 -0500 Received: from terminus.zytor.com ([198.137.202.10]:54265 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754929Ab3APRit (ORCPT ); Wed, 16 Jan 2013 12:38:49 -0500 Message-ID: <50F6E582.60905@zytor.com> Date: Wed, 16 Jan 2013 09:38:10 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Yinghai Lu CC: Stefano Stabellini , Thomas Gleixner , Ingo Molnar , "Eric W. Biederman" , Andrew Morton , Borislav Petkov , Jan Kiszka , Jason Wessel , "linux-kernel@vger.kernel.org" , Konrad Rzeszutek Wilk Subject: Re: [PATCH v7u1 00/31] x86, boot, 64bit: Add support for loading ramdisk and bzImage above 4G References: <1357260531-11115-1-git-send-email-yinghai@kernel.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/16/2013 09:31 AM, Yinghai Lu wrote: > > rom af4f3bc044d1556f89bd488c7ea75e2a162bb273 Mon Sep 17 00:00:00 2001 > From: Yinghai Lu > Date: Mon, 14 Jan 2013 21:11:05 -0800 > Subject: [PATCH] x86, mm: Fix page table early allocation offset checking > > During debugging loading kernel above 4G, found that one page is not used > in pre-allocated BRK area for early page allocation. > > pgt_buf_top is address that can not be used, so should check if that new > end is above that top, otherwise last page will not be used. > The first sentence here doesn't parse, and this description doesn't give any hint to anyone who is researching this code in say, five years, what problems this caused. I can't really figure it out, either; from looking at the thread and the patch I'm assuming the problem is somehow that the code failed to use the last page in the brk buffer, which somehow lead to a Xen boot failure... but the bits from here to there are totally unclear. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.