On Wed, Dec 12, 2012 at 8:23 PM, H. Peter Anvin wrote:
> I still want to do what I mentioned before, because we need to not rely on
> the initialized/16-bit portion so much:
>
> 1. add a field in the uninitialized portion, call it "sentinel";
> 2. make sure the byte position corresponding to the "
On 12/12/2012 06:49 PM, Yinghai Lu wrote:
Hi, Peter,
What's your decision about this?
Do you mean have one boot_params mask in initdata and AND that with
boot_params from bootloader
to clean not used bytes?
So later will not need to check
if (boot_params.hdr.xloadflags & USE_EXT_BOOT_PAR
On Thu, Dec 6, 2012 at 10:57 PM, Yinghai Lu wrote:
> On Wed, Dec 5, 2012 at 7:12 PM, Yinghai Lu wrote:
>> On Wed, Dec 5, 2012 at 5:57 PM, H. Peter Anvin wrote:
>>> Hi Eric,
>>>
>>> Could you give a list of struct boot_params field which are initialized
>>> properly by kexec? I think we need to
On Wed, Dec 5, 2012 at 7:12 PM, Yinghai Lu wrote:
> On Wed, Dec 5, 2012 at 5:57 PM, H. Peter Anvin wrote:
>> Hi Eric,
>>
>> Could you give a list of struct boot_params field which are initialized
>> properly by kexec? I think we need to do the sentinel hack, and want to
>> know what to whitelist
On Wed, Dec 5, 2012 at 5:57 PM, H. Peter Anvin wrote:
> Hi Eric,
>
> Could you give a list of struct boot_params field which are initialized
> properly by kexec? I think we need to do the sentinel hack, and want to
> know what to whitelist.
the one with *
? means set only when lfb_depth > 8
also
Hi Eric,
Could you give a list of struct boot_params field which are initialized
properly by kexec? I think we need to do the sentinel hack, and want to
know what to whitelist.
Also, does kexec set a bootloader ID?
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-
6 matches
Mail list logo
