Re: [PATCH V4 0/3] Use mm_struct and switch_mm() instead of manually

2018-03-03 Thread Ard Biesheuvel
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

Re: [PATCH V4 0/3] Use mm_struct and switch_mm() instead of manually

2018-01-29 Thread Ard Biesheuvel
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()

Re: [PATCH V4 0/3] Use mm_struct and switch_mm() instead of manually

2018-01-26 Thread Matt Fleming
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

[PATCH V4 0/3] Use mm_struct and switch_mm() instead of manually

2018-01-18 Thread Sai Praneeth Prakhya
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