From: Matt Fleming <matt@codeblueprint.co.uk>
To: "Kweh, Hock Leong" <hock.leong.kweh@intel.com>
Cc: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
joeyli <jlee@suse.com>, Borislav Petkov <bp@alien8.de>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
"Ong, Kean Chai" <kean.chai.ong@intel.com>
Subject: Re: [PATCH] efi/capsule: Make efi_capsule_pending() lockless
Date: Thu, 5 May 2016 15:36:43 +0100 [thread overview]
Message-ID: <20160505143643.GN2839@codeblueprint.co.uk> (raw)
In-Reply-To: <F54AEECA5E2B9541821D670476DAE19C4A914755@PGSMSX102.gar.corp.intel.com>
On Thu, 05 May, at 02:27:16PM, Kweh, Hock Leong wrote:
>
> If not mistaken, the EFI firmware will not update a partially uploaded binary due to checksum error.
> User is required to re-update the efi capsule again on the next boot up.
Ah, so the capsule is only processed by the firmware after rebooting?
That makes sense and alleviates my concerns about rebooting while in
the middle of efi_capsule_update().
Thanks Wilson!
next prev parent reply other threads:[~2016-05-05 14:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 22:13 [PATCH] efi/capsule: Make efi_capsule_pending() lockless Matt Fleming
2016-05-03 9:02 ` Borislav Petkov
2016-05-03 14:12 ` Matt Fleming
2016-05-04 9:30 ` Borislav Petkov
2016-05-04 11:46 ` Matt Fleming
2016-05-04 12:20 ` Borislav Petkov
2016-05-04 13:36 ` Matt Fleming
2016-05-04 14:35 ` Matt Fleming
2016-05-05 14:27 ` Kweh, Hock Leong
2016-05-05 14:36 ` Matt Fleming [this message]
2016-05-05 14:55 ` One Thousand Gnomes
2016-05-06 1:32 ` Bryan O'Donoghue
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=20160505143643.GN2839@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=boon.leong.ong@intel.com \
--cc=bp@alien8.de \
--cc=hock.leong.kweh@intel.com \
--cc=jlee@suse.com \
--cc=kean.chai.ong@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pure.logic@nexus-software.ie \
/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).