From: Alex Thorlton <athorlton@sgi.com>
To: linux-kernel@vger.kernel.org
Cc: Alex Thorlton <athorlton@sgi.com>,
Dimitri Sivanich <sivanich@sgi.com>, Russ Anderson <rja@sgi.com>,
Mike Travis <travis@sgi.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-efi@vger.kernel.org
Subject: [RFC PATCH 0/2] Fix EFI runtime calls on SGI UV
Date: Wed, 11 May 2016 14:55:43 -0500 [thread overview]
Message-ID: <1462996545-98387-1-git-send-email-athorlton@sgi.com> (raw)
These patches make the necessary changes to get SGI UVs working with the
latest EFI memory mapping code. The motivation behind the changes is
fairly simple:
Patch 1: The current efi_call_virt macro will not work with function
pointers that don't live in efi.systab->runtime
Patch 2: The efi_call assembly code incorrectly puts the return address
from the current stack frame into the space reserved for the
arguments in the stack frame that we're setting up for our EFI
runtime call, instead of the 7th argument to efi_call.
I'm pretty sure that the second patch should be fine in its current
state, but there will likely need to be some discussion about how to
properly handle the stuff I'm doing in the first patch. I know we need
to do something kind of like what I did, but I know my copied/pasted
UV-specific macros are not how we'll want to implement this in the end.
Please note that, as requested, these patches apply to the current
tip/master branch, but they will not apply out-of-the-box to
linus/master.
Let me know what everybody thinks!
Cc: Dimitri Sivanich <sivanich@sgi.com>
Cc: Russ Anderson <rja@sgi.com>
Cc: Mike Travis <travis@sgi.com>
Cc: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Borislav Petkov <bp@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Cc: linux-efi@vger.kernel.org
Alex Thorlton (2):
Create UV efi_call macros
Fix efi_call
arch/x86/include/asm/efi.h | 3 ++
arch/x86/platform/efi/efi_stub_64.S | 2 +-
arch/x86/platform/uv/bios_uv.c | 3 +-
drivers/firmware/efi/runtime-wrappers.c | 44 +-------------------------
include/linux/efi.h | 55 +++++++++++++++++++++++++++++++++
5 files changed, 61 insertions(+), 46 deletions(-)
--
1.8.5.6
next reply other threads:[~2016-05-11 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 19:55 Alex Thorlton [this message]
2016-05-11 19:55 ` [PATCH 1/2] Create UV efi_call macros Alex Thorlton
2016-05-12 6:46 ` Ingo Molnar
2016-05-12 7:35 ` Ard Biesheuvel
2016-05-12 8:17 ` Ingo Molnar
2016-05-16 23:00 ` Alex Thorlton
2016-05-12 12:06 ` Matt Fleming
2016-05-16 22:58 ` Alex Thorlton
2016-05-17 12:11 ` Matt Fleming
2016-05-17 20:14 ` Alex Thorlton
2016-05-11 19:55 ` [PATCH 2/2] Fix efi_call Alex Thorlton
2016-05-12 6:48 ` Ingo Molnar
2016-05-12 11:43 ` Matt Fleming
2016-05-16 16:24 ` Alex Thorlton
2016-05-12 11:41 ` Matt Fleming
2016-05-16 16:25 ` Alex Thorlton
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=1462996545-98387-1-git-send-email-athorlton@sgi.com \
--to=athorlton@sgi.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=rja@sgi.com \
--cc=sivanich@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--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
all inboxes | Powered by JetHome®