[Xen-devel] Re: [PATCH] e820: fix clip_to_limit()

[Keir Fraser <keir.fraser@xxxxxxxxxxxxx>]

On 10/11/2009 08:19, "Xiao Guangrong" <xiaoguangrong@xxxxxxxxxxxxxx> wrote:

>> Firstly, your 'break' was not inside that if-else block; it was right at the
>> end of the for loop. Secondly, just because we found one RAM region entirely
>> beyond the end of the clip boundary, does not mean there isn't another. We
>> can't just bail -- we have to iterate all the way to the end of the e820
>> map.
>> 
> 
> I think that sanitize_e820_map() can sort e820 items from low address
> to high address, so, if we meet one e820 item beyond the end of the clip
> boundary, subsequent items also beyond it.
> 
> Maybe I misunderstand sanitize_e820_map()? I'll reread it :-)

No, you understand it. And if we meet one e820 item beyond the end of the
clip boundary, all subsequent items are also beyond it. But that doesn't
mean we shouldn't handle them -- in fact we must handle them, as one of them
could be E820_RAM. Right?

 -- Keir



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