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: Tue, 1 Mar 2016 23:31:30 +0000 [thread overview]
Message-ID: <20160301233130.GB31476@codeblueprint.co.uk> (raw)
In-Reply-To: <20160301233040.GA31476@codeblueprint.co.uk>
On Tue, 01 Mar, at 11:30:40PM, Matt Fleming wrote:
> On Fri, 26 Feb, at 02:41:14PM, Matt Fleming wrote:
> > On Thu, 18 Feb, at 02:16:24PM, Peter Jones wrote:
> > >
> > > So the question I have is: would you rather chop up regions and reserve
> > > the space, or allocate a new copy and update the configuration table
> > > (after ExitBootServices()) to point to it? The latter makes it pretty
> > > easy to do from an API that all these drivers can use, and it makes the
> > > kexec case completely transparent.
> > >
> > > Up to you.
> >
> > I think it makes the most sense to chop up the regions we care about
> > (i.e. the ones we have drivers for) because not only does that save us
> > the effort of copying out the data on every kexec reboot, it also
> > prevents us from leaking each copy since we don't free them at the
> > moment.
> >
> > Then we just need to maintain a separate list of regions to free in
> > efi_free_boot_services() or have some other way to distinguish between
> > them.
> >
> > Oh, and save_runtime_map() would need updating to save Boot Services
> > regions too.
>
> I have a very rough draft of patches that implement this strategy on
> the 'experiemntal/efi-memmap' branch in the EFI tree if anyone is
> curious and wants to take a look. The series will be sent out soon.
Obviously that's supposed to read: experimental/efi-memmap
next prev parent reply other threads:[~2016-03-01 23:31 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
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 [this message]
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=20160301233130.GB31476@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