From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org,
Ross Lagerwall <ross.lagerwall@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>
Subject: Re: [PATCH v4] efi: Avoid calling boot services after ExitBootServices()
Date: Tue, 9 Jun 2015 13:53:02 +0100 [thread overview]
Message-ID: <1433854382.7108.554.camel@citrix.com> (raw)
In-Reply-To: <5576EF6C020000780008294A@mail.emea.novell.com>
On Tue, 2015-06-09 at 12:51 +0100, Jan Beulich wrote:
> >>> On 09.06.15 at 12:36, <ross.lagerwall@citrix.com> wrote:
> > ping
>
> I'm still waiting for the ARM maintainers to ack ...
>
> >> --- a/xen/arch/arm/efi/efi-boot.h
> >> +++ b/xen/arch/arm/efi/efi-boot.h
> >> @@ -522,6 +522,11 @@ static void __init efi_arch_blexit(void)
> >> efi_bs->FreePool(memmap);
> >> }
> >>
> >> +static void __init efi_arch_halt(void)
> >> +{
> >> + stop_cpu();
> >> +}
> >> +
> >> static void __init efi_arch_load_addr_check(EFI_LOADED_IMAGE *loaded_image)
> >> {
> >> if ( (unsigned long)loaded_image->ImageBase & ((1 << 12) - 1) )
>
> ... this.
I think it is ok, it does a bit more than the x86 variant, which is that
it would interlock correctly with __cpu_die, where the open coded on x86
wouldn't (assuming you have any interlock anyway.
In terms of the rest of the patch, are those two places changed to use
SystemTable->BootServices instead of efi_bs, if the point of the patch
is to not use BootServices after exit is called?
>
> Jan
>
next prev parent reply other threads:[~2015-06-09 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:38 [PATCH v4] efi: Avoid calling boot services after ExitBootServices() Ross Lagerwall
2015-06-09 10:36 ` Ross Lagerwall
2015-06-09 11:51 ` Jan Beulich
2015-06-09 12:53 ` Ian Campbell [this message]
2015-06-09 13:05 ` Ross Lagerwall
2015-06-09 13:24 ` Ian Campbell
2015-06-09 13:26 ` Andrew Cooper
2015-06-09 13:44 ` Ian Campbell
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=1433854382.7108.554.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=ross.lagerwall@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.