From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/3] arm: Add [U]EFI runtime services support
Date: Thu, 17 Oct 2013 12:58:34 -0400 [thread overview]
Message-ID: <1382029114.1768.10.camel@deneb.redhat.com> (raw)
In-Reply-To: <20131017143121.GJ1557@rocoto.smurfnet.nu>
On Thu, 2013-10-17 at 16:31 +0200, Leif Lindholm wrote:
> On Thu, Oct 17, 2013 at 03:07:39PM +0100, Matt Fleming wrote:
> > > +/*
> > > + * If you need to (temporarily) support buggy firmware.
> > > + */
> > > +#define KEEP_BOOT_SERVICES_REGIONS
> >
> > Have you seen firmware that requires this? I'm just curious more than
> > anything else.
>
> Not really.
> I _think_ I saw it on a debug build of a development platform once.
> That coincided with me seeing a post on linux-efi about some laptop
> that broke unless boot services regions were preserved, so I decided
> to put it in there for any future debugging.
>
I see a fairly consistent segfault when the arm64 kernel calls the
SetVirtualAddressMap function. It doesn't happen when the boot services
regions are included in the mapping. This is with edk2 firmware. I
haven't really dug into where it goes wrong.
next prev parent reply other threads:[~2013-10-17 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 11:24 [PATCH v2 0/3] arm: [U]EFI runtime services support Leif Lindholm
2013-10-03 11:24 ` [PATCH v2 1/3] Documentation: arm: add UEFI support documentation Leif Lindholm
2013-10-03 16:11 ` Rob Herring
2013-10-03 17:18 ` Leif Lindholm
2013-10-04 12:54 ` Mark Rutland
2013-10-03 17:10 ` Mark Rutland
2013-10-03 19:44 ` Leif Lindholm
2013-10-03 11:24 ` [PATCH v2 2/3] arm: Add [U]EFI runtime services support Leif Lindholm
2013-10-17 14:07 ` Matt Fleming
2013-10-17 14:31 ` Leif Lindholm
2013-10-17 16:58 ` Mark Salter [this message]
2013-10-03 11:24 ` [PATCH v2 3/3] init: efi: arm: enable (U)EFI runtime services on arm Leif Lindholm
2013-11-15 18:04 ` [PATCH v2 0/3] arm: [U]EFI runtime services support Olof Johansson
2013-11-15 18:54 ` Leif Lindholm
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=1382029114.1768.10.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--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).