On Fri, Jun 27, 2014 at 4:58 PM, H. Peter Anvin wrote:
> On 06/10/2014 10:04 PM, Yinghai Lu wrote:
>> When using kexec with 64bit kernel, bzImage and ramdisk could be
>> loaded above 4G. We need this to get correct ramdisk adress.
>>
>> Make get_ramdisk_image() global and use it for early
On Fri, Jun 27, 2014 at 4:58 PM, H. Peter Anvin h...@zytor.com wrote:
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
> When using kexec with 64bit kernel, bzImage and ramdisk could be
> loaded above 4G. We need this to get correct ramdisk adress.
>
> Make get_ramdisk_image() global and use it for early microcode updating.
> Also make it to take boot_params pointer for
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early microcode updating.
Also make it to take boot_params pointer for
On Wed, Jun 11, 2014 at 10:34 AM, Yinghai Lu wrote:
> On Wed, Jun 11, 2014 at 10:32 AM, H. Peter Anvin wrote:
>>
>> It is not about loading over 4G, it is that some kinds of code (in
>> particular accessing global variables) from the early microcode loading
>> code doesn't work on 32 bits, so it
On Wed, Jun 11, 2014 at 10:34 AM, Yinghai Lu ying...@kernel.org wrote:
On Wed, Jun 11, 2014 at 10:32 AM, H. Peter Anvin h...@zytor.com wrote:
It is not about loading over 4G, it is that some kinds of code (in
particular accessing global variables) from the early microcode loading
code doesn't
On Wed, Jun 11, 2014 at 10:32 AM, H. Peter Anvin wrote:
>
> It is not about loading over 4G, it is that some kinds of code (in
> particular accessing global variables) from the early microcode loading
> code doesn't work on 32 bits, so it needs to be tested.
Ok, will test 32bit path.
Thanks
On 06/11/2014 10:30 AM, Yinghai Lu wrote:
> On Tue, Jun 10, 2014 at 11:08 PM, H. Peter Anvin wrote:
>> On 06/10/2014 10:04 PM, Yinghai Lu wrote:
>>> When using kexec with 64bit kernel, bzImage and ramdisk could be
>>> loaded above 4G. We need this to get correct ramdisk adress.
>>>
>>> Make
On Tue, Jun 10, 2014 at 11:08 PM, H. Peter Anvin wrote:
> On 06/10/2014 10:04 PM, Yinghai Lu wrote:
>> When using kexec with 64bit kernel, bzImage and ramdisk could be
>> loaded above 4G. We need this to get correct ramdisk adress.
>>
>> Make get_ramdisk_image() global and use it for early
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
> When using kexec with 64bit kernel, bzImage and ramdisk could be
> loaded above 4G. We need this to get correct ramdisk adress.
>
> Make get_ramdisk_image() global and use it for early microcode
> updating. Also make it to take boot_params pointer for
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early microcode
updating. Also make it to take boot_params pointer for
On Tue, Jun 10, 2014 at 11:08 PM, H. Peter Anvin h...@zytor.com wrote:
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early
On 06/11/2014 10:30 AM, Yinghai Lu wrote:
On Tue, Jun 10, 2014 at 11:08 PM, H. Peter Anvin h...@zytor.com wrote:
On 06/10/2014 10:04 PM, Yinghai Lu wrote:
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make
On Wed, Jun 11, 2014 at 10:32 AM, H. Peter Anvin h...@zytor.com wrote:
It is not about loading over 4G, it is that some kinds of code (in
particular accessing global variables) from the early microcode loading
code doesn't work on 32 bits, so it needs to be tested.
Ok, will test 32bit path.
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early microcode updating.
Also make it to take boot_params pointer for different usage.
Signed-off-by: Yinghai Lu
---
When using kexec with 64bit kernel, bzImage and ramdisk could be
loaded above 4G. We need this to get correct ramdisk adress.
Make get_ramdisk_image() global and use it for early microcode updating.
Also make it to take boot_params pointer for different usage.
Signed-off-by: Yinghai Lu
16 matches
Mail list logo