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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] cleanup for __start_xen()

To: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Xiao Guangrong <xiaoguangrong@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] cleanup for __start_xen()
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 01 Dec 2009 12:07:57 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Delivery-date: Tue, 01 Dec 2009 04:08:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091201094217.GI14284@xxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpyapQ754hm51KxQbeKLo4PThFrkgAFFbpG
Thread-topic: [Xen-devel] [PATCH] cleanup for __start_xen()
User-agent: Microsoft-Entourage/
On 01/12/2009 09:42, "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx> wrote:

> At 01:16 +0000 on 01 Dec (1259630197), Xiao Guangrong wrote:
>> e is moved in [e-(modules_length+modules_headroom), e] range,
>> so, s is not overrun e too...
> OK, but:
>  - this is not obvious (hence this thread);
>  - even Keir makes mistakes here from time to time; and
>  - it's a single test on code that runs at start of day
> so maybe we should just leave it as it was?

I'll put it back and fix my other pre-existing mistake also.

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>