From: matt@codeblueprint•co.uk (Matt Fleming)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/2] efi: esrt: use memremap not ioremap to access ESRT table in memory
Date: Thu, 18 Feb 2016 14:38:25 +0000 [thread overview]
Message-ID: <20160218143825.GI2651@codeblueprint.co.uk> (raw)
In-Reply-To: <CAKv+Gu8RP21vw1Ht7UtkHsen2GMUNx8DikH-hLaezV+uZvWO-g@mail.gmail.com>
On Thu, 18 Feb, at 03:21:25PM, Ard Biesheuvel wrote:
>
> We treat all Boot Services regions like Loader Code/Data or free
> regions: it is all recorded in memblock as usable memory, and only the
> regions that are explicitly reserved are protected from further
> general use.
>
> I am currently looking into the memory attribute table, and the use
> case is very similar. It would be very useful from our pov to simply
> memblock_reserve() the region right after having called
> efi_config_parse_tables(), and actually consume its data when we get
> around to it later. The ESRT handling is already split down the middle
> in the same way.
Agreed, this would also be useful in general for kexec. I've got a
couple of patches in flight that try to handle the BGRT case in a
different way,
https://lkml.kernel.org/r/1455723910-16710-2-git-send-email-matt at codeblueprint.co.uk
https://lkml.kernel.org/r/1455723910-16710-3-git-send-email-matt at codeblueprint.co.uk
Let me instead take a look at how we might be able to preserve only
those Boot Services regions we care out.
next prev parent reply other threads:[~2016-02-18 14:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 11:32 [PATCH v2 0/2] efi: ARM/arm64: wire up ESRT table Ard Biesheuvel
2016-02-15 11:32 ` [PATCH v2 1/2] efi: esrt: use memremap not ioremap to access ESRT table in memory Ard Biesheuvel
2016-02-15 15:45 ` Peter Jones
2016-02-16 19:19 ` Baicar, Tyler
2016-02-18 10:44 ` Matt Fleming
2016-02-18 12:16 ` Ard Biesheuvel
2016-02-18 13:28 ` Matt Fleming
2016-02-18 13:29 ` Ard Biesheuvel
2016-02-18 13:43 ` Matt Fleming
2016-02-18 13:44 ` Ard Biesheuvel
2016-02-18 14:15 ` Matt Fleming
2016-02-18 14:21 ` Ard Biesheuvel
2016-02-18 14:38 ` Matt Fleming [this message]
2016-02-19 9:27 ` Dave Young
2016-02-18 19:16 ` Peter Jones
2016-02-26 14:41 ` Matt Fleming
2016-03-01 23:30 ` Matt Fleming
2016-03-01 23:31 ` Matt Fleming
2016-03-02 1:16 ` Dave Young
2016-03-02 10:23 ` Matt Fleming
2016-03-04 6:25 ` Dave Young
2016-05-18 8:36 ` Ard Biesheuvel
2016-05-18 8:53 ` Matt Fleming
2016-06-16 13:47 ` Ard Biesheuvel
2016-06-20 11:49 ` Matt Fleming
2016-02-15 11:32 ` [PATCH v2 2/2] arm64/efi: esrt: add missing call to efi_esrt_init() Ard Biesheuvel
2016-02-15 15:46 ` Peter Jones
2016-02-16 20:25 ` Baicar, Tyler
2016-02-17 8:32 ` Ard Biesheuvel
2016-05-17 20:36 ` Christopher Covington
-- strict thread matches above, loose matches on Subject: below --
2016-07-11 19:00 [PATCH v2 0/2] efi/arm*: wire up ESRT table Ard Biesheuvel
2016-07-11 19:00 ` [PATCH v2 1/2] efi: esrt: use memremap not ioremap to access ESRT table in memory Ard Biesheuvel
2016-07-15 15:05 ` 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=20160218143825.GI2651@codeblueprint.co.uk \
--to=matt@codeblueprint$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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