From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>
Cc: Tapasweni Pathak <tapaswenipathak@gmail.com>,
matt.fleming@intel.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH] efi: Clean up the efi_call_phys_[prolog|epilog]() save/restore interaction
Date: Tue, 10 Mar 2015 13:36:37 +0000 [thread overview]
Message-ID: <20150310133637.GC17573@codeblueprint.co.uk> (raw)
In-Reply-To: <20150303064850.GA30036@gmail.com>
On Tue, 03 Mar, at 07:48:50AM, Ingo Molnar wrote:
>
> Also clean up the save_pgd global variable while at it.
>
> untested as well.
>
> Thanks,
>
> Ingo
>
> ==============>
> From 166625ceaef68fcbeee63adc63c02d75abcaf0db Mon Sep 17 00:00:00 2001
> From: Ingo Molnar <mingo@kernel.org>
> Date: Tue, 3 Mar 2015 07:42:48 +0100
> Subject: [PATCH] efi: Clean up the efi_call_phys_[prolog|epilog]() save/restore interaction
>
> Currently x86-64 efi_call_phys_prolog() saves into a global variable (save_pgd),
> and efi_call_phys_epilog() restores the kernel pagetables from that global
> variable.
>
> Change this to a cleaner save/restore pattern where the saving function returns
> the saved object and the restore function restores that.
>
> Apply the same concept to the 32-bit code as well.
>
> Plus this approach, as an added bonus, allows us to express the
> !efi_enabled(EFI_OLD_MEMMAP) situation in a clean fashion as well,
> via a 'NULL' return value.
>
> Cc: Tapasweni Pathak <tapaswenipathak@gmail.com>
> Signed-off-by: Ingo Molnar <mingo@kernel.org>
> ---
> arch/x86/include/asm/efi.h | 6 ++++--
> arch/x86/platform/efi/efi.c | 5 +++--
> arch/x86/platform/efi/efi_32.c | 11 ++++++++---
> arch/x86/platform/efi/efi_64.c | 26 ++++++++++++++++----------
> 4 files changed, 31 insertions(+), 17 deletions(-)
Applied, thanks!
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-03-10 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 2:58 [PATCH] arch: x86: platform: efi: Disabling interrupt around kmalloc Tapasweni Pathak
2015-03-03 6:34 ` [PATCH] efi: Disable interrupts around EFI calls, not in the epilog/prolog calls Ingo Molnar
2015-03-03 6:48 ` [PATCH] efi: Clean up the efi_call_phys_[prolog|epilog]() save/restore interaction Ingo Molnar
2015-03-10 13:36 ` Matt Fleming [this message]
2015-03-10 13:36 ` [PATCH] efi: Disable interrupts around EFI calls, not in the epilog/prolog calls Matt Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150310133637.GC17573@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tapaswenipathak@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox