Re: Extending boot protocol & bzImage for paravirt_ops

Jeremy Fitzhardinge <[email protected]> writes:

> H. Peter Anvin wrote:
>> It would have to, because of the way code32_start is defined to work.
>> We don't get control again after its use as a hook.
>>   
>
> Who uses that hook?  The impression I get is that the execution
> environment for jumping to that pointer is not very well defined at present.

loadlin.

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

---

• References:
  • Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: [email protected] (Eric W. Biederman)
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: "H. Peter Anvin" <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: "H. Peter Anvin" <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: "H. Peter Anvin" <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: "H. Peter Anvin" <[email protected]>
  • Re: Extending boot protocol & bzImage for paravirt_ops
    • From: Jeremy Fitzhardinge <[email protected]>

• Prev by Date: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately?
• Next by Date: Re: [RFC] [PATCH] cpuset operations causes Badness at mm/slab.c:777 warning
• Previous by thread: Re: Extending boot protocol & bzImage for paravirt_ops
• Next by thread: Reg: redundancy in inet socket
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]