From: Alex Thorlton <athorlton@sgi.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Alex Thorlton <athorlton@sgi.com>,
linux-kernel@vger.kernel.org, Russ Anderson <rja@sgi.com>,
Mike Travis <travis@sgi.com>, Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [RFC PATCH] Fix EFI callbacks on UV during kexec
Date: Thu, 4 Aug 2016 10:07:26 -0500 [thread overview]
Message-ID: <20160804150726.GP5939@stormcage.americas.sgi.com> (raw)
In-Reply-To: <20160804092532.GJ3636@codeblueprint.co.uk>
On Thu, Aug 04, 2016 at 10:25:32AM +0100, Matt Fleming wrote:
> On Mon, 01 Aug, at 09:34:10AM, Alex Thorlton wrote:
> >
> > Hmm... That's a good point. It certainly would be nice for us to have
> > those mappings in the kexec kernel, at least for the time being. If
> > you're not opposed to it, I can write up the patch. Pretty sure it's a
> > one-liner.
>
> If it's that trivial, sure, please go ahead and submit.
Sure thing. I played around with this a bit before I sent this patch
up. I'm pretty sure it all worked as expected, but I'll need to double
check everything. I'll try and get it out in the next day or two.
Thanks, Matt!
- Alex
prev parent reply other threads:[~2016-08-04 15:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 22:38 [RFC PATCH] Fix EFI callbacks on UV during kexec Alex Thorlton
2016-07-26 22:38 ` [PATCH] Skip UV runtime services mapping in the efi_runtime_disabled case Alex Thorlton
2016-08-01 13:49 ` Matt Fleming
2016-08-01 14:28 ` Alex Thorlton
2016-08-03 19:36 ` Alex Thorlton
2016-08-04 9:23 ` Matt Fleming
2016-08-01 13:39 ` [RFC PATCH] Fix EFI callbacks on UV during kexec Matt Fleming
2016-08-01 14:34 ` Alex Thorlton
2016-08-04 9:25 ` Matt Fleming
2016-08-04 15:07 ` Alex Thorlton [this message]
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=20160804150726.GP5939@stormcage.americas.sgi.com \
--to=athorlton@sgi.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mingo@redhat.com \
--cc=rja@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