From: "Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
Chun-Yi <jlee@suse.com>, Borislav Petkov <bp@alien8.de>,
"Luck, Tony" <tony.luck@intel.com>,
"Will Deacon" <will.deacon@arm.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"Mark Rutland" <mark.rutland@arm.com>,
Bhupesh Sharma <bhsharma@redhat.com>,
"Neri, Ricardo" <ricardo.neri@intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
Matt Fleming <matt@codeblueprint.co.uk>,
"Zijlstra, Peter" <peter.zijlstra@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>
Subject: RE: [PATCH V2 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization
Date: Thu, 8 Mar 2018 18:06:45 +0000 [thread overview]
Message-ID: <FFF73D592F13FD46B8700F0A279B802F2E581AD0@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu_ZYGwgORet4ruL8=GUy75LMAuLeYD987FA3UVYuw8GMg@mail.gmail.com>
> > void __init efi_enter_virtual_mode(void) diff --git
> > a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c index
> > cd42f66a7c85..838b8efe639c 100644
> > --- a/drivers/firmware/efi/efi.c
> > +++ b/drivers/firmware/efi/efi.c
> > @@ -328,6 +328,12 @@ static int __init efisubsys_init(void)
> > if (!efi_enabled(EFI_BOOT))
> > return 0;
> >
> > + /*
> > + * Clean DUMMY object calls EFI Runtime Service, set_variable(), so
> > + * it should be invoked only after efi_rts_workqueue is ready.
> > + */
> > + efi_delete_dummy_variable();
> > +
>
> Is there any way to keep this local to arch/x86?
>
I think, we can definitely do that. I will retake a look at the possibilities
and will update this thread.
> > /* We register the efi directory at /sys/firmware/efi */
> > efi_kobj = kobject_create_and_add("efi", firmware_kobj);
> > if (!efi_kobj) {
> > diff --git a/include/linux/efi.h b/include/linux/efi.h index
> > f5083aa72eae..c4efb3ef0dfa 100644
> > --- a/include/linux/efi.h
> > +++ b/include/linux/efi.h
> > @@ -992,6 +992,7 @@ extern efi_status_t efi_query_variable_store(u32
next prev parent reply other threads:[~2018-03-08 18:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 23:23 [PATCH V2 0/3] Use efi_rts_workqueue to invoke EFI Runtime Services Sai Praneeth Prakhya
2018-03-05 23:23 ` [PATCH V2 1/3] x86/efi: Call efi_delete_dummy_variable() during efi subsystem initialization Sai Praneeth Prakhya
2018-03-08 7:43 ` Ard Biesheuvel
2018-03-08 18:06 ` Prakhya, Sai Praneeth [this message]
2018-03-05 23:23 ` [PATCH V2 2/3] efi: Introduce efi_rts_workqueue and some infrastructure to invoke all efi_runtime_services() Sai Praneeth Prakhya
2018-03-06 11:13 ` Mark Rutland
2018-03-08 4:00 ` Prakhya, Sai Praneeth
2018-03-07 11:55 ` Miguel Ojeda
2018-03-08 4:22 ` Prakhya, Sai Praneeth
2018-03-08 9:12 ` Miguel Ojeda
2018-03-08 18:09 ` Prakhya, Sai Praneeth
2018-03-07 12:11 ` Borislav Petkov
2018-03-08 5:31 ` Prakhya, Sai Praneeth
2018-03-08 14:08 ` Borislav Petkov
2018-03-08 17:05 ` Luck, Tony
2018-03-09 10:57 ` Borislav Petkov
2018-03-09 2:37 ` Prakhya, Sai Praneeth
2018-03-09 11:11 ` Borislav Petkov
2018-03-10 0:33 ` Prakhya, Sai Praneeth
2018-03-14 17:40 ` Borislav Petkov
2018-03-08 5:38 ` Prakhya, Sai Praneeth
2018-03-05 23:23 ` [PATCH V2 3/3] efi: Use efi_rts_workqueue to invoke EFI Runtime Services Sai Praneeth Prakhya
2018-03-06 0:05 ` Dan Williams
2018-03-06 0:56 ` Prakhya, Sai Praneeth
2018-03-06 11:26 ` Mark Rutland
2018-03-08 4:11 ` Prakhya, Sai Praneeth
2018-03-08 4:33 ` Dan Williams
2018-03-08 5:06 ` Prakhya, Sai Praneeth
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=FFF73D592F13FD46B8700F0A279B802F2E581AD0@ORSMSX114.amr.corp.intel.com \
--to=sai.praneeth.prakhya@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bhsharma@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matt@codeblueprint.co.uk \
--cc=peter.zijlstra@intel.com \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).