From: Matt Fleming <matt@console-pimps.org>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt.fleming@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Kweh, Hock Leong" <hock.leong.kweh@intel.com>
Subject: Re: [PATCH 2/2] efi: Capsule update support
Date: Tue, 14 Oct 2014 22:46:33 +0100 [thread overview]
Message-ID: <20141014214633.GD14343@console-pimps.org> (raw)
In-Reply-To: <20141010182846.GA10588@pd.tnic>
On Fri, 10 Oct, at 08:28:47PM, Borislav Petkov wrote:
>
> You have efi_capsule_update() vs efi_update_capsule(). Maybe change the
> names a bit more for differentiation. Or prepend the workhorse doing all
> the work with "__" or so...
Yeah, I really didn't come up with a great naming scheme here. I'll fix
that.
> > +
> > + for (i = 0; i < nr_block_pgs; i++) {
> > + block_pgs[i] = alloc_page(GFP_KERNEL);
>
> Maybe alloc_pages() once we verify that it actually gives phys. contig.
> memory and maybe also try to do it outside of the locked region. I don't
> know if it would matter to drop the locks though as capsule updating is
> not something you do pretty often. I'd hope!
Actually, I'm not bothered about getting physically contiguous memory
because we pass a scatter gather list to the firmware anyway. What I was
looking for was to avoid doing high order allocations when we don't
really need them (lots of low order allocs are fine).
Right, allocating under the lock isn't a great idea. I'll take a look at
reworking this to do the allocation up front.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-10-14 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 14:42 [PATCH 1/2] efi: Move efi_status_to_err() to efi.h Matt Fleming
2014-10-07 14:42 ` [PATCH 2/2] efi: Capsule update support Matt Fleming
2014-10-10 18:28 ` Borislav Petkov
2014-10-14 21:46 ` Matt Fleming [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-10 15:55 Sam Protsenko
2014-10-13 9:53 ` Matt Fleming
2014-10-13 15:43 ` Sam Protsenko
2014-10-14 15:30 ` Sam Protsenko
2014-10-16 16:15 ` Matt Fleming
2014-11-04 13:56 ` Sam Protsenko
2014-11-07 15:12 ` 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=20141014214633.GD14343@console-pimps.org \
--to=matt@console-pimps.org \
--cc=bp@alien8.de \
--cc=hock.leong.kweh@intel.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
/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