On 8/10/2017 9:46 AM, Ingo Molnar wrote:
>
> * Matt Fleming wrote:
>
>> On Wed, 02 Aug, at 11:41:38AM, Stuart Hayes wrote:
>>> (Resend because I mistyped the maintainer's email address the first time.)
>>>
>>> The kernel's EFI stub locates and copies EFI ROM images into memory,
>>> which it allo
* Matt Fleming wrote:
> On Wed, 02 Aug, at 11:41:38AM, Stuart Hayes wrote:
> > (Resend because I mistyped the maintainer's email address the first time.)
> >
> > The kernel's EFI stub locates and copies EFI ROM images into memory,
> > which it allocates using the byte-granular EFI allocate_pool
On Wed, 02 Aug, at 11:41:38AM, Stuart Hayes wrote:
> (Resend because I mistyped the maintainer's email address the first time.)
>
> The kernel's EFI stub locates and copies EFI ROM images into memory,
> which it allocates using the byte-granular EFI allocate_pool
> function. These memory ranges a
(Resend because I mistyped the maintainer's email address the first time.)
The kernel's EFI stub locates and copies EFI ROM images into memory, which it
allocates using the byte-granular EFI allocate_pool function. These memory
ranges are then added to setup_data, and later to e820 (in
e820__r
The kernel's EFI stub locates and copies EFI ROM images into memory, which it
allocates using the byte-granular EFI allocate_pool function. These memory
ranges are then added to setup_data, and later to e820 (in
e820__reserve_setup_data()). The e820 ranges are parsed to create nosave
regions
5 matches
Mail list logo