lkml.org 
[lkml]   [2007]   [Jun]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Extending boot protocol & bzImage for paravirt_ops
Jeremy Fitzhardinge wrote:
>
> Well, I think we can safely say that its something that's only
> meaningful in 32/64-bit mode, so we aren't constrained by the real-mode
> address space.
>
> One of my goals in this project is to make the boot image, in some way,
> completely define which memory it needs it get started. That means that
> the boot loader can either place things knowing they'll avoid the boot
> image and/or definitively know that the image is unloadable.
>
> So I don't think its strictly necessary to pre-define what memory this
> object can use, since I think it can be safely determined dynamically.
>

That's a method of defining the memory space.

I think the current definition is suitable for entering at the 16-bit
entry point.

-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-02 02:45    [W:0.076 / U:0.876 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site