From: mjg59@srcf.ucam.org (Matthew Garrett)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4] Documentation: arm: [U]EFI runtime services
Date: Thu, 27 Jun 2013 15:37:14 +0100 [thread overview]
Message-ID: <20130627143714.GA12900@srcf.ucam.org> (raw)
In-Reply-To: <1372314821.557.33.camel@dabdike>
On Wed, Jun 26, 2013 at 11:33:41PM -0700, James Bottomley wrote:
> On Thu, 2013-06-27 at 07:23 +0100, Grant Likely wrote:
> > What is the problem trying to be avoided by not using the virtual map?
> > Is it passing the virtual mapping data from one kernel to the next
> > when kexecing? Or something else?
>
> Where to begin ... SetVirtualAddressMap() is one massive hack job ...
> just look at the tiano core implementation. Basically it has a fixed
> idea of where all the pointers are and it tries to convert them all to
> the new address space. The problem we see in x86 is that this
> conversion process isn't exhaustive due to implementation cockups, so
> the post virtual address map image occasionally tries to access
> unconverted pointers via the old physical address and oopses the kernel.
And yet it's the only mode in which the firmrware is actually tested
against an OS, so we don't have any real choice in the matter.
--
Matthew Garrett | mjg59 at srcf.ucam.org
next prev parent reply other threads:[~2013-06-27 14:37 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 18:10 [PATCH 0/4] arm: [U]EFI runtime services support Leif Lindholm
2013-06-25 18:11 ` [PATCH 1/4] Documentation: arm: [U]EFI runtime services Leif Lindholm
2013-06-25 18:46 ` Christopher Covington
2013-06-25 23:42 ` Stephen Warren
2013-06-26 13:20 ` Grant Likely
2013-06-26 13:53 ` Leif Lindholm
2013-06-26 13:59 ` Matt Fleming
2013-06-26 14:38 ` James Bottomley
2013-06-27 1:32 ` Matthew Garrett
2013-06-27 6:23 ` Grant Likely
2013-06-27 6:33 ` James Bottomley
2013-06-27 14:37 ` Matthew Garrett [this message]
2013-06-27 15:09 ` James Bottomley
2013-06-27 15:37 ` Grant Likely
2013-06-27 17:28 ` Matthew Garrett
2013-06-27 14:54 ` Grant Likely
2013-06-27 15:04 ` James Bottomley
2013-06-27 18:32 ` Russell King - ARM Linux
2013-06-27 9:00 ` Leif Lindholm
2013-06-27 14:38 ` Matthew Garrett
2013-06-27 18:32 ` H. Peter Anvin
2013-06-26 18:32 ` Stephen Warren
2013-06-26 19:31 ` Leif Lindholm
2013-06-27 18:04 ` Stephen Warren
2013-06-27 20:11 ` Grant Likely
2013-06-26 13:13 ` Grant Likely
2013-06-26 14:04 ` Leif Lindholm
2013-06-26 14:35 ` Grant Likely
2013-06-27 14:22 ` Arnd Bergmann
2013-06-30 3:21 ` Rob Landley
2013-06-25 18:11 ` [PATCH 2/4] x86: efi: break efi_lookup_mapped_addr out to generic code Leif Lindholm
2013-06-26 13:30 ` Grant Likely
2013-06-26 13:32 ` Matt Fleming
2013-06-26 14:11 ` Leif Lindholm
2013-06-26 14:40 ` Matt Fleming
2013-06-25 18:11 ` [PATCH 3/4] arm: Add [U]EFI runtime services support Leif Lindholm
2013-06-25 18:20 ` Matthew Garrett
2013-06-26 13:46 ` Grant Likely
2013-06-26 13:46 ` Grant Likely
2013-06-26 13:54 ` Matt Fleming
2013-06-26 14:15 ` Borislav Petkov
2013-06-26 14:35 ` Grant Likely
2013-06-26 14:22 ` Leif Lindholm
2013-06-25 18:11 ` [PATCH 4/4] init: efi: arm: enable (U)EFI runtime services on arm Leif Lindholm
2013-06-26 13:24 ` Grant Likely
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=20130627143714.GA12900@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).