From: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org
Cc: sylvain.chouleur-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
Ard Biesheuvel
<ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: [PATCH 0/3] efi interruptible runtime services
Date: Fri, 22 Apr 2016 09:13:20 +0200 [thread overview]
Message-ID: <1461309203-11806-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This is a resend of the generic part of the series 'efi interruptible runtime
services', of which v3 was sent out on January 13th. I have added an additional
patch on top which gives runtime-wrappers.c the same treatment as efivars.c,
i.e., replacing the spinlock with a semaphore.
Ard Biesheuvel (1):
efi: replace runtime services spinlock with semaphore
Sylvain Chouleur (2):
efi: use a file local lock for efivars
efi: don't use spinlocks for efi vars
drivers/firmware/efi/efi-pstore.c | 36 +++--
drivers/firmware/efi/efivars.c | 22 ++-
drivers/firmware/efi/runtime-wrappers.c | 77 +++++-----
drivers/firmware/efi/vars.c | 150 +++++++++++++-------
fs/efivarfs/inode.c | 5 +-
fs/efivarfs/super.c | 9 +-
include/linux/efi.h | 13 +-
7 files changed, 202 insertions(+), 110 deletions(-)
--
2.5.0
next reply other threads:[~2016-04-22 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 7:13 Ard Biesheuvel [this message]
[not found] ` <1461309203-11806-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-22 7:13 ` [PATCH 1/3] efi: use a file local lock for efivars Ard Biesheuvel
2016-04-22 7:13 ` [PATCH 2/3] efi: don't use spinlocks for efi vars Ard Biesheuvel
2016-04-22 7:13 ` [PATCH 3/3] efi: replace runtime services spinlock with semaphore Ard Biesheuvel
[not found] ` <1461309203-11806-4-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-04-22 7:55 ` Ard Biesheuvel
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=1461309203-11806-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
--cc=sylvain.chouleur-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).