From: Demi Marie Obenour <demi@invisiblethingslab.com>
To: Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xenproject.org
Cc: osstest service owner <osstest-admin@xenproject.org>
Subject: Re: [xen-unstable-smoke test] 171511: regressions - FAIL
Date: Wed, 6 Jul 2022 02:56:51 -0400 [thread overview]
Message-ID: <YsUyUCv7IAbXYwaB@itl-email> (raw)
In-Reply-To: <a9a8276f-725a-db6e-8223-a9e6060f7700@suse.com>
[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]
> > commit 8d410ac2c178e1dd1001cadddbe9ca75a9738c95
> > Author: Demi Marie Obenour <demi@invisiblethingslab.com>
> > Date: Tue Jul 5 13:10:46 2022 +0200
> >
> > EFI: preserve the System Resource Table for dom0
> >
> > The EFI System Resource Table (ESRT) is necessary for fwupd to identify
> > firmware updates to install. According to the UEFI specification §23.4,
> > the ESRT shall be stored in memory of type EfiBootServicesData. However,
> > memory of type EfiBootServicesData is considered general-purpose memory
> > by Xen, so the ESRT needs to be moved somewhere where Xen will not
> > overwrite it. Copy the ESRT to memory of type EfiRuntimeServicesData,
> > which Xen will not reuse. dom0 can use the ESRT if (and only if) it is
> > in memory of type EfiRuntimeServicesData.
> >
> > Earlier versions of this patch reserved the memory in which the ESRT was
> > located. This created awkward alignment problems, and required either
> > splitting the E820 table or wasting memory. It also would have required
> > a new platform op for dom0 to use to indicate if the ESRT is reserved.
> > By copying the ESRT into EfiRuntimeServicesData memory, the E820 table
> > does not need to be modified, and dom0 can just check the type of the
> > memory region containing the ESRT. The copy is only done if the ESRT is
> > not already in EfiRuntimeServicesData memory, avoiding memory leaks on
> > repeated kexec.
> >
> > See https://lore.kernel.org/xen-devel/20200818184018.GN1679@mail-itl/T/
> > for details.
> >
> > Signed-off-by: Demi Marie Obenour <demi@invisiblethingslab.com>
> > Reviewed-by: Jan Beulich <jbeulich@suse.com>
>
> ... this is the most likely candidate, considering in the log all we
> see is:
>
> Xen 4.17-unstable (c/s Mon Jun 27 15:15:39 2022 +0200 git:61ff273322-dirty) EFI loader
> Jul 5 23:09:15.692859 Using configuration file 'xen.cfg'
> Jul 5 23:09:15.704878 vmlinuz: 0x00000083fb1ac000-0x00000083fc880a00
> Jul 5 23:09:15.704931 initrd.gz: 0x00000083f94b7000-0x00000083fb1ab6e8
> Jul 5 23:09:15.836836 xenpolicy: 0x00000083f94b4000-0x00000083f94b6a5f
> Jul 5 23:09:15.980866 Using bootargs from Xen configuration file.
This would not surprise me at all. I was hoping that Jan would be able
to test this before he merged it, especially the ARM-specific stuff.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-06 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 3:39 [xen-unstable-smoke test] 171511: regressions - FAIL osstest service owner
2022-07-06 6:44 ` Jan Beulich
2022-07-06 6:56 ` Demi Marie Obenour [this message]
2022-07-06 7:02 ` Jan Beulich
2022-07-06 7:26 ` Demi Marie Obenour
2022-07-06 7:53 ` Julien Grall
2022-07-06 8:05 ` Demi Marie Obenour
2022-07-06 8:17 ` Julien Grall
2022-07-06 8:46 ` Jan Beulich
2022-07-06 8:50 ` Luca Fancellu
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=YsUyUCv7IAbXYwaB@itl-email \
--to=demi@invisiblethingslab.com \
--cc=jbeulich@suse.com \
--cc=osstest-admin@xenproject.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 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.