WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for 64-bit Xen support
From: "Yinghai Lu" <yhlu.kernel@xxxxxxxxx>
Date: Thu, 3 Jul 2008 12:19:53 -0700
Cc: Nick Piggin <npiggin@xxxxxxx>, Mark McLoughlin <markmc@xxxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Eduardo Habkost <ehabkost@xxxxxxxxxx>, Vegard Nossum <vegard.nossum@xxxxxxxxx>, Stephen Tweedie <sct@xxxxxxxxxx>, x86@xxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>
Delivery-date: Thu, 03 Jul 2008 12:20:14 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=BBs3l/QFiTTJGFapNmDkqQog/Wo6jRnhWCY6Nb+NE8I=; b=kyIca0O5PxxIcmMaSAgainMqFarMxep68HozNUM0kP+gI5zrG19crrB69Ta4We015I VBaxCulAYr1JRipQRs27NtXpO7KvB8ExwmqsxWQJir+o4kSrsnakcwM+L93ilzcPMgbk TsuGfmxV/FU+L5lDfeaGw5NVp6Xk7dJrIMSb8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=bVo0RmvFKt7IzeU9J9YGGmwKz/V0XQT0ggJRtuecny0jVFAapfrosQtafkRkyqq+9l Vx2vZA8ML/+Q/wAGpbJzaEOGvidHjTz82qxLUod4bynk0jmS7PXPJ5Y9fCLrPpN0JZXX 9HW/GNmq7naj7uKjuii0lybRHsV732vMlGwMM=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <86802c440807031151o577d001g3e72bae3aa88df25@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <486539A3.3030102@xxxxxxxx> <20080701092152.GA18918@xxxxxxx> <486A57C8.3010008@xxxxxxxx> <20080701203123.GG4896@xxxxxxx> <20080703091053.GA1883@xxxxxxx> <86802c440807031120o6e87459em8c4f239eb1a2507c@xxxxxxxxxxxxxx> <486D19B1.1080402@xxxxxxxx> <86802c440807031130keada2fbva256f2efe3c4801@xxxxxxxxxxxxxx> <486D1D40.9050309@xxxxxxxx> <86802c440807031151o577d001g3e72bae3aa88df25@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, Jul 3, 2008 at 11:51 AM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
> On Thu, Jul 3, 2008 at 11:41 AM, Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
..
>> I modified the vmemmap code so it would create 4k mappings if PSE isn't
>> supported.  Did I get it wrong?  It should have no effect when PSE is
>> available (which is any time you're not running under Xen).
>>
>
> it could be address continuous checkup for printout in
> vmemmap_populated has some problem...

you moved p_end = p + PMD_SIZE before...

if (p_end != p || node_start != node) {

YH

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel