On 29 January 2018 at 10:51, Ard Biesheuvel wrote:
> On 26 January 2018 at 21:16, Matt Fleming wrote:
>> On Thu, 18 Jan, at 01:01:04PM, Sai Praneeth Prakhya wrote:
>>> From: Sai Praneeth
>>>
>>> Presently, in x86, to invoke any efi function like
>>> efi_set_virtual_address_map() or any efi_runti
On 26 January 2018 at 21:16, Matt Fleming wrote:
> On Thu, 18 Jan, at 01:01:04PM, Sai Praneeth Prakhya wrote:
>> From: Sai Praneeth
>>
>> Presently, in x86, to invoke any efi function like
>> efi_set_virtual_address_map() or any efi_runtime_service() the code path
>> typically involves read_cr3()
On Thu, 18 Jan, at 01:01:04PM, Sai Praneeth Prakhya wrote:
> From: Sai Praneeth
>
> Presently, in x86, to invoke any efi function like
> efi_set_virtual_address_map() or any efi_runtime_service() the code path
> typically involves read_cr3() (save previous pgd), write_cr3()
> (write efi_pgd) and
From: Sai Praneeth
Presently, in x86, to invoke any efi function like
efi_set_virtual_address_map() or any efi_runtime_service() the code path
typically involves read_cr3() (save previous pgd), write_cr3()
(write efi_pgd) and calling efi function. Likewise after returning from
efi function the co
4 matches
Mail list logo