From: Jason Andryuk <jandryuk@gmail.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] [PATCH v3 0/2] Optionally call EFI SetVirtualAddressMap()
Date: Tue, 15 Oct 2019 08:25:54 -0400 [thread overview]
Message-ID: <CAKf6xpsFj_8b9nDWLU2iYdHJTFmYQ-vy2YTwhiPQSDNoa79j6A@mail.gmail.com> (raw)
In-Reply-To: <cover.b80738fa53144bc6e5e32c048ccf4e4b95355844.1570918263.git-series.marmarek@invisiblethingslab.com>
On Sat, Oct 12, 2019 at 6:11 PM Marek Marczykowski-Górecki
<marmarek@invisiblethingslab.com> wrote:
>
> Workaround buggy UEFI accessing boot services memory after ExitBootServices().
> Patches discussed here:
> https://lists.xenproject.org/archives/html/xen-devel/2019-08/msg00701.html
>
> In addition to the tests below, I've tested kexec on xen.efi with this option
> enabled and it (still) works.
>
> Test results on few laptops:
>
> Thinkpad x230, firmware version 2.77:
> - without the patch: crashes on RS call (mapbs helps)
> - with patch: works
> - same with xen.efi and MB2
>
> Librem 14 v1, firmware version (AMI) ARUD026 (06/18/2015):
> - without the patch: works
> - with the patch: works
> - same with xen.efi and MB2
>
> Dell Latitude E6420, firmware version A21:
> this machine requires efi=attr=uc workaround
> - without the patch: dom0 hangs before sending any message to the console (even with earlyprintk=xen etc)
> - with the patch: crashes before dom0 prints anything: mm.c:896:d0v0 non-privileged attempt to map MMIO space 2c2c2c2c2c
> - same with xen.efi and MB2
>
> Thinkpad W540:
> - without the patch: crashes on RS call (only efi=no-rs helps)
> - with patch: works
> - tested only with MB2
>
> Thinkpad X1 Carbon gen5, firmware version 1.22 (2017-07-04):
> - without the patch: works
> - with patch: works
> - tested only xen.efi
>
> Thinkpad P52, firmware version 1.25 (2018-04-15):
> - without the patch (MB2): hangs on RS call (mapbs helps)
> - without the patch (xen.efi): works(?!)
> - with the patch: works
> - tested with xen.efi and MB2
>
> Changes in v2:
> - fix boot with xen.efi (efi_memmap at this point still needs to be accessed
> via physical address). TBH, I don't understand why previous version worked
> with MB2 - is directmap mapped at this point?
v1 failed to boot for me.
For v3:
Dell Latitude 5580, firmware 1.16.0
- without the patch: works
- with patch: works
- tested only xen.efi
Tested-by: Jason Andryuk <jandryuk@gmail.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-10-15 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 22:11 [Xen-devel] [PATCH v3 0/2] Optionally call EFI SetVirtualAddressMap() Marek Marczykowski-Górecki
2019-10-12 22:11 ` [Xen-devel] [PATCH v3 1/2] efi: remove old SetVirtualAddressMap() arrangement Marek Marczykowski-Górecki
2019-10-23 15:15 ` Jan Beulich
2019-10-23 15:36 ` Marek Marczykowski-Górecki
2019-10-23 16:10 ` Jan Beulich
2019-10-23 16:38 ` Marek Marczykowski-Górecki
2019-10-23 15:26 ` Jan Beulich
2019-10-12 22:11 ` [Xen-devel] [PATCH v3 2/2] xen/efi: optionally call SetVirtualAddressMap() Marek Marczykowski-Górecki
2019-10-15 23:40 ` Andrew Cooper
2019-10-23 15:37 ` Jan Beulich
2019-10-23 16:07 ` Marek Marczykowski-Górecki
2019-10-23 16:13 ` Jan Beulich
2019-10-15 12:25 ` Jason Andryuk [this message]
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=CAKf6xpsFj_8b9nDWLU2iYdHJTFmYQ-vy2YTwhiPQSDNoa79j6A@mail.gmail.com \
--to=jandryuk@gmail.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=konrad.wilk@oracle.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).