>>> On 28.09.16 at 11:56, wrote:
> On Wed, Sep 28, 2016 at 03:06:31AM -0600, Jan Beulich wrote:
>> >>> On 27.09.16 at 21:55, wrote:
>> > On Mon, Sep 26, 2016 at 09:03:30AM -0600, Jan Beulich wrote:
>> >> >>> On 23.09.16 at 23:47, wrote:
>> >> > +1: mov %eax,sym_fs(l2_bootmap)-8(%ebx,%ec
On Wed, Sep 28, 2016 at 03:06:31AM -0600, Jan Beulich wrote:
> >>> On 27.09.16 at 21:55, wrote:
> > On Mon, Sep 26, 2016 at 09:03:30AM -0600, Jan Beulich wrote:
> >> >>> On 23.09.16 at 23:47, wrote:
> >> > @@ -426,32 +453,65 @@ trampoline_bios_setup:
> >> > xor %cl, %cl
> >> >
> >> >
>>> On 27.09.16 at 21:55, wrote:
> On Mon, Sep 26, 2016 at 09:03:30AM -0600, Jan Beulich wrote:
>> >>> On 23.09.16 at 23:47, wrote:
>> > @@ -426,32 +453,65 @@ trampoline_bios_setup:
>> > xor %cl, %cl
>> >
>> > trampoline_setup:
>> > +/*
>> > + * Called on legacy BIOS
On Mon, Sep 26, 2016 at 09:03:30AM -0600, Jan Beulich wrote:
> >>> On 23.09.16 at 23:47, wrote:
> > @@ -426,32 +453,65 @@ trampoline_bios_setup:
> > xor %cl, %cl
> >
> > trampoline_setup:
> > +/*
> > + * Called on legacy BIOS and EFI platforms.
> > + *
> > +
>>> On 23.09.16 at 23:47, wrote:
> @@ -426,32 +453,65 @@ trampoline_bios_setup:
> xor %cl, %cl
>
> trampoline_setup:
> +/*
> + * Called on legacy BIOS and EFI platforms.
> + *
> + * Initialize 0-15 bits of BOOT_FS segment descriptor base address.
> +
Every multiboot protocol (regardless of version) compatible image must
specify its load address (in ELF or multiboot header). Multiboot protocol
compatible loader have to load image at specified address. However, there
is no guarantee that the requested memory region (in case of Xen it starts
at 2
